What sensor data can Avala label for robotics?
Avala publishes workflows for cameras, video, LiDAR, point clouds, depth maps, and sequences, and it imports MCAP, ROS 1, and ROS 2 recordings with synchronized camera, LiDAR, and telemetry streams.
Sensor data labeling
Avala labels camera, LiDAR, point-cloud, and sequence data for robotics, then keeps that work inside the fleet learning loop: ingest, review, a versioned dataset, and the training handoff.
面向 Physical AI 的 Fleet Learning Infrastructure
| Capability | Status | What Avala publishes |
|---|---|---|
| Cameras and video | Supported | Images and video are labeled with 2D boxes and masks, alongside the sequence they belong to. |
| LiDAR and point clouds | Supported | Point-cloud scenes take 3D cuboids and point-cloud labels, with camera and sequence context kept where the workflow supports them. |
| Depth maps | Supported | Depth maps are a published annotation type on the same workflow as video, point clouds, text, and audio. |
| MCAP, ROS 1, and ROS 2 | Supported | MCAP回放遵循支持的消息模式。SDK的ROS bag导入器会转换相机数据及支持的数值和文本主题,并报告跳过的主题,包括点云。支持的消息类型 |
| Timestamp and calibration context | Preserved | Timestamp and calibration context stay attached while teams inspect the same event across sensor streams. |
| 2D boxes, masks, polylines, and classifications | Supported | These are published ground-truth outputs for camera and sequence data. |
| 3D cuboids | Supported | Cuboids capture position, dimensions, and heading in point-cloud scenes. |
| Tracking across a sequence | Supported | Tracked objects are a published output, so an object keeps its identity across the sequence. |
| Trajectory context | Supported | Camera, point-cloud, and trajectory data stay aligned as work moves through labeling and review. |
| LeRobot datasets | Supported | 将LeRobot数据导入为MCAP记录。LeRobot v3往返转换保留数值列和文本列;相机帧会重新编码,因此像素并非完全一致。 一个Avala序列对应一个LeRobot episode。状态和动作需要数值源字段。可选的结果标签写入附属文件;序列导出的时间戳遵循配置的帧率。 LeRobot转换指南 |
查看两条 LeRobot v3 导出路径的字段映射。所需输入各不相同:仅有相机数据无法提供机器人动作。选择转换器前,请展开各路径查看要求。
默认导出包含相机、时间戳和任务文本。状态和动作需要配置数值型源字段;缺失值会报错。结果以可选的附属文件元数据提供。序列时间戳使用配置的帧率。
observation.images.*
--state-key → observation.state
--action-key → action
frame_index / fps → timestamp
--include-outcomes → meta/avala_sequence_outcomes.jsonl关节状态提供实测位置,独立的命令主题提供动作。帧以第一台相机为基准,其他主题使用各帧时刻或之前的值。导出报告记录时间偏差、丢弃的起始帧和视频编码模式。
foxglove.CompressedImage / CompressedVideo → observation.images.*
/joint_states → observation.state
/joint_commands → action
frame_index / fps → timestamp
meta/avala_export_report.json使用此清单与 Avala 或其他供应商确定基准测试范围。开始前就证据和验收标准达成一致。勾选仅记录您在本页的审查,不代表认证供应商,也不会提交请求。
英文空白规划模板。请在商定项目之前定义要求并记录证据。这些文件不含结果或商业条款。
The pages below are the detailed sources for the capabilities in the table.
Avala publishes workflows for cameras, video, LiDAR, point clouds, depth maps, and sequences, and it imports MCAP, ROS 1, and ROS 2 recordings with synchronized camera, LiDAR, and telemetry streams.
在Avala的车队学习工作流程中,标注与数据导入、可视化、质量审核及版本化数据集交付相连接。
Labeling runs with human review and traceable quality-control states. The annotation pages describe the review path for camera, LiDAR, and telemetry.
Book a demo, or read the ground-truth outputs and the MCAP annotation page. LeRobot import and export are documented with the SDKs.