- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper proposes ProgPrune, a training-free visual token pruning framework for vision-language-action models. A deterministic instruction parser and an execution-feedback tracker identify the active subtask and phase, which determine the instruction spans used to guide token selection. The method combines active-context guidance with a full-instruction reserve, refreshes relevance scores using current-layer Q/K projections, and applies motion-dependent pruning schedules. Experiments evaluate task success and computational efficiency across multiple manipulation benchmarks and VLA backbones.
Critical strengths
Controlled experiments provide useful support for the proposed design. Under the same configured pruning schedule, combining active-context and full-instruction guidance improves LIBERO-Long success from 92.0% to 94.2% compared with full-instruction-only scoring. The appendix further reports switching accuracy, paired interventions, and uncertainty estimates, providing useful evidence about the progress mechanism. Complete action-call measurements also show practical speedups in several settings.
Critical weaknesses
-
The broader benefit of progress-aware pruning is insufficiently established. Table 10 shows that CALVIN never enables the progress tracker, so its results cannot establish the benefit of internally tracked progress. On RoboCasa365, complete action-call latency is essentially unchanged relative to the dense policy, while success decreases from 57.72% to 51.16%. These results limit the evidence for the central mechanism and its practical value in long-horizon manipulation.
-
The independent novelty of Fresh-QK is not sufficiently clear. ADP already uses text–visual QK relevance scores, and SpecPrune-VLA updates token importance across decoder layers. The Fresh-QK ablation supports its usefulness, but the additional methodological insight beyond progress-conditioned text selection remains unclear.
Questions for authors
-
Attribution of long-horizon gains. Given that CALVIN never enables progress tracking, which components account for its improvements? What evidence isolates the benefit of internally tracked progress beyond LIBERO-Long?
-
Practical efficiency on compositional tasks. What explains the essentially unchanged complete action-call latency on RoboCasa365 despite reduced analytical FLOPs? Given the accompanying success-rate decrease, what evidence supports a favorable measured performance–latency trade-off in this setting?
-
Contribution of Fresh-QK. What is the new methodological insight in Fresh-QK beyond the QK-based scoring in ADP and the layer-wise importance updates in SpecPrune-VLA? Please distinguish this from the contribution of progress-conditioned text selection.