vla-evaluation-harness

repository·main·Indexed 19 days ago

https://github.com/allenai/vla-evaluation-harness

A unified framework for evaluating Vision-Language-Action (VLA) models across various robot simulation benchmarks. It utilizes a model-server/benchmark-client architecture to decouple models from environments. Supported benchmarks include BEHAVIOR-1K, CALVIN, DuoBench, Kinetix, LIBERO (including Mem, Plus, and Pro versions), ManiSkill2, Mikasa, MolmoSpaces-Bench, RLBench, and RoboCasa.

Tokens
82.3K
Snippets
177
Records
355
Agent score
66%

What's inside vla-evaluation-harness

  1. Overview of RoboCasa365 Benchmark

    main

    RoboCasa365 is a multi-task kitchen manipulation benchmark built on MuJoCo and robosuite. It evaluates models on 50 target tasks across three categories: atomic_seen, composite_seen, and composite_unseen in pretrain kitchens.

    Important Note: This implementation uses a specific Docker image that pins RoboCasa 1.0.1 and robosuite 1.5.2. Because this is a separate integration from the original RoboCasa repository, scores are not directly comparable across the two.

  2. Overview of RLinf Distributed RL Infrastructure

    main

    RLinf is a distributed reinforcement learning (RL) infrastructure designed to train Vision-Language-Action (VLA) models (such as Pi0, OpenVLA, and GR00T) using algorithms like PPO, GRPO, and SAC. It utilizes a Ray-based scheduler and NCCL collective communications for distributed scaling.

    Key technical details:

    • Purpose: Scaling RL training for VLA models.
    • Core Technologies: Ray (scheduling), NCCL (collective communication).
    • License: Apache License 2.0.
    • Reference for vla-evaluation-harness: The rlinf/envs/ structure is a key reference point for designing environment wrappers.
  3. Overview of vla-eval Reproductions

    main

    The vla-eval harness provides systematic verification of Vision-Language-Action (VLA) model scores across various codebases and benchmarks. It compares reproduced scores against originally reported scores to ensure consistency.

    Reproduction Status Key

    • ✅: Reproduced within 95% Confidence Interval (CI).
    • 🟡: Reproduced outside CI but within 5 percentage points (pp).
    • 🔧: In progress or reproduction error > 5pp with a known cause.
    • ⬜: Not attempted.
    • ·: No score or no checkpoint available.

    Note: CI is binomial at p=0.95 (±1.9pp for 500 episodes).

  4. OpenEnv Architecture Overview

    main
    OpenEnv is an end-to-end framework for creating, deploying, and using isolated execution environments for LLM agents. It utilizes a client-server architecture that combines a Gymnasium-style API with WebSocket communication and Docker isolation. The framework is designed to provide environments via a client-server model where the environment runs in a container and the agent interacts with it through a client.
  5. RoboChallenge Benchmark Overview

    main

    RoboChallenge is an external benchmark for large-scale real-robot evaluation of embodied policies.

    Key Details:

    Important Note for Developers: This benchmark is marked as external_only. The vla-evaluation-harness does not mirror these results locally. The leaderboard.json file in this repository must contain zero rows for this benchmark. A previous API mirror was retired in July 2026.

  6. What is Real-Time Evaluation and why use it?

    main

    Traditional VLA benchmarks are synchronous, meaning the simulation environment pauses while the agent is performing inference. This does not reflect real-world robot deployment, where slow inference can lead to failures as the environment continues to change.

    vla-evaluation-harness introduces Real-Time Evaluation mode, where the environment time flows independently of the agent's execution. This allows developers to:

    • Quantify the impact of inference speed on task success rates.
    • Analyze the trade-offs between inference speed and action chunk sizes.
    • Compare performance between synchronous and real-time modes for models like CogACT, Pi0, and OpenVLA.
  7. Understand ManiSkill2 benchmark scoring and task subsets

    main

    The ManiSkill2 benchmark evaluates models using the success_rate metric (0-100%).

    Standard Task Set

    To ensure comparability and enable a sortable overall_score, models must be evaluated on the standard 5-task set:

    • PickCube
    • StackCube
    • PickSingleYCB
    • PickSingleEGAD
    • PickClutterYCB

    Scoring Logic

    • overall_score: This is the arithmetic mean of the 5 standard tasks listed above. If a model uses a different subset of tasks, the overall_score must be set to null.
    • task_scores: This object contains the per-task success rates. Keys must match the PascalCase task names exactly (e.g., PickCube, OpenCabinetDoor).
    • suite_scores: Not used for ManiSkill2.

    Important Comparison Note

    Task subsets vary significantly across different papers. Because different subsets are used, scores across different task subsets are not directly comparable. Only entries using the standard 5-task set are ranked in the leaderboard.