Rule inference: sizes
arc-stack-by-size-visionvision variantVisionFloating gripperRule inferenceVisionmedium
Instruction
Vision variant
This is the vision version of the task. robo observe does not give object or goal positions: you get only the robot's own state (hand_pos, gripper_open, holding, examples, grid, constraint_violations) and two camera images (front, top), saved on every robo observe and printed as paths. Open the images to see the scene. robo info lists each camera with a 3x4 projection matrix P: for a world point (x, y, z), [u*w, v*w, w] = P @ [x, y, z, 1] gives its pixel (u, v) in that camera's saved image (u to the right, v down, origin at the top-left). With two cameras you can triangulate a point you see in both, or intersect a pixel's ray with a known height. Any field names in the description below that are not in your observation are hidden in this variant.
A two-finger parallel gripper hangs over a table (a floating gripper, no arm). The camera looks at the table from the front: x points to the right, y away from the camera (toward the back of the table), z up; the table top is at z = 0. The fingers close along the y axis.
Goal: Coloured blocks stand on a grid of cells marked on the table. The observation field examples holds demonstrations of a hidden rule: each shows an arrangement of coloured blocks on a grid of the same shape before and after the rule was applied (cells are [row, col], row 0 = back row, col 0 = left column). Work out the rule from the examples and apply it to the blocks in front of you by moving them. Some examples mention extra items (spare blocks off the grid, pads, a marker, block sizes); these correspond to the same kinds of items in your scene. Blocks of the same colour are interchangeable. Only the final arrangement is judged; blocks must be released and resting on the table.
What robo observe shows
hand_pos: the gripper's tool point (between the fingertips), metres.gripper_open: 0 = closed, 1 = fully open (10 cm gap).holding: names of objects currently touching the fingers.objects: every movable object by name, withkind,color,pos(centre, metres),size(full x/y/z extent in its own frame),yaw_deg,half_height(current half extent along z),tilt_deg(0 = upright), andcell([row, col]or null when off the grid).fixtures: static things by name (pads, bowls, trays, plates, sockets, the drawer cabinet) with their positions and sizes. Pads are flat coloured squares on the table; bowls and trays have afloor_zand arim_z.grid: rows, cols,cell_sizeand the centre of every cell (cell_centers[row][col]). Row 0 is the back row, col 0 the left column.examples: the before/after demonstrations described above.
Gripper
The grip value is a finger position target, not a hold command: +1 = fully closed, -1 = fully open (10 cm gap), and values in between give a partial opening (finger gap = 10 cm * (1 - G) / 2, so 0 = half open, a 5 cm gap). There is no separate "hold" value: to keep holding an object, keep sending +1 (the fingers then squeeze it). robo move-to X Y Z --grip G applies G on every step of the move, starting with the first, so --grip 1 closes the fingers at the start of the move (they take about 15 steps to close fully); without --grip, the last grip value is kept. robo grip G --steps N holds the hand still for N steps while applying G. The same values apply to the GRIP argument of robo act.
Objects must be released (not touching the fingers) when the episode is judged.
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 doneexactly once when finished.
Run this task
bench eval run \
-d benchflow/robouse-tabletop@0.1 \
--registry https://robouse.ai/hub/registry.json \
--agent oracle \
--include arc-stack-by-size-visionPinned to robohub commit 9e672aa1e7f0. The verifier and the reference solution are not published.
| Trial | |||||
|---|---|---|---|---|---|
| GPT-6 Astra · Codex | Solved | 400 / 800 | 2 min | Trial Compare | |
| Kimi K3 · Claude Code | Solved | 373 / 800 | 4 min | Trial Compare | |
| Kimi K3 · mini-swe-agent | Solved | 403 / 800 | 4 min | Trial Compare | |
| GLM-5.3 · mini-swe-agent | Solved | 612 / 800 | 5 min | Trial Compare | |
| GLM-5.3 · Claude Code | Solved | 412 / 800 | 6 min | Trial Compare |
No model matches.Clear the filter or change the models in the comparison set.