Robo Use

Find a pawn in camera images and land it on a gold-outlined square (ALOHA 2)

menagerie-aloha-pawn-landing-visionMenagerieALOHA 2ManipulationVisionhard

Reference solution, 280 of 600 steps.

Instruction

An ALOHA 2 bimanual rig: two ViperX 300 arms (6 joints each, with parallel-jaw grippers that open to about 7 cm) are mounted side by side at the back edge of a 1.6 m x 0.94 m desk, both reaching forward toward you. The "left" arm is the one at negative x (on the left in the front camera view), the "right" arm the one at positive x. This is a MuJoCo physics simulation with the MuJoCo Menagerie robot models: every object is a free rigid body that moves only through contact and friction (nothing is attached or teleported), so a loose grip, a fast swing or a collision can drop or knock things over. World frame in metres: +x to the right, +y toward the robots (the back of the desk), +z up; the desk top is z = 0.

Goal: A light chess pawn (6 cm tall; base disc 2.6 cm across, a 1.8 cm stem, round crown) stands in the left bowl (a shallow dish 28 cm across with a 3 cm rim). Move it onto the square outlined in gold on the chessboard, standing upright, and let go. Where the pawn is is not given as numbers: find it in the camera images.

Success: The pawn's base centre is within 12 mm of pad_center, its base rests on the board (within 4 mm of z = 0.0102), it is tilted at most 10 degrees, released and at rest. Success is judged by the episode server from the physical state after you call robo done and the robots have held still for about 10 steps (0.5 s). "Released" means neither arm touches the object; "at rest" means it moves slower than 1 cm/s.

Goal fields in robo observe: pad_center (centre of the gold square on the board top) and pad_half_size (0.02 m).

Controls. You drive the left arm only (the other arm stays parked). robo act DX DY DZ GRIP moves the arm's commanded gripper target by DX, DY, DZ times 2 cm per step along world x, y, z (each in [-1, 1], so 0.25 = 5 mm); GRIP 0 keeps the fingers as they are, any positive value closes them, and a negative value -f opens them to fraction f of full width (-1 fully open, -0.4 = 40 % open). One step is 50 ms of simulated time. Inverse kinematics turns the target into joint commands; the gripper always points straight down. robo move-to X Y Z and robo grip G drive the same arm (move-to stops within --tol metres of the point, default 0.01).

Observation. robo observe reports, for each arm you drive, hand_pos (the measured point between the fingertips), hand_target (where the arm is being driven; it can run up to 5 cm ahead of the hand, which then catches up), gripper_open (0 closed .. 1 fully open) and touching (task objects in contact with that arm); plus the goal fields listed above (object poses are not reported).

Observation mode: vision. robo observe does not report where the task objects are. It returns only the fields listed in robo info (the robot's own state, touching, and the goal fields) and saves one image per camera, printing their paths: workspace (a front view from above the desk edge) and top (straight down; +x to the right and +y, the robots' side, at the top of the picture). Open them to look. robo info gives each camera's 3x4 projection matrix P, with [u*w, v*w, w] = P @ [x, y, z, 1] in the saved image's pixels (v down), so you can relate what you see to world coordinates. The arms can hide things from a camera; move them out of the way to look.

The step budget is 600 steps (30 s of simulated time).

How the robot is controlled and scored

You are controlling a simulated robot. Read the task below, then solve it by running the robo command in your shell (start with robo info and robo observe). Keep going until the task is done, then call robo done once. Do not stop to ask questions; there is no human to answer.

How to control the robot

You are the robot's policy. You act only through the robo command in your shell. There is no other way to move the robot, and you cannot read or change the simulator, the scoring, or other files to succeed; the episode server judges the final physical state itself.

robo info                         # action space, available skills, step budget
robo observe                      # robot and object state as numbers
robo observe --image              # also saves a camera image and prints its path (open it to look)
robo act DX DY DZ GRIP [--repeat N]   # low-level action, applied N times (N <= 50)
robo move-to X Y Z [--grip G]     # skill: move the gripper toward a point (if enabled for this task)
robo grip G [--steps N]           # skill: hold position and set the gripper (+1 close, -1 open)
robo done "short summary"         # end the episode and ask for scoring
robo give-up "reason"             # end the episode without claiming success
  • Positions are in metres in the world frame (x, y on the table plane, z up).
  • The episode has a fixed step budget (see robo info); every simulated step counts, including skills.
  • Unless the task says otherwise, success is judged about 10 steps after you call robo done, with the robot holding still, so the goal must still be true when the robot stops.
  • Work in small steps and re-observe after each motion. Call robo done exactly once when finished.

Run this task

bench eval run \
  -d benchflow/robouse-menagerie@0.1 \
  --registry https://robouse.ai/hub/registry.json \
  --agent oracle \
  --include menagerie-aloha-pawn-landing-vision

Pinned to robohub commit 9e672aa1e7f0. The verifier and the reference solution are not published.

Trial
GPT-6 Astra · CodexSolved332 / 6002 minTrial Compare
Kimi K3 · mini-swe-agentSolved269 / 60013 minTrial Compare
GLM-5.3 · mini-swe-agentSolved228 / 60010 minTrial Compare
GLM-5.3 · Claude CodeSolved425 / 60011 minTrial Compare
Kimi K3 · Claude CodeNot solved335 / 6004 minTrial Compare
GLM-5.3 · CodexInfra failure0 / 6009 sTrial Compare