- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes ActionCritic, which adds a pre-execution self-check mechanism to StarVLA. Before grasping or releasing an object, the model re-observes the scene and judges whether the action is appropriate; if not, it generates a language correction and replans. Training uses four types of QA tasks to learn action understanding and error correction, with failed trajectories serving as negative samples. Experiments on SIMPLER, LIBERO, LIBERO-Plus, and real-world ALOHA tasks show gains of roughly 1–8 percentage points.
Critical strengths
- Checking before critical actions such as grasping and releasing prevents hard-to-recover errors early. Triggering only at key moments also avoids unnecessary computation.
- With the same backbone, data, and action representation as StarVLA, the method improves performance across model scales, simulation benchmarks, and real-robot tasks.
- Failed trajectories are used only to learn error recognition, not to imitate erroneous actions. Using a single model for action generation, verification, and correction also simplifies the architecture.
Critical weaknesses
- VLA-in-the-Loop already studies verification and correction before critical actions. Action Draft and Verify uses the VLA's internal capability to verify actions. VLAC unifies policy and critic in a single model. OneTwoVLA, RACER, and others also address self-correction and recovery. The paper should clearly explain its differences from these methods and compare against them empirically.
- There are missing key controls; the revierer is unclear why the method works. The results only show that adding ActionCritic improves performance. They do not answer three questions. Would simply letting the VLA re-observe and replan before critical actions work equally well? Is a shared critic better than a separate one? Is language correction actually necessary? Table 5 also omits the most important setting: zero corrections. These controls bear directly on the core contribution. Moreover, unlimited corrections yield the highest success rate in Table 5, suggesting that simply retrying more contributes substantially.
- The method uses extra QA supervision, failed trajectories, and VLM-generated correction labels. The current experiments cannot separate gains due to the self-check mechanism from gains due to the additional supervision.
- The paper claims that sharing one model reduces overhead, but it does not clearly report critic inference time or compare against a separate critic. The current latency results are insufficient to support the efficiency claims.
Questions for authors
Please address my comments above, especially:
- Would simply letting the VLA re-observe and replan before critical actions work equally well?
- Is a shared critic better than a separate one?
- Is language correction actually necessary?