Skip to content

Core Concepts ​

The key to understanding NexCore is understanding its objects and how data moves between them. This page defines the core terms used throughout the documentation.

Objects at a Glance ​

ObjectWhat it isCreated byMutability
DeviceA collection or execution device registered in the device inventory, identified by model and serial number (SN)Device registrationName and status are editable; SN is not
Collection taskA task sheet that defines which device to use, how to upload, how many episodes to record, and who records themFAE / R&D engineerDevice, SN, format, and upload mode are locked
Data assetOne uploaded and validated recording with a permanent data IDUpload and ingestionRead-only
Curation projectA workspace that references a set of data assets and records labels, ranges, and reviewsUserContinuously editable
Processing jobOne pipeline run that processes project data with selected operatorsUserRun record is retained
Annotated dataData with structured annotations: quality labels, time ranges, trajectories, depth, keypoints, and moreCuration and pipelinesUpdated through new versions
Dataset versionA frozen snapshot exported from a curation project, in HDF5 or LeRobot formatExportFrozen and immutable
Training jobA single training run bound to dataset versions, a model family, and computeUserParameter snapshot is locked
ModelA model version produced by training, or a checkpoint model exported during trainingTraining jobLineage fields are fixed
DeploymentA model version running on a cloud or edge nodeUserCan be stopped or rolled back
Bad caseA failed segment from a run, with the failed node, step, and time rangeInference feedbackCan enter curation after review

Data Side: From Raw Data to Datasets ​

How data assets, curation projects, processing jobs, outputs, and dataset versions relate

  • Data assets are read-only. A curation project references data IDs; it never copies or modifies the original data. The same asset can be used in multiple projects.
  • Processing jobs create new data. Pipeline outputs are written back to the asset pool and tagged with the processing job ID, while the original data is preserved. Outputs can be added to curation projects in turn.
  • Datasets are snapshots. A curation project remains editable; each export creates a new dataset version and leaves earlier versions untouched.
  • Annotated data can be delivered directly. Besides training, an exported dataset can be packaged and downloaded through a delivery order.

Two Storage Formats ​

Storage formatSourceCurate directly?
HDF5Teleoperated robots: Station Lite, MOS✓
RAWRobot-free Ego, Robot-free UMIAfter a pipeline run

The storage format is determined by the device model and cannot be selected manually. The export format (HDF5 or LeRobot) is chosen when you export a dataset.

Model Side: From Datasets to Deployment ​

How training jobs, checkpoint models, model versions, and deployments relate

  • Training jobs take dataset versions as input. You can select multiple versions in the same format; the parameter snapshot is locked on submission.
  • One training job can produce multiple models. Checkpoints exported during training are registered as models, and a final model version is produced when training completes.
  • Models are counted by version. Each model version records its training job, dataset versions, hyperparameter snapshot, and step count.
  • Deployments run models on robots. A deployment record links to its model version, execution data flows back to the platform, and failure segments can be reviewed and returned to curation.

Accounts, Projects, and Roles ​

ConceptDescription
AccountProvisioned by an administrator; self-registration is not available
ProjectThe unit of business organization. Data is isolated by project, and an account can access only the projects it has been granted
RoleAdministrator, FAE, data collector, R&D engineer, data owner, and so on. Determines which pages are visible and which actions are allowed

See Accounts and Members and Roles and Permissions.

Terminology ​

The documentation uses these terms consistently:

UseAvoid
Dataset / dataset versionTraining set, data package
Collection taskPersonal task, collection order
Pipeline / processing jobWorkflow task, pipeline task
Training jobTraining run, training task
Model / model versionWeights package
DeploymentGo-live, push to device

For the full list, see the Glossary.

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