- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper proposes RATIO for zero-shot object navigation. The system organizes geometric uncertainty, task semantics, and navigable positions into a queryable environment representation and an executable navigation graph. An LLM selects tools for candidate search, experience retrieval, exploration, and multi-view verification based on current evidence, then uses tool feedback to select navigation nodes. Dedicated modules handle spatial computation and path planning, while all model parameters remain frozen. The authors evaluate the system on HM3Dv1, HM3Dv2, MP3D, and HM3D-OVON Unseen, reporting improvements in success rate and path efficiency.
Critical strengths
- The paper associates task semantics, geometric uncertainty, visit history, and path information with navigable nodes, grounding the LLM's high-level choices in concrete executable positions. The interfaces between environment representation, tool queries, and navigation execution are reasonably clear and form a complete navigation pipeline.
- The experiments cover four navigation benchmarks, including unseen target categories in an open-vocabulary setting. The GPT-5.6 Luna variant achieves 53.0% SR and 34.0% SPL on HM3D-OVON Unseen, exceeding SpaceVLN's reported 51.6% and 33.1%. In internal ablations with shared components, progressively adding the navigation graph, LLM decisions, and tools with feedback history improves both SR and SPL on all four benchmarks, supporting the practical value of the overall design.
Critical weaknesses
- Limited methodological novelty. The paper primarily integrates executable navigation graphs, LLM tool orchestration, and dedicated spatial computation. Most tools in Table 4 also come from existing methods. The independent technical contribution over tool-use methods such as AgenticNav and existing graph-based navigation methods remains unclear.
- Insufficient causal evidence for the core mechanism. Table 2 adds tool access and feedback history simultaneously, without a fixed-orchestration control or a separate history ablation. It therefore cannot distinguish whether the gains come from additional information, memory, or adaptive tool selection.
- Insufficiently controlled comparisons with external baselines. RATIO uses SAM 3, but Table 1 does not clarify whether the baselines were rerun with shared perception modules and comparable computational budgets. Differences in foundation models and computational resources may therefore contribute to the reported gains.
Questions for authors
- What is the independent technical contribution over the closest tool-use and graph-based navigation methods?
- Could you compare against fixed orchestration using the same tools, history, and budget, and separately ablate feedback history?
- Please clarify the sources of baseline results and provide comparisons with representative strong baselines using shared perception components and comparable budgets.
Thank you for recognizing the navigation representation and tool interaction design, and for your suggestions on the independent contribution, mechanism analysis, and baseline comparisons. We address these points below and describe the corresponding revisions and planned experiments.
Weakness 1 and Question 1
Thank you for the suggestion. We fully agree that the independent contribution should be clarified and would also like to explain the existing experimental evidence. We compare RATIO with three related groups of methods: semantic exploration, map reasoning, and LLM decisions (Table 1). Progressive ablations with shared components further support the contributions of the executable navigation graph, LLM decisions, and tool interaction (Table 2).
The core innovation is the combination of the executable navigation graph, tool-selection mechanism, and LLM. The executable navigation graph provides task evidence and navigable positions; the LLM selects tools according to the current task state and uses tool feedback to adjust subsequent decisions. Most existing tool-using navigation methods organize tools around perception, planning, and control, and modular methods already support replacing these components. For example, in a fixed environment, the best-performing perception tool can generally be selected in advance, making repeated online selection unnecessary. RATIO considers that different navigation stages may require different strategies. We therefore design tools for evidence acquisition, target candidate search, broad exploration, and multi-view verification, allowing the LLM to select the navigation capabilities needed as the task progresses to improve exploration efficiency. Section 3.4.2 describes these tools, and Figure 4(a) in Section 4.4 further illustrates how tool use changes across navigation stages.
The method overview and contribution paragraphs in the Introduction, together with the final paragraph of Section 2.3, LLM-Driven Navigation Decisions, did not sufficiently explain the role of this combination or the design of tools around the strategy needs of different navigation stages. We have revised these passages to explain how the executable navigation graph supports tool selection, how tool feedback affects subsequent decisions, and how the tools address different navigation stages. We have also connected the tool-use patterns in Section 4.4 with the ablation results in Table 2 to clarify the value of this design for navigation success and path efficiency.
Weakness 2 and Question 2
Thank you for the suggestions. We fully agree that stronger experimental evidence is needed for the core mechanism, and partially agree with the fixed-orchestration comparison requested in Question 2. Several tools draw on existing methods, including CogNav and UniGoal, which are compared in Table 1; Table 4 in Appendix D lists the corresponding tool sources. On HM3Dv1, RATIO achieves 36.4% SPL, compared with 26.2% for CogNav and 25.1% for UniGoal. We had not sufficiently articulated the conclusion from this comparison and have now added a statement after the corresponding results in Section 4.2, explaining the value of orchestrating existing navigation capabilities on demand for path efficiency.
For tool feedback history, we agree that an independent ablation with and without this history is needed to complete the evaluation. The current comparison from C to D reflects the combined contribution of tool interaction and tool feedback history. Due to time constraints, we will add this ablation in future work, keeping the executable navigation graph, tools, LLM, and budgets fixed while comparing retained and disabled tool feedback history. The experiment will be added to the ablation study.
Weakness 3 and Question 3
Thank you for raising the issue of fair comparison. We agree that the sources of baseline results and reproduction settings should be clarified. We attempted to reproduce some baselines, but our local results did not reach the metrics reported in the literature. For ApexNav, a reproduction using the smallest segmentation model and BLIP-2 did not reach the reported results. Under our local configuration, the original perception pipeline also incurred greater overhead than the configuration using SAM 3. We therefore also attempted a reproduction using SAM 3 for detection and segmentation.
Given concerns that differences in CPUs, GPUs, storage devices, and runtime configurations could affect reproduction results, we ultimately used baseline results recorded in other papers for Table 1. We have identified the cited sources and original result provenance in the revision. RATIO uses SAM 3 primarily to integrate detection and segmentation and simplify the perception pipeline; our research focus remains the executable navigation graph and task-adaptive tool orchestration. To examine these designs, the internal ablations share perception, map updates, path planning, and the executor, supporting the contributions of the executable navigation graph, LLM decisions, and tool interaction.