- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
This paper proposes RePIC, a training-free inference acceleration method for flow-based robot policies. It reuses complete denoising trajectories across consecutive replans through noise-aligned trajectory transfer and parallel Picard refinement, reducing sequential network evaluations. Experiments demonstrate 2.66× and 2.75× speedups on RoboTwin 2.0 and LIBERO with comparable success rates, along with evaluations on other VLA models and a real robot.
Critical strengths
- Clear motivation and practical relevance. The paper addresses an important inference bottleneck in flow-based robot policies by exploiting computational redundancy across consecutive replans.
- Simple and effective design. RePIC integrates trajectory reuse with parallel refinement without requiring additional training or modifications to pretrained models.
- Comprehensive experimental evaluation. The paper includes multiple benchmarks, different policy architectures, real-world experiments, and ablation studies that provide evidence for the effectiveness of the proposed framework.
Critical weaknesses
- The novelty and contribution of the framework could be better clarified. ParaDiGMS has explored parallel Picard sampling, C3ache has investigated cross-chunk denoising reuse, and DVAC has studied adaptive execution horizons. In my view, the key contribution of RePIC is the observation that intermediate denoising states contain reusable information beyond final action predictions, improving subsequent parallel refinement. The authors should better highlight and substantiate this insight. (Please feel free to point out if my understanding is incorrect.)
- The necessity of full-trajectory reuse remains unclear. The current ablations mainly compare endpoint-only and full-trajectory reuse, without exploring intermediate alternatives. Reusing a sparse subset of denoising states might achieve comparable efficiency with lower storage overhead. Further analysis would help establish whether retaining the entire trajectory is necessary.
Questions for authors
- Initialization of newly exposed action positions. RePIC directly reuses the same-index denoising states from the previous replan, despite the lack of temporal correspondence. What motivates this choice? Have the authors considered alternatives such as fresh-noise initialization or trajectory extrapolation?
- Inconsistency in the noise-alignment ablation. Section 4.2 states that noise alignment has no effect without trajectory shifting due to the fixed noise seed. However, Table 9 reports different network calls (3.36 vs. 3.18) and latency (233.4 vs. 290.9 ms) for these theoretically equivalent initialization settings. Could the authors clarify this discrepancy?