Records
5
HF AUTHOR CLUSTER
5 robotics-tagged HF records from andreaskoepf, totaling 2,769 cumulative downloads.
DIRECT ANSWER
Author clusters consolidate every record from one publisher into a single buyer-review surface. andreaskoepf ships 5 robotics datasets on Hugging Face. Top license: apache-2.0. Of those, 5 get a full standalone page, 0 get a shorter profile, and 0 are folded into this cluster.
5
2,769
apache-2.0
DATASETS
5 of 5 datasets
Published Apr 2026 · apache-2.0 · andreaskoepf
DK-1 Merged Dataset This dataset was created using LeRobot. Dataset Description Merged and deduplicated DK-1 bimanual robot dataset. All source videos are re-encoded to 640x360 h264 with 14D joint-space actions.
Published Apr 2026 · apache-2.0 · andreaskoepf
This dataset was created using LeRobot. Dataset Description Place Lego Duplo bricks in a container Robot: TRLC DK1 bimanual (bi_dk1_follower) — 2× 6-DOF arms with grippers Task: place the duplo bricks in the container Episodes: 101 Total…
Published Apr 2026 · apache-2.0 · andreaskoepf
This dataset was created using LeRobot. Dataset Description Place Lego Duplo bricks in a container Robot: TRLC DK1 bimanual (bi_dk1_follower) — 2× 6-DOF arms with grippers Task: place the duplo bricks in the container Episodes: 106 Total…
Published Apr 2026 · apache-2.0 · andreaskoepf
This dataset was created using LeRobot. Dataset Description Place Lego Duplo bricks in a container Robot: TRLC DK1 bimanual (bi_dk1_follower) — 2× 6-DOF arms with grippers Task: place the duplo bricks in the container Episodes: 101 Total…
Published May 2026 · apache-2.0 · andreaskoepf
This dataset was created using LeRobot. Dataset Description Bimanual duplo disassembly demonstrations with DK1 robot Robot: TRLC DK1 bimanual (bi_dk1_follower) — 2× 6-DOF arms with grippers Task: separate the duplo bricks Episodes: 42…
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.