Solutions

Solutions.

Egocentric video, manipulation demonstrations, tactile data, and robot teleoperation.

Full-body ASCII illustration of the Tesla Optimus Gen 2 humanoid robot

Process

From model failure to a validated collection.

Datoric forms a hypothesis from a failure, tests collection methods, then records at scale while checking the method still holds.

01

Failure case

Datoric starts from a model failure or a capability target and finds the data reasons behind it.

Internal evaluator systems determine hypotheses on the reasons behind the failure and define collection experiments to test them.

What is formed

  • The failure, the evaluation set, or the stated capability
  • Hypotheses on the reasons behind the failure
  • Collection experiments defined to test those hypotheses
Copper ASCII illustration of a robot arm placing a cube on a target

02

Collection experiments

The defined collection experiments are run as side-by-side collections that change one method at a time.

Tests can change cameras, sensors, who demonstrates, the robot, how actions are recorded, objects, rooms, and labels. Video, motion, and tactile methods are tested on their own when the failure points there.

Each test uses the same tasks and the same mix of people, sites, and devices so the only change is the collection method.

What is compared

  • Side-by-side collections on the same task list
  • The same processing and evaluation for every test
  • Success measures agreed before recording starts
ASCII illustration of two NASA Robonaut robots working with tools

03

Validated collection

The method that works is then used for the full collection.

New recordings stay checked against the target model and the collection method that already worked. Datoric watches for drift as more hours, sites, and people are added.

Capture stays on the specification that held: specified robot, tasks, sensors, labels, and quality checks.

What continues

  • Full collection volume on the method that worked
  • Ongoing checks against the target model and collection method
  • Drift checks on capture, labels, and model results
ASCII illustration of a dexterous NASA Robonaut hand

Related datasets

Frequently asked

Questions

What is collected?

Egocentric video, manipulation demonstrations, and robot teleoperation. Tasks, equipment, labels, and quality checks are agreed before recording.

How does a collection start?

A hypothesis is formed from the failure or capability first. Collection methods are tested next. The method that works is then used for the full collection and checked for drift.

Can we review samples before a full delivery?

Yes. Request samples from the dataset page and specify the tasks and recordings to review.

Can data be collected on a specified robot?

Teleoperation collections are planned around a specified robot and task list. The number of recordings, sensors, control signals, and file format are agreed before collection.

Which training formats are available?

UMI data uses aligned Zarr episodes. Custom teleoperation collections can use LeRobot, Open X-Embodiment-compatible RLDS/TFRecord, HDF5, ROS bag, or an agreed custom format. Each dataset page lists its recording and delivery formats.

Plan a collection

Specify the robot, tasks, and file format.

Browse datasets