Collection Tasks
A collection task captures which device to use, how to upload, how many episodes to record, and who records them, all on one task sheet. The model determines the format, and the SN determines the source: a task can be submitted only once both are set.
Where: Data Collection → Collection Tasks in the left navigation.
Creating a Collection Task
FAEs and R&D engineers can create tasks in the projects they have access to. Click New and complete four steps:
Step 1: Select a Device Model
Choose Station Lite, MOS, Robot-free Ego, or Robot-free UMI from the list. The storage format field is then filled in automatically and becomes read-only:
| Model | Storage format |
|---|---|
| Station Lite / MOS | HDF5 |
| Robot-free Ego / Robot-free UMI | RAW |
Step 2: Select a Device SN
The list shows only registered devices of the selected model, each displayed as name · SN · status.
- Devices that are under maintenance, offline, or decommissioned are grayed out.
- Devices already bound to open tasks are marked "Bound to N open tasks".
- If the list is empty, the create button is disabled and the page offers Register Device and Go to Device Management. Register the device and its SN, then return here to continue.
Step 3: Select an Upload Mode
Choose full, screened, or segmented upload. All three modes are available for every device model. See Data Upload for guidance.
The upload mode is locked after creation
The upload mode is set by an authorized role when the task is created and can't be changed afterward. Collectors follow the mode as specified.
Step 4: Enter Task Details
| Field | Required | Rules |
|---|---|---|
| Task name | ✓ | Up to 50 characters |
| English name | ✓ | Letters, digits, and underscores only; used to build storage paths |
| Scene | ✓ | Selected from the scene list |
| Target count | ✓ | A positive integer; cannot be 0 or a decimal |
| Collector | Can be left blank and assigned later | |
| Due date | Optional | |
| Tags | Selected from tag management; used for filtering later | |
| Notes | Up to 500 characters |
Click Create Task. The task appears in the list with status Pending Claim (collector assigned) or Pending (no collector assigned).
Editing a Task
| Field | Editable after creation? | Notes |
|---|---|---|
| Task name, notes, due date, tags | Yes | — |
| Collector | Yes | Use Change Assignee |
| Target count | Yes | Only FAEs and R&D engineers can change it. The platform records who changed it and when; the progress denominator updates, and the completed count never goes down. If the task has already been claimed, the collector is asked to reconfirm. |
| Device model, device SN, storage format, upload mode | No | Create a new task if any of these need to change. The original task is kept so historical data definitions stay intact. |
For Data Collectors
After signing in, collectors see only My Collection Tasks, with their assigned tasks shown as cards.
- Claim the task: Click Claim Task on a card marked Pending Claim. If the task configuration changed after assignment, the card is marked Changed, and a dialog lists the changes before you claim. You then work to the latest configuration.
- Run pre-collection checks: Connect the device and let the client complete its checks. If the teleoperation device ID is missing or a check fails, the task can't be set to ready.
- Start collecting: Click Start Collecting and record each episode as instructed. Upload progress is shown live in a dialog.
- Pause and resume: You can pause at any time; uploaded data is not affected.
- Finish: Once the target count is reached and every upload has finished, the task changes to Completed automatically.
What collectors can't change
Collectors can't change the target count or the upload mode. To adjust either, contact an FAE or R&D engineer.
Task States
| State | Meaning |
|---|---|
| Pending | Created, but no collector assigned yet |
| Pending Claim | Assigned and waiting for the collector to claim it |
| In Progress | Claimed by the collector and collection has started |
| Completed | Target count reached and all uploads finished |
| Incomplete | Past the due date without reaching the target count |
| Closed | Closed manually; no longer accepts new data |
Reaching the count isn't enough
A task is complete only when it has both reached the target count and finished uploading. If the count is reached but data is still uploading or an upload failed, the task stays In Progress.
Task List Columns
| Column | Description |
|---|---|
| Task ID | Generated by the platform, starting with the creation time, for example 20260929181225_LUMOSMOS |
| Task name | Entered at creation |
| Assignee | The current collector |
| Device | Model · name · SN |
| Upload mode | Full / screened / segmented |
| Progress | Completed episodes / target count |
| Due date, status, created at | — |
You can filter the list by keyword (task name or task ID), upload mode, and status.

