Poke &Wiggle
Papers
Paper

ActionMap (50 demos per task)

ActionMap: Robot Policy Learning via Voxel Action Heatmap

Claim tested: ActionMap's voxel action heatmap head improves real-robot task success over OpenVLA-OFT's standard action regression head.

Tested

Paper
arXiv⁠ (opens in a new tab)
Code
GitHub⁠ (opens in a new tab)
Venue
—
Authors
Pei Yang et al.
Farm tasks
3
Evaluation
360 episodes (180 for baseline, 180 for method)

Result

Improvement over baseline

Replicated

Reported
+33 pts
Ours
+14 pts
−200+20+40+60
  • Gain vs baseline
  • 95% CI, +4 pts to +25 pts
  • Paper's reported gain
  • No difference

Success rate

Reported
47%
Ours
22%
0%20%40%60%80%100%
  • Measured on our stations
  • 95% CI, 15%–32%
  • Reported in the paper

Across iterations

  1. Iteration 1vs OpenVLA-OFT+14 pts
  2. Iteration 2vs OpenVLA-OFT+2 pts
−200+20+40+60

By task

TaskBaselineOpenVLA-OFTMethodActionMap (50 demos per task)Improvement
e01Clamp electrical component0%0/300%0/300 pts−11 to +11
e02Pour screws into the funnel3%1/3040%12/30+37 pts+16 to +55
e03Datum-corner alignment20%6/3027%8/30+7 pts−15 to +27
All tasks8%7/9022%20/90+14 pts+4 to +25
Reported in the paper13%47%+33 pts

Rollouts

One clip per environment from this entry's evaluation, beside where each evaluation episode placed the environment's objects, coloured by its rating. Use the button beside each environment to open its evaluation dataset in the dataset viewer.

  1. e02Pour screws into the funnel
  2. Held-out benchmark environment
    e01Clamp electrical component
  3. Held-out benchmark environment
    e03Datum-corner alignment

Implementation Details

What we changed

We replaced only OpenVLA-OFT’s L1 regression head with the paper’s voxel heatmap head, and trained both on the same 50 demonstrations per task with the paper’s real-robot recipe. Both heads match the official code. This round evaluates them on the station’s synchronous runtime. Differences from the paper:

  • Two arms and three cameras. Each step predicts 14 action values instead of 7, and ActionMap has one heatmap branch per arm on a shared trunk.
  • Delta actions on absolute targets. Both heads predict per-step deltas that are added to the measured pose, with normalization ranges fitted per chunk position. Rotations are rotation vectors instead of Euler angles.
  • Scarce data. Each task’s 50 training episodes are a fixed, seeded subset of the 276 to 288 available demonstrations, stratified by which arm moves.
  • Training budget. Both heads train for 4,000 steps at a constant learning rate of 5e-4 and batch 64, without a validation split.
  • Chunk timing and execution. Chunks are 16 steps at 30 Hz, about the paper’s 0.5 s horizon, and each chunk executes in full before the next request, as in OFT.
  • Evaluation. Each task runs 30 placements with one trial each, instead of the paper’s 10 trials.
  • Hardware. The pour pair trained on four A100s and the other pairs on four H100s, always the same within a task.

See the code changes on GitHub⁠ (opens in a new tab)

Prompt summary

Test whether ActionMap improves real-robot success over OpenVLA-OFT when demonstrations are scarce. Implement both, choose 3 tasks, train in the cloud and evaluate on stations. (Fixed 50-episode subset per task, the paper's recipe of 4,000 steps at constant LR 5e-4, sync runtime.)

Response summary

L1 vs ActionMap success: pour 1/30 (2580) vs 12/30, push 6/30 vs 8/30, clamp 0/30 vs 0/30; the agent reported SR +14.4 pp for ActionMap (95% CI 4.1 to 24.8) and AP +24.8 pp, driven almost entirely by pour.

Conclusion

ActionMap ahead on sync (+14.4 pp, mostly pour), but the training setup was later found flawed. Next: re-evaluate on blend.