LeRobot Dataset Export

Dataset bridge

The LeRobot lane is a dataset-profile example, not a second runtime path. It shows how Golden event streams can become dataset-friendly records while preserving the original timing, source, and conversion metadata.

Run the bridge

pixi run demo-robotics-lerobot-bridge

Expected result: the command prints canonical rows, LeRobot-style records, and round-trip rows so you can verify conversion without a real dataset upload.

InputCanonical rows

Small Golden event records with explicit event time, source, and lineage.

ExportLeRobot records

Dataset-friendly rows that preserve the robot payload boundary.

CheckRoundtrip rows

A local conversion proof before any heavy dataset pipeline or cloud storage enters the loop.

Output To Recognize

Canonical rows: 2
LeRobot records: 2
Roundtrip rows: 2
Sample record:
  {...}

The exact payload values can change as examples evolve, but those four labels should stay stable: source rows, exported rows, round-trip rows, and one inspectable record.

What It Demonstrates

Typed source payloadsStart from Golden robot payloads before conversion.

Dataset profileMap event records into fields expected by an offline dataset consumer.

Lineage retentionPreserve timing, source, and conversion details for debugging.

Keep The Boundary Small

Keep here	Keep out of first-run docs
Small local conversion example.	Heavy dataset generation.
Event-time and source metadata preservation.	Cloud upload, private storage, or credential setup.
Public payload/profile contract.	Robot-lab-specific capture procedures.

Keep this bridge lightweight. It should make the export shape clear before any large dataset pipeline grows around it.