Records
4
HF AUTHOR CLUSTER
4 robotics-tagged HF records from Traly, totaling 23,195 cumulative downloads. Some records cite published arxiv research.
DIRECT ANSWER
Author clusters consolidate every record from one publisher into a single buyer-review surface. Traly ships 4 robotics datasets on Hugging Face. Top license: apache-2.0. Of those, 4 get a full standalone page, 0 get a shorter profile, and 0 are folded into this cluster.
4
23,195
apache-2.0
DATASETS
4 of 4 datasets
Published Feb 2026 · apache-2.0 · Traly
RoboChallenge-lerobot-merged Note: The original dataset comes from RoboChallenge/Table30. This is an unofficial conversion to LeRobot v3.0 format. Dataset Description RoboChallenge benchmark dataset (merged version) in LeRobot v3.0 format.
Published Feb 2026 · apache-2.0 · Traly
RoboChallenge-lerobot Note: The original dataset comes from RoboChallenge/Table30. This is an unofficial conversion to LeRobot v3.0 format. Dataset Description RoboChallenge benchmark dataset in LeRobot v3.0 format.
Published Jan 2026 · apache-2.0 · Traly
Note This is an unofficial implementation. This dataset was converted from AgiBotWorld-Alpha into the LeRobot format using https://github.com/Tavish9/any4lerobot/tree/main/agibot2lerobot Configurations Each sub-task is available as a…
Published Apr 2026 · apache-2.0 · Traly
RoboTwin2.0 - LeRobot v3.0 RoboTwin2.0 converted to LeRobot v3.0 format. Contains both joint-space and end-effector (EE) pose data for bimanual manipulation across 5 robot embodiments.
KEEP DIGGING
A dataset record is only useful when it connects into the rest of the buyer workflow. The next review step is usually not another summary; it is a fit check, rights triage, source comparison, or custom bounty spec that names the missing proof.
For physical AI teams, the hard question is whether the public source can support a specific model objective under real deployment constraints. That requires adjacent dataset records, tools, comparisons, and sourcing paths, plus external references that a reviewer can open and challenge.
Use the links below to keep the review grounded. Start broad when discovery is incomplete, move into profile and comparison pages when the candidate source is known, and switch to custom collection when the blocker is rights, consent, geography, robot embodiment, or target environment coverage.
TRUELABEL ROUTING
If the Hub records don't carry the license, consent, or deployment fit your team needs, commission a custom collection on the same modality with explicit commercial terms.