AuraOne / Documentation / Robotics Studio Open
Supported manifests. Synchronized review and failure clusters. Sensor QA and reviewed local exports.
Start with the bundled sample or your own JSON or JSONL manifest. The task guides cover review and export.
At a glance
Documentation entries
Choose a guide by dataset object, review task, or output.
Open the bundled sample or a local dataset, mark the failures, and export a reviewed subset on your own machine.
The core objects in Robotics Studio Open: datasets, episodes and clips, then the exports a reviewer approved.
The episode fields a Robotics Studio Open manifest declares: task, duration, frame rate, embodiment, outcome, review state, sensors and interventions.
Open the bundled sample or a supported JSON or JSONL manifest for local review.
Catch timestamp drift, dropped frames, and metadata gaps before export.
Review the failures that repeat. Recovery gaps, sensor desync, and brittle camera shifts.
What Robotics Studio Open exports: reviewed-subset manifests, sensor QA reports and local evidence archives with SHA-256 checksums.
Prepare teleoperation captures for local review through a supported manifest.
Local-first defaults. Path-based media references. Opt-in telemetry only.
Headless checks for manifest validation, dataset QA, and local handoff files.
Fix common Robotics Studio Open problems: missing local files, unsupported codecs, stale export paths and failed imports.
Guide structure
Every guide names its supported input and its output. It tells you what runs locally.
