Quick Start
This page gives you a working overview of NexCore and walks through a minimal example of the full collect → train → deploy loop.
Before You Begin
| Requirement | Details |
|---|---|
| Platform URL | NexCore website and sign-in: nexcore.lumosbot.tech |
| Account | Accounts are provisioned by an administrator; self-registration is not available. See Accounts and Members. If you don't have an account yet, request access. |
| Project access | Data is isolated by project. When your account is created, the administrator assigns your role and the projects you can access. |
| Collection devices | Before collecting, each device must be registered in the device inventory with its serial number (SN). See Device Management. |
| Browser | The latest Chrome or Edge, with a screen at least 1440 px wide so the data workbench timeline and charts display in full. |
The Console
After you sign in, the console has three main areas:
| Area | Contents |
|---|---|
| Top bar | Assistant and personal settings |
| Left navigation | Grouped by workflow: Data Collection, Data Curation, Model Training, Model Deployment, Model Evaluation, Device Management, and System. Only modules available to your role are shown. |
| Home | Platform asset statistics (total data collected, datasets, models, devices, inference runs), workflow overview, training loss monitor, recent activity, device overview, and latest models |
The shortcut buttons on the home page (New Collection, New Training, Inference Test, and New Deployment) take you straight into each workflow.
Start by Role
| Role | Main responsibilities | Start here |
|---|---|---|
| Administrator | Account provisioning, role and project assignment, compute quotas | Accounts and Members |
| Field application engineer (FAE) | Create collection tasks, curate data, export datasets, train and deploy models | Tutorial B |
| Data collector | Claim assigned tasks and collect data as specified | Running a collection task |
| R&D engineer | Upload and configure operators, maintain training templates, deploy models | Developing Operators · Tutorial A |
| Data owner | Define quality criteria and sign off on dataset versions | Data Workbench · Datasets and Versions |
Minimal Example: One Complete Loop
This example uses a registered Station Lite dual-arm workstation and an example task: placing a cube in a box.
- Create a collection task. Go to Data Collection → Collection Tasks and click New. Select device model
Station Lite, the device SN, and Full upload, then enter task namepick_place_demo, a target count of20, a collector, and a due date. - Collect and upload. The collector claims the task and records 20 demonstrations through teleoperation. Each episode uploads automatically when it ends and is stored as HDF5.
- Curate. In Data Assets, filter by the collection task
pick_place_demo, select all items, and create a curation project. In the data workbench, step through each episode, label failed grasps asAnomaly_grasp failed, mark those segments as excluded ranges, and review each episode. - Export a dataset. Click Export in the workbench and choose HDF5. This creates dataset version v1.
- Train a model. Go to Model Training → Task Management, click Create Training Job, select dataset v1, a model family, and a compute tier, then submit.
- Check direction early. While the job is running, export a checkpoint from the job details page; it is registered as a model.
- Deploy for inference. Go to Model Deployment → Inference Deployment, select the checkpoint model and target device, complete the safety confirmation, and start inference.
- Review feedback. Inference data flows back automatically. In Data Feedback, review the failure segments and add them to a curation project to prepare the next dataset version.
Teleoperation data vs. egocentric data
HDF5 data from Station Lite and MOS can be curated directly. RAW data from Robot-free Ego and Robot-free UMI must first be processed by a data pipeline.

