Evaluation protocol

Evaluation

Three levels. One physical contract.

DexArena separates failures in execution, generalization, and composition while preserving matching task definitions.

01Stage level

Skill execution

Run each of the 30 canonical stage environments with its registered robot, horizon, action layout, and physical success predicate.

  • Success rate across fixed seeds
  • Persistent success, not transient contact
  • 29-D single-arm or 58-D bimanual actions
02Scene level

Visual generalization

Evaluate every stage on three native scene surfaces using identical object placement and the fixed 256 × 256 policy camera rig.

  • 90 task × scene combinations
  • Shared seeds across algorithms
  • Saved background manifest
03Sequence level

Skill composition

Execute two to five dependent stages in their parent long-horizon environment and report complete-sequence success.

  • Stage progress and terminal success
  • Inherited state between stages
  • Single-arm and bimanual tasks
Metric contract

Report the failure mode, not only the final number.

Stage Success Rate

Fraction of evaluation episodes whose stage predicate is satisfied for its required hold duration.

Cross-scene Average

Mean stage success over robocasa_l3_s2, robocasa_l3_s1, and robocasa_l3_s6 with matched seeds.

Generalization Gap

Difference between the reference collection workspace and native-scene performance.

Composition Rate

Fraction of complete long-horizon episodes reaching the final task success state.

Paper protocol

Fifty episodes. Three distinct questions.

All six baselines use image observations and robot proprioception, with matched task horizons, randomization and embodiments. Stage and long-horizon success are measured over 50 episodes per task; generalization uses 50 episodes in each of three held-out kitchens without further adaptation.

01

Recorded evaluation seeds

The manuscript specifies stage seeds 50000–50049 for ACT and DP. GR00T uses 10001–10050, reused for each generalization scene and the long-horizon protocol. Record the seed manifest alongside each result.

02

Scene-level uncertainty

Generalization reports mean ± standard deviation across three scenes. The average row aggregates stage performance within each scene before reporting variation across scenes.

03

Transitions without resets

PPO, RLPD, ACT, DP and π0.5 switch between learned stage policies when the stage succeeds. GR00T uses one task model trained on pooled stage data, with a new instruction at each transition.

01 / 30 stages · training scene

Strong individual skills.

GR00T records the highest average success in the training scene. ACT and RLPD follow, but no method consistently solves every stage.

+3.4 ppadvantage over ACT
Stage-level results
Average success by policySuccess (%) · 0–100
  1. GR00T61.4 percent success
  2. ACT58.0 percent success
  3. RLPD54.3 percent success
  4. π0.552.1 percent success
  5. Diffusion Policy39.2 percent success
  6. PPO27.9 percent success

50 evaluation episodes per stage. Scores are averaged over 30 canonical stages.

02 / 30 stages × 3 native scenes

A different scene changes the ranking.

π0.5 leads across three held-out kitchens. Its average is 2.9 percentage points below the training-scene result; the same policy is evaluated without adaptation.

+3.8 ppadvantage over ACT
Cross-scene results
Average success by policySuccess (%) · 0–100
  1. π0.549.2 ± 2.3 percent success
  2. ACT45.4 ± 3.6 percent success
  3. GR00T41.7 ± 14.2 percent success
  4. PPO21.7 ± 3.5 percent success
  5. RLPD17.8 ± 10.9 percent success
  6. Diffusion Policy17.2 ± 5.7 percent success

50 episodes per stage per scene. ± denotes standard deviation across three scene averages, not a confidence interval.

03 / 10 sequences · no stage resets

The sequence remains the challenge.

π0.5 and ACT report non-zero average success on complete sequences. Successful individual stages do not yet translate into reliable end-to-end behavior.

2 / 6methods with non-zero sequence success
Complete-sequence results
Average success by policySuccess (%) · 0–100
  1. π0.51.6 percent success
  2. ACT1.2 percent success
  3. PPO0.0 percent success
  4. RLPD0.0 percent success
  5. Diffusion Policy0.0 percent success
  6. GR00T0.0 percent success

50 episodes per complete task. Success requires reaching the final task condition without resets between stages.

Manuscript baseline results · 6 methods · Not a live submission rankingHow to read these results ↗
Explore all results↗
Reproducibility

What an evaluation record should contain.

  1. Environment identityExact env ID, task source fingerprint, robot UID, control mode, horizon, and seed.
  2. Observation contractState layout, camera rig, image size, preprocessing, and language-instruction version.
  3. Scene manifestBackground ID, native table metadata, camera configuration, and reset-time checks.
  4. EvidencePer-episode success, stage trace, videos, aggregate table, and checkpoint provenance.