- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper studies recovery planning under partial observation, where a planner may appear recoverable when evaluated with hidden future information, but the selected recovery strategy may not be executable during real deployment. The authors identify this issue as the oracle-to-deployable recoverability gap and propose oc-rap, an observation-consistent recovery-affordance planner.
The core component, oc-mero, changes the recovery selection procedure by aggregating observation-compatible latent futures before selecting a recovery option, preventing the planner from relying on unavailable future information.
The paper also introduces a signed recovery margin to unify recovery reasoning before and after contact events, together with rifa to separate recovery evidence from intervention preference. Experiments on Waymo Open Motion Dataset with Waymax closed-loop evaluation demonstrate improvements in several Near-Contact and Contact scenarios while maintaining conservative behavior in Safe scenarios.
Critical strengths
The main strength of this paper is the identification of the oracle-to-deployable recoverability gap. The paper highlights an important issue that recovery planning methods may implicitly use information that is unavailable during deployment. This provides a clear motivation for enforcing observation consistency in safety-critical decision making.
The proposed oc-mero operator is well aligned with the identified problem. Instead of selecting recovery actions separately for each latent future and then aggregating the results, the method first evaluates a fixed recovery option across compatible futures and only then performs selection. This design directly addresses the information constraint considered in the paper.
The experimental evaluation is carefully designed. The authors evaluate Safe, Near-Contact, and Contact settings using a unified framework and provide component-wise ablations. The results suggest that the proposed observation-consistent aggregation and rifa mechanism contribute to improved recovery behavior rather than only relying on a single metric improvement.
If the authors can better establish the novelty of oc-mero compared with existing non-anticipative planning methods and provide stronger evidence about the practical validity of the soft compatibility approximation, I would consider increasing the rating.
Critical weaknesses
The main concern is the novelty of the proposed method. The paper acknowledges that the general principle of making decisions based only on available information is not new. The connection between oc-mero and existing non-anticipative planning, stochastic optimization, and risk-sensitive decision methods needs to be clarified more carefully. Without a stronger distinction, the contribution may appear as a domain-specific adaptation of existing ideas.
There is a gap between the theoretical analysis and practical implementation. The theoretical guarantee is established under hard observation partitions, while the actual method uses a soft compatibility kernel as an approximation. It is unclear how robust the proposed method is when the compatibility estimation contains errors or when different latent futures are incorrectly grouped.
The method relies on several learned or predefined components, including latent future generation and recovery option libraries. If the latent future model misses important failure cases or the recovery set does not contain suitable actions, the benefits of oc-rap may be limited. Furthermore, the physical Contact evaluation is based on a relatively small number of paired scenarios, which limits the strength of the generalization claim.
The evaluated final selector gives nonzero weight 0.05 to distance from the logged future ego trajectory. That future is unavailable to a deployed observation-only planner. Without the authors' proposed zero-weight rerun, the reported closed-loop numbers cannot establish the abstract's full deployability claim. This does not refute the OC-MERO operator or its hard-partition result.
Questions for authors
- How does oc-mero fundamentally differ from existing non-anticipative stochastic planning or risk-aware contingency planning methods? Could the authors clarify which part of the formulation cannot be directly derived from existing frameworks?
2.The theoretical analysis assumes hard observation partitions, while the practical implementation uses a soft compatibility kernel. How sensitive is the performance to errors in the compatibility estimation?
3.How sensitive is oc-rap to errors in the latent future generation process? If the latent roots fail to cover important failure modes, how does this affect recovery reliability?
- The recovery option library appears to play an important role in determining available recovery behaviors. How does the method perform when the optimal recovery trajectory is not included in the candidate recovery set?
AI Use Clarification
The text bellow is my original, human-written review draft, reproduced exactly as I submitted it to the AI tool, including any grammatical or spelling errors. I used AI to polish the language and check for potential factual errors, inconsistencies, and unclear expressions. The substantive assessment, strengths, weaknesses, questions, and final rating were independently determined by me. The original text is provided here to clarify the scope of AI assistance and demonstrate my independent evaluation of the paper.
Summary This paper study recovery planning under partial observation. Planners can look recoverable with hidden future info, but strategies fail in real use. Authors call this the oracle-to-deployable recoverability gap, and propose OC-RAP. Core part OC-MERO aggregates observation-compatible latent futures before picking recovery options, so planner don’t rely on unavailable future info. Paper also uses signed recovery margin and RIFA to seperate recovery evidence from intervention preference. Waymo dataset tests show better near-contact/contact performance, stays conservative in safe cases.
Strengths
Critical Weaknesses
Questions