
LeRobotDataset to fix that: one standardized format (Parquet for state and action, MP4 for camera feeds) across radically different embodiments, from SO-100 arms to bimanual ALOHA rigs to industrial Kuka arms.lerobot-tagged datasets on the Hub, and that alone lifted SO-100 task success from 51.7% to 78.3% (source). The format itself had to evolve under that success: the original v2.x layout stored one Parquet file and one MP4 per episode, which started hitting filesystem limits once community datasets reached millions of episodes. lerobot v0.4.0 shipped v3.0 in response, packing many episodes into shared chunked files and supporting streaming without a full download first.fo.types.LeRobotDataset as a first-class import path, built around one idea: a sample is an episode, not a file. The fiftyone-lerobot-import agent skill wraps that native support with the parts a script usually skips: detecting whether a Hub dataset is still on v2.x, running the documented conversion before import, and refusing to create a dataset or install a package without asking first.meta/episodes.jsonl, meta/tasks.jsonl) and runs the documented conversion to v3.0 before importing, instead of failing on an unsupported-version error.lerobot/aloha_sim_insertion_human, a real v2.1-tagged Hub dataset, which converted to v3.0 and imported as 50 episodes of a bimanual ALOHA arm with zero episodes skipped.fo.Dataset.from_dir, dataset.add_dir), so the same import runs identically from a chat prompt or a checked-in script.curl -sL skil.sh | sh -s -- voxel51/fiftyone-skillsfiftyone-lerobot-import. Point it at a local LeRobot directory or a Hugging Face Hub repo id, and it detects the version, converts if needed, and builds the FiftyOne dataset. That’s a different problem from the one fiftyone-dataset-import’s MCAP path solves. MCAP’s question is a schema scan: what kind of sensor data is this? LeRobot’s question is about versioning: what version of this format is this, and does it need conversion first?lerobot/aloha_sim_insertion_human is one of LeRobot’s official example repos: a bimanual ALOHA arm running a simulated peg-insertion task, one task label (“Insert the peg into the socket.”), 50 episodes, 50 fps, 25,000 total frames.| Detail | Value |
|---|---|
| Repo | lerobot/ |
| Revision pulled | v2.1 |
| Episodes | 50 |
| FPS | 50 |
| robot_type | aloha |
| Camera | observation |
| observation | 14 / 14 (bimanual: waist, shoulder, elbow, forearm roll, wrist angle, wrist rotate, gripper, same layout on both arms) |
| Task | “Insert the peg into the socket.” |
v2.1 tag specifically, not main (already v3.0), so the conversion path would get exercised for real instead of simulated.lerobot/aloha_sim_insertion_human into FiftyOne.meta/info.json and finds codebase_version: v2.1, along with layout markers like meta/episodes.jsonl and meta/tasks.jsonl. Instead of failing on unsupported versions, the skill detects the older format, hits the packages stop gate, and runs the conversion script (python-m lerobot. scripts. convert_dataset_v21_to_v30) to update the dataset to v3.0, ensuring reliable import even with legacy data.lerobot (needed only for the conversion).python -m lerobot.scripts.convert_dataset_v21_to_v30 --repo-id lerobot/aloha_sim_insertion_human --root <path> --push-to-hub=false.lerobot.datasets.v30.* module path; it was still at the older lerobot.scripts.* path. The skill’s own troubleshooting notes already anticipate this exact fallback, and it’s what happened on the first real run, not a hypothetical edge case.meta/info.json, confirms codebase_version: v3.0, and the new layout: meta/episodes/chunk-000, meta/tasks.parquet, meta/stats.json.LeRobot Import Plan for lerobot/aloha_sim_insertion_human:
Source:
- codebase_version: v3.0 (converted from v2.1: yes)
- 50 episodes, 50 fps, robot_type: aloha
- camera: observation.images.top (video, av1)
- observation.state: 14 dims, action: 14 dims
- tasks: 1 ("Insert the peg into the socket.")
Import:
- Dataset name: lerobot-aloha-sim-insertion-human
- Episodes: all
- Persistent: yes
Proceed with import? (yes/no)dataset.media_type comes back "multimodal". All 50 episodes import; dataset.info["lerobot"]["skipped_episodes"] is an empty list: a clean import, worth stating plainly rather than manufacturing a gap that isn’t there. Every episode runs exactly 10 seconds (dataset.bounds("duration") returns (10.0, 10.0)), which checks out at 50 fps × 500 frames/episode.observation.images.top tile: two robot arms working over a blue and red object, with the episode header reading “Insert the peg into the socket. · 10s.” That’s what “one sample equals one episode” looks like in the viewer, not an abstraction: a single click surfaces the whole 10-second demonstration, not one video frame.pip install "pyarrow>=10.0.0" huggingface_hub lerobotlerobot is only needed for the v2.1 → v3.0 conversion below. A dataset already on codebase_version: v3.0 only needs pyarrow and huggingface_hub.fo.Dataset.from_dir reads from a local directory, not directly from the Hub, so pull the files down first:
from huggingface_hub import snapshot_download
local_dir = snapshot_download(
repo_id="lerobot/aloha_sim_insertion_human",
repo_type="dataset",
revision="v2.1",
local_dir="/abs/path/lerobot/aloha_sim_insertion_human",
)python -m lerobot.scripts.convert_dataset_v21_to_v30 \
--repo-id lerobot/aloha_sim_insertion_human \
--root /abs/path/lerobot/aloha_sim_insertion_human \
--push-to-hub=falsev3.0 on the Hub; for example, pull revision="v3.0" in Step 2 instead.import fiftyone as fo
dataset = fo.Dataset.from_dir(
dataset_dir=local_dir,
dataset_type=fo.types.LeRobotDataset,
name="lerobot-aloha-sim-insertion-human",
persistent=True,
)
assert dataset.media_type == "multimodal"
fo.launch_app(dataset)dataset.add_dir(dataset_dir=..., dataset_type=fo.types.LeRobotDataset) instead of from_dir.meta/info.json and meta/episodes/*.parquet, nothing in the video files, so it stays fast even on large sources. The skill’s stop gates are a conversation; the SDK calls underneath are the same ones either way.fiftyone-lerobot-import turns that check into something an agent already knows how to run correctly against your files, every time.lerobot/aloha_sim_insertion_human, part of LeRobot’s official example datasets, Hugging Facevoxel51/fiftyone-skills, installed the same one-line way as Part Onefiftyone-lerobot-import skill, or call fo.Dataset.from_dir(..., dataset_type=fo.types.LeRobotDataset) directly. Both require the dataset to be on codebase_version: v3.0.fo.types.LeRobotDataset only supports v3.0. v2.x sources need conversion first.pyarrow>=10.0.0.media_type == "multimodal" and fields like episode_index, task, duration, and fps.dataset.info["lerobot"]["skipped_episodes"] instead of being silently dropped or silently accepted.
© 2026 Voxel51 All Rights Reserved


