CERES user guide

Review and export a completed run

ResultsUpdated 2026-08-08

CERES exports accepted completed cycles with sensor frames and task-segment metadata. Pauses and reset windows are context, not separate captured tasks.

Review before exporting

Use the monitor's EPS list to confirm the final cycle has arrived. Review the outward video, hand overlays, gap count, maximum hand speed and tracking-loss information while the action is still fresh.

RETRY means the current attempt failed. The retry replaces that attempt for the task rather than adding it as a retained recorded repetition. Use it before the reset window closes.

Export locally

Choose a local folder when the dataset should stay on the research workstation or be handed to a controlled storage process. CERES keeps the run available until the export has completed.

Export to Hugging Face

For a signed-in account, CERES prepares the dataset, uploads it and commits it to the selected repository. The visible stage continues from storage writing through reading, hashing, upload and commit. Large commits may take time at Hugging Face, but account reconciliation and commit verification continue in the background after the request is durable.

If an upload needs attention after a browser reload, the Solo page shows it above the configuration steps. You can wait for it, resume the rest of the setup or abort the upload.

What a completed dataset contains

Each accepted episode carries the task instructions, cycle and repetition context, outward media, headset pose, hand joints, durable gap records and quality information. The viewer lets you inspect this material without modifying the capture. Read Data description and output format when you need the exact dataset layout and provenance fields.