Capture a run in Solo

Solo puts the run editor, camera setup and capture controls on one device. It records through the same durable journal as paired capture.

Configure the run

1. Open Launch > Solo.
2. Choose local storage or Hugging Face as the destination.
3. Select the camera, create or open the run and specify its tasks.
4. Start a task only after the capture setup reads ready.

When Hugging Face is selected, choose the account and repository. A recognised repository name is normalised to the name after the slash, so research-team/reach-study becomes reach-study in the repository field instead of duplicating the account name.

Resume or reset

If a capture is still present, the task panel shows Resume rather than silently resetting the run. Resume preserves the unfinished capture and enables Open XR. Reset is for deliberately discarding that unfinished local state before a new run.

Leaving XR pauses the capture. It does not delete it. Return to Solo, confirm the pending run and resume when the scene is ready again.

Use Hugging Face without waiting for finalisation

Hugging Face sign-in, repository checks and an older upload reconciliation run separately from capture controls. You can continue configuring the run while status checks finish. A previous upload appears in its own banner before it completes, with an abort action when you do not want it to continue.

Once a capture ends, CERES shows the active stage: writing to headset storage, reading, hashing, uploading or committing. The finalisation request is saved before background processing begins, so the capture interface does not remain blocked while Hugging Face verifies a large dataset.

Abort an upload

Use the abort control next to an active or recovered upload only when you intend to stop publishing that dataset. Aborting the upload does not erase the local capture automatically.

Read Setup and system requirements before a first Solo run and Review and export a completed run before choosing a destination for research data.