Skip to content

Object States ​

Every object's state in the platform is driven by actions and can't be edited manually.

Collection Tasks ​

text
Pending ──assign──▶ Pending Claim ──claim──▶ In Progress ──target reached and uploads complete──▶ Completed
                                                │
                                                ├─ due date passed, target not reached ──▶ Incomplete
                                                └─ closed manually ──▶ Closed
StateEntered when
PendingCreated without an assigned collector
Pending ClaimA collector is assigned but hasn't claimed the task
In ProgressThe collector has claimed the task
CompletedThe target count is reached and all uploads are complete
IncompleteThe due date passed before the target count was reached
ClosedClosed manually by an authorized role

Devices ​

StateDescriptionSelectable for tasks?
OnlineHeartbeat is normal✓
In UseRunning a task✓
OfflineNo heartbeat for about 90 seconds✗
Under MaintenanceManually set to maintenance✗
DecommissionedOut of service✗

Data Assets ​

text
Upload complete ──G1 check──┬─ Pass + HDF5 ──▶ Ready to Curate ──exported to a dataset──▶ Exported
                            ├─ Pass + RAW ──▶ Awaiting Pipeline ──pipeline complete──▶ (outputs) Ready to Curate
                            └─ Fail ──────▶ Validation Failed
StateCan be added to a curation project?
Ready to Curate✓
Awaiting Pipeline✗
Validation Failed✗
Exported✓

Items in a Curation Project ​

DimensionValues
Review statusPending Review / Reviewed
Exclude episodeYes / No
Anomaly labelsZero or more
RangesZero or more keep / excluded ranges

Batch Processing ​

StateDescription
ProcessingRunning in the background
CompletedEverything succeeded
Completed with ErrorsAt least one item failed; the rest were processed normally
FailedThe job couldn't run

Pipeline Processing ​

text
Not Processed ──start──▶ Processing ──all required operators succeed──▶ Completed
                             └──any required operator fails──▶ Failed ──retry failed steps──▶ Processing

Dataset Versions ​

text
Pending Export ──▶ Exporting ──┬─ success ──▶ Exported (frozen)
                              └─ failure ──▶ Export Failed ──export again──▶ Pending Export

Only Exported versions can be used for training.

Training Jobs ​

text
Queued ──compute allocated──▶ Training ──full step budget──▶ Completed
                                 ├─ stopped manually ──▶ Stopped
                                 └─ terminated abnormally ──▶ Failed

Exporting a checkpoint during training doesn't change the job state.

Deployments ​

StateDescription
CheckingThe four edge checks are running
DeployingThe client is pulling the model and inference code
RunningDeployed and ready for inference
StoppedStopped manually
FailedThe deployment failed; the stable version is not replaced

NexCore is evolving rapidly; the latest version prevails.NexCore Docs · Embodied AI Skill Learning Platform by Lumos Robotics