- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper studies real-time execution for chunk-wise relative-pose policies. It argues that aligning overlapping relative actions may fail to preserve the corresponding absolute targets when the robot’s reached pose differs from the preceding chunk’s planned pose. RRTC re-anchors the overlap, conditions suffix generation on tracking error, and trains with pseudo-errors derived from temporal offsets in demonstrations. The authors evaluate it in five simulated tasks under varied execution conditions and on three real-robot tasks. Results and ablations favor RRTC over the reported baselines in the tested settings
Critical strengths
-
A concrete geometric analysis. The paper distinguishes action-prefix alignment from consistency of the absolute targets represented by those actions, then derives a direct re-anchoring operation.
-
Useful component ablations and real-robot evaluation. The experiments test multiple execution conditions, and the ablations indicate that re-anchoring, tracking-error conditioning, and pseudo-error training each contribute in the evaluated setting.
Critical weaknesses
-
The relationship to RTC is not established through a matched comparison. RTC is formulated as generic action-chunk inpainting, while this paper analyzes prior methods using an absolute-target formulation. The reported baselines are TT-RTC and REMAC, including re-anchored variants; the paper does not directly compare against RTC adapted to the same relative-pose representation. The results therefore support RRTC against the reported baselines, but do not establish that RTC itself is limited to absolute-pose actions or cannot be combined with re-anchoring.
-
The evidence has limited scope. The pseudo-error proxy is evaluated against replay tracking errors, while real-robot evaluation uses one robot, three tasks, and 30 trials per task. It remains unclear how well the proxy covers errors during closed-loop policy execution, particularly when they do not resemble temporal lag.
Questions for authors
-
How are action coordinates represented in each RTC-related baseline? Can the authors clarify why an inference-time RTC comparison using the same relative-pose representation and re-anchored prefix is not included? Isn't pi0.5 what’s known as a relative pose strategy?
-
Were tracking-error distributions measured during closed-loop policy rollouts and compared with the pseudo-errors used for training, or is the reported validation based on replayed demonstrations? This would clarify the scope of the pseudo-error results.
-
Given that this work focuses on the coherent, real-time execution of action chunks, and although the authors have provided the code, are there any more intuitive video demos available to showcase the algorithm's performance?
2 comments
Response to W2 and Q2: Validating Pseudo Tracking Errors under Closed-Loop Execution.
We thank the reviewer for this insightful comment. Our original pseudo-error validation (Appendix B) was based on demonstration replay. To further validate the rationale behind our pseudo-error design, we extend the analysis to closed-loop policy execution across all three real-world tasks, using observations from 140 real-robot execution logs.
Why Temporal Offsets Approximate Tracking Errors. Our pseudo-error design is motivated by the idea that applying different temporal offsets along demonstration trajectories can simulate a range of pose deviations resembling the tracking errors encountered during real-world execution. Specifically, varying the temporal offset generates different relative pose deviations, allowing us to approximate diverse tracking-error conditions without requiring robot-collected error data. Accordingly, we synthesize pseudo tracking errors from robot-free demonstrations as , where .
Validation with Closed-Loop Policy Rollouts. To verify whether temporal offsets can approximate tracking errors during actual policy execution, we directly measure the anchor tracking error at each re-planning step, where is the reached pose and is the preceding chunk's planned target. We analyze observations from 140 real-robot execution logs across all three tasks. Following the same principle as our pseudo-error training, we construct five candidate tracking-error approximations using temporal offsets along the recorded preceding-chunk trajectory.
Evaluation Metrics. Following the temporal-offset matching procedure in Appendix B, we report the measured positional tracking error (TE), the residual error after matching the closest temporal offset, and the Temporal-Lag Residual Reduction (TLRR). A high TLRR indicates that temporal offsets approximate the observed tracking error well.
| Evaluation | Median TE (mm) | Residual (mm) | TLRR (%) |
|---|---|---|---|
| Demonstration Replay | 7.67 | 0.45 | 91.80 |
| Towel Pick-and-Place | 10.85 | 0.63 | 93.37 |
| Board Wiping | 8.86 | 0.76 | 90.43 |
| Tabletop Sorting | 11.03 | 1.01 | 88.73 |
| All Closed-Loop Rollouts | 10.65 | 0.86 | 90.26 |
Results and Implications. As shown above, although closed-loop execution exhibits larger tracking errors than demonstration replay (10.65 vs. 7.67 mm), the same temporal-offset approximation achieves a 90.26% median residual reduction, closely consistent with the 91.8% reported in our original replay validation. Similar results are observed across all three real-world tasks.
These results support the rationale behind our pseudo-error training: sampling different temporal offsets can generate pose deviations that closely approximate the tracking errors encountered during real-world closed-loop execution. Importantly, this conclusion is not limited to demonstration replay but is further explained by real robot policy rollouts.
Response to Q3: Supplementary Video Demonstrations.
We thank the reviewer for this valuable suggestion. We have added a supplementary video showcasing all three real-world tasks: Towel Pick-and-Place, Board Wiping, and Tabletop Sorting. The video includes four baselines (Vanilla , Temporal Ensemble, TT-RTC, and REMAC), four additional ablation variants, and our full RRTC method. Each method is demonstrated through three repeated real-robot executions per task.
Additional Ablation Variants. The video includes: (1) RTC + Re-anchor, which applies inference-time RTC guidance to a re-anchored prefix; (2) TT-RTC + Re-anchor, which adds coordinate-consistent re-anchoring to TT-RTC; (3) TT-RTC + Re-anchor + Tuned Offset, which further incorporates a task-specific fixed training offset based on measured tracking errors; and (4) TT-RTC + Re-anchor + GlobalConcat, which incorporates tracking-error information through global feature concatenation instead of layer-wise FiLM modulation.
These visual comparisons complement our quantitative results, highlighting the smoother motion, reduced jitter, and faster task execution achieved by RRTC compared with the baselines and ablation variants.
We thank the reviewer for the careful evaluation and insightful comments. We appreciate the recognition of our analysis and validation, and have conducted additional experiments to address the concerns.
Response to W1 and Q1: Inference-Time RTC as a Baseline.
Our original evaluation focused on training-time RTC methods, as TT-RTC has been shown to achieve better performance while avoiding the additional computational overhead of inference-time inpainting guidance, as demonstrated in the TT-RTC paper [1]. Nevertheless, we agree that a direct comparison with inference-time RTC is important for establishing the effectiveness of our RRTC framework.
We add two inference-time RTC baselines using the same relative-action representation: RTC, which directly applies guidance to the preceding chunk's relative-action prefix, and RTC + Re-anchor, which applies guidance to the re-anchored prefix to ensure coordinate consistency. Both baselines are implemented using π0.5 with the same chunk-relative end-effector pose representation as RRTC.
Simulation Results. As shown below, RRTC outperforms both RTC and RTC + Re-anchor, achieving the highest average SR (90.3% vs. 85.5% and 87.7%), TPR, and LDLJ. These results demonstrate that re-anchoring inference-time RTC alone is insufficient and support the effectiveness of our RRTC designs.
Real-World Results. Since RTC + Re-anchor outperforms RTC in simulation, we focus on RTC + Re-anchor as the stronger baseline for real-world evaluation. Across all three tasks, RRTC achieves higher average SR (88.9% vs. 77.8%), shorter completion time (13.85 s vs. 18.14 s), and better LDLJ (-27.33 vs. -27.84).
Overall, these additional experiments establish a direct comparison with inference-time RTC and show that RRTC provides further improvements beyond re-anchoring alone.
Reference: [1] Black K, Ren A Z, Equi M, et al. Training-time action conditioning for efficient real-time chunking[J]. arXiv preprint arXiv:2512.05964, 2025.