- Rating
- 1
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
This paper asks whether a VLA deployment failure caused by a moved camera or a joint offset can be identified and repaired before rollout. The robot is used as its own calibration target: it moves to a few probe poses, and the camera or joint error is estimated by matching the arm silhouette. A score predicts whether the failure can be undone, and the repair is done by resetting the joints or reprojecting the image back to the training view. On LIBERO-Plus, the wrapper raises OpenVLA-OFT success under camera shifts from 0.58 to 0.76 and repairs most joint-offset cases.
Critical strengths
- The question is well motivated. Benchmark perturbation labels do not tell whether a failure can be fixed (e.g., a 20° orbit is recoverable while a 35° turn is not), and deciding this before rollout would be useful in deployment.
- Using the robot body as a calibration target to measure the nuisance and predict repairability is a good entry point, and the attempt to give a theoretical guarantee (the minimax floor on body-only calibration) is a nice idea.
Critical weaknesses
- The method section is hard to follow. Many components are introduced with little connection to the experiments, and it is often unclear which variant is used in which result. The theory is also not closed with the experiments.
- The experiments do not support the claims well. Related camera-robust VLA baselines (e.g., AnyCamVLA) are not compared. There is no sham control with the same probe motion but no reprojection. Each unit is evaluated with a single rollout, so the results are hard to reproduce. Some experiments do not show much: "repairing" all starting-pose failures by resetting to the training start pose just undoes the perturbation. In addition, one of the important meanings of the work should be repair before deployment, but no deployment in the real world is provided, which should not be a limitation.
- The central claim that most failures are "not the policy's fault" is largely a change of definition. A failure is attributed to the policy only if it persists under a perfect render from the training camera, i.e., the nominal condition, so this mostly restates the base success rate (as the paper itself acknowledges). Failing under a viewpoint change is itself a robustness problem of the policy. The paper uses an external wrapper to pull the input back to the training distribution rather than making the policy robust, which does not show that the policy has no deficit.
Questions for authors
- Can you run the sham wrapper (same probe motion, no reprojection)?
- How does the method compare with camera-robust VLA methods (e.g., AnyCamVLA)?
- Can you report results with multiple rollouts per unit?
- How does the theoretical bound relate to the observed repair outcomes?
- Why should a failure that is fixed only by restoring the training view not be considered a robustness failure of the policy?