robocurve/cubepick-reach
The reach-the-cube world from inspect-robots.
bench eval run \
-d robocurve/cubepick-reach@0.1 \
--registry https://robouse.ai/hub/registry.json \
--agent oracleAbout this dataset
- Embodiment
- Point end effector in the unit square
- Simulator
- inspect-robots CubePick (numpy)
- Requirements
- CPU only ·
bench>=0.7.4,<0.8 - Licence
- Task packages Apache-2.0; adapted from inspect-robots cubepick-reach by Robocurve, MIT
@misc{robouse_robocurve_cubepick_reach_0_1,
title = {Robo Use robocurve/cubepick-reach 0.1},
author = {{BenchFlow}},
year = {2026},
howpublished = {\url{https://robouse.ai/hub/robocurve/cubepick-reach/}},
note = {BenchFlow dataset, tag robocurve/cubepick-reach-v0.1, commit 8e777592c151; adapted from inspect-robots cubepick-reach (Robocurve)}
}5 tasks
cubepick-reach-layout-0A point end effector moves in the unit square (x from 0 to 1, y from 0 to 1). It starts at (0.1, 0.1); a cube lies somewhere in the far quadrant…A point end effector moves in the unit square (x from 0 to 1, y from 0 to 1). It starts at (0.1, 0.1); a cube lies somewhere in the far quadrant (both coordinates between 0.6 and 0.9). This is inspect-robots' built-in cubepick-reach benchmark, layout 0.
Point end effector in the unit square80 stepsends when first reached
cubepick-reach-layout-1A point end effector moves in the unit square (x from 0 to 1, y from 0 to 1). It starts at (0.1, 0.1); a cube lies somewhere in the far quadrant…A point end effector moves in the unit square (x from 0 to 1, y from 0 to 1). It starts at (0.1, 0.1); a cube lies somewhere in the far quadrant (both coordinates between 0.6 and 0.9). This is inspect-robots' built-in cubepick-reach benchmark, layout 1.
Point end effector in the unit square80 stepsends when first reached
cubepick-reach-layout-2A point end effector moves in the unit square (x from 0 to 1, y from 0 to 1). It starts at (0.1, 0.1); a cube lies somewhere in the far quadrant…A point end effector moves in the unit square (x from 0 to 1, y from 0 to 1). It starts at (0.1, 0.1); a cube lies somewhere in the far quadrant (both coordinates between 0.6 and 0.9). This is inspect-robots' built-in cubepick-reach benchmark, layout 2.
Point end effector in the unit square80 stepsends when first reached
cubepick-reach-layout-3A point end effector moves in the unit square (x from 0 to 1, y from 0 to 1). It starts at (0.1, 0.1); a cube lies somewhere in the far quadrant…A point end effector moves in the unit square (x from 0 to 1, y from 0 to 1). It starts at (0.1, 0.1); a cube lies somewhere in the far quadrant (both coordinates between 0.6 and 0.9). This is inspect-robots' built-in cubepick-reach benchmark, layout 3.
Point end effector in the unit square80 stepsends when first reached
cubepick-reach-layout-4A point end effector moves in the unit square (x from 0 to 1, y from 0 to 1). It starts at (0.1, 0.1); a cube lies somewhere in the far quadrant…A point end effector moves in the unit square (x from 0 to 1, y from 0 to 1). It starts at (0.1, 0.1); a cube lies somewhere in the far quadrant (both coordinates between 0.6 and 0.9). This is inspect-robots' built-in cubepick-reach benchmark, layout 4.
Point end effector in the unit square80 stepsends when first reached
↑ ↓ move between rows · Enter shows details · O opens the task
Each task is a package in the task format, pinned to robohub commit 8e777592c151. The verifier and the reference solution are not published.