- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
TraceWAM addresses task-state alignment drift in long-horizon robot manipulation. It uses stage references and progress memory to evaluate a base action chunk and a bounded residual candidate against the active stage goal. A shared verifier predicts each candidate’s structured physical deviations and uncertainty. The residual is accepted only when the reference is valid and the prediction indicates both lower risk than the base action and progress from the current state; otherwise, the base action is retained. Shared-state simulator branches provide supervision for learning candidate outcomes.
Critical strengths
- A clear formulation of task-state alignment drift. The paper characterizes execution errors through changes in task-critical poses, contacts, and spatial relations relative to the active stage goal. Distinguishing current misalignment from further deterioration provides a useful framework for studying how physical errors develop during multi-stage manipulation.
- Consistent gains across manipulation benchmarks. TraceWAM improves over Fast-WAM by 1.6 and 1.4 percentage points on RoboTwin 2.0 and LIBERO, reaching 93.0% and 98.1% success, respectively. The larger improvement on RMBench, from 4.0% to 41.6%, demonstrates the practical value of the combined stage references, progress memory, and candidate evaluation on memory-dependent tasks.
Critical weaknesses
-
Comparison with related methods. EV-WM already uses structured event prediction, uncertainty scoring, and candidate gating, with bounded residual proposals in its contact-sensitive setting. The scalar-verifier baseline does not establish TraceWAM's advantage over this approach. Please compare under matched budgets and clarify the benefit in success rate, latency, or supervision requirements.
-
Dependence on predefined references. The experiments mainly vary scenes within trained tasks, leaving transfer to new task structures untested. How much additional schema design and demonstration data does a new task require?
-
Insufficient real robot evaluation. The real world PiPER case lacks training data size, training tasks, success rates, and more details. Please report these and provide a complete demo through an anonymous link (if possible). I would raise my score if the authors address my concerns raised in points 1 and 3.
Meanwhile, replacing the schematic robot interactions in Figures 1 and 2 with images from real robot executions may make the paper more visually appealing.
Questions for authors
Could TraceWAM’s short-term scoring override useful recovery actions, such as withdrawing before retrying an insertion? Can the authors compare recovery success rates with the base policy from the same failure states?
Reminder: Reviewer Engagement During the Discussion Period
Dear Reviewers,
As the discussion period is drawing to a close, could you please review the authors' rebuttal and provide your feedback at your earliest convenience?
Active engagement in discussions with the authors is an essential part of the peer-review process and plays an important role in ensuring the success of the conference. Your participation would be greatly appreciated.
Thank you for your time and contributions.
Best regards,
AC