- Rating
- 3(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
TRACE combines tracking-policy post-training with a learned risk head that selectively scales motion commands. It aims to reduce collisions while preserving embodied target-following performance.
Critical strengths
The paper provides comprehensive experimental results. The collision reduction under oracle perception is supported by the reported data.
Critical weaknesses
Practical validation is insufficient. All experiments are simulated without real world deployment.
Some test episodes were also used to train the risk predictor. The remaining episodes were used to choose the intervention threshold, so they are not an independent test set either. Performance on unseen episodes remains unclear.
Questions for authors
Does the method still reduce risks on new episodes that were heldout form training nor threshold selection?
What inputs in the 84 dim allow the risk predictor to detect walls or other obstacles?
3 comments
Thank you for the following-up experiments and detailed responses, which have addressed most of my concern. I am raising the score to weak acceptance.
Thank You for Reconsidering Your Assessment
Thank you very much for reading our rebuttal and revised manuscript, and for raising your score! Your constructive questions directly motivated the scene-disjoint evaluation, the collision-foresight analysis, and the learned-perception and on-board validations, which substantially strengthened the paper.
Response to Reviewer Mh2C
Thank you for your thoughtful review and for noting our comprehensive experimental results. We ran new experiments directly addressing each question and added them to the revised PDF; our replies follow your numbering.
W2 & Q1 — Does the method still reduce collisions on new episodes held out from both training and threshold selection?
Yes. The revision adds a strictly disjoint test in which fitting, threshold selection, and measurement use three non-overlapping sets of scenes (Appendix U, p. 38). The 101 DT scenes are split at the scene level, balanced on collision rate (5.49%, 5.49%, 5.53%):
On TEST (5 policy seeds, 1,255 paired episode rollouts across the 251 unseen episodes, concurrent-pair protocol):
On unseen scenes, episodes, and targets, collisions fall by 3.67 points—in line with the full-set −3.96—with every seed negative and SR/FR intervals spanning zero (ΔSR +1.35 [−1.35, +4.06], ΔFR −0.17 [−1.41, +1.03]). §4, Table 2, and Appendix J now report this test.
Q2 — What inputs in the 84 dimensions allow the risk predictor to detect walls or other obstacles?
§4.1 now states EVT-Bench's exact collision rule:
HumanCollision(which defines CR) triggers when the robot comes within 0.5 m of the followed person; walls and furniture do not enter CR (navmesh constraints govern scene geometry). All 712 collision terminations in our logs end with robot–target distance < 0.5 m.The inputs that anticipate this event are on-board target-state cues (Appendix K): target box and scale, identity margin, candidate competition, probe distance/bearing bins, memory state, previous command, and predicted waypoints—computed from RGB and policy outputs with no simulator distance.
Appendix V (p. 38) evaluates predicting collision within H steps (733,203 steps, 6,900 episodes) against two privileged quantities the head never sees:
W1 — Practical validation: oracle perception and real-world deployment.
We strengthened practical validation on both fronts:
target #1) and online risk readouts (Figs. 10–11). Resolving a 3.67-point binary collision shift requires ≈780 paired trials at 80% power, which we measure across the 2,510 paired rollouts on unseen scenes (Appendix G).We hope these new experiments and clarifications address your concerns, and we respectfully invite you to reconsider your assessment in light of the updated results.