- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes NaviVLN, a dual-system navigation framework combining task-aligned visual/textual auxiliary targets, Joint Attention, and staged training. Auxiliary decoders shape navigation representations during training and are removed at deployment; latent intention queries condition a local trajectory expert. With 330K reported decision anchors, the method improves over NaVid and Uni-NaVid on R2R-CE and RxR-CE.
Critical strengths
- The framework is well motivated. Progress-aware text and task-aligned semantic visual targets provide complementary supervision, while removing auxiliary decoders at inference is a practical design choice.
- The architecture comparisons support Joint Attention. With auxiliary targets and loss settings held fixed, Joint improves R2R-CE SR from 47.09% for Separate to 51.39%, and SPL from 44.52% to 48.03%. Representation analyses provide supporting evidence, and the 110K/220K/330K experiments demonstrate gains from additional training data.
Critical weaknesses
- The integrated architecture is supported more clearly than its specific design choices. Separate/Merged/Joint comparisons do not independently isolate the navigation anchor or stop-gradient. The contribution of task-aligned targets relative to less task-specific auxiliary targets, and that of staged training, also remains uncertain. This makes it difficult to determine which choices account for the advance beyond the broader auxiliary-supervision and hierarchical-navigation recipe.
- Comparative sample efficiency is not established under matched conditions, and missing configuration details hinder assessment. Table 1 contrasts decision-anchor counts with reported or estimated counts from methods with different data compositions, models, and inputs. The internal scaling curve shows improvement with more data, but not superiority over a matched baseline. The provided PDF also lacks the exact VLM checkpoint, numerical loss weights, optimizer settings, and training steps or epochs for each stage.
Overall, the ablations and results support a useful integrated method, but the contribution of its specific choices and the comparative sample-efficiency claim remain insufficiently established. Together with the missing training configuration, these concerns lead me to a weak reject.
Questions for authors
- Could the authors prioritize matched ablations of the navigation anchor and stop-gradient? If available, comparisons with less task-specific targets or a simpler training schedule would help explain the sources of the gains.
- Please define a decision anchor and report data use and repeated exposure across all stages, together with the missing model/training configuration and the exact representation-scoring protocol. What evidence supports comparative sample efficiency under matched backbone, supervision, and training-budget conditions?
5 comments
Response to Reviewer UZA2 — W2 & Q2
[W2 & Q2] Sample efficiency, per-stage data, and repeated exposure
Section 3.1 defines the decision anchor and the unit. An anchor is one effective trajectory sample carrying both task-aligned annotations; every count uses the effective-trajectory-sample unit (one trajectory, one view, one height, one instruction). The dataset has about 4.0M such samples: 0.8M anchors and 3.2M instruction-following samples without both annotations. Stage 0 uses the 4.0M; Stages 1--2 reuse the 0.8M anchors, a subset rather than an additional pool, so later stages do not add to the dataset total. STOP oversampling is reported separately, so repeated exposures are not new samples. The table below records how each data component enters training; per-stage source composition and the exact counts are also spelled out in the data-accounting paragraph of Appendix A.
On matched conditions: input modality is fixed and the baseline's own reported count is used — 68.3 vs 66.9 SR on R2R-CE Val-Unseen for Qwen-RobotNav-4B, with 4.0M vs 15.6M samples (about 25.6%). The Table 1 caption states counts follow each method's unit and are not interchangeable, and Table 1 now lists every backbone. The +10.2-point gain (58.1% to 68.3%) is Stage 0 navigation SFT versus full Joint under like-for-like accounting — a method gain, not a data-volume gain. Scale results are in Appendix D; the model and training configuration is in Appendix A.
| Data component | Samples | Task-aligned annotations | Used in |
|---|---|---|---|
| Effective trajectory samples | about 4.0M | — | Stage 0 |
| Decision anchors | 0.8M | Yes (visual and textual) | Stages 1 and 2 |
| Instruction-following samples | 3.2M | No | Stage 0 |
| STOP oversampling | Counted separately | — | All stages |
Response to Reviewer UZA2 — Overall
[Overall] The three points in your assessment
The revision adds evidence on your three points. (i) Which choices produce the gain: Tables 2--4 remove each mechanism, target and stage singly, with margins of 6.5 points for the anchor, 5.1 for cross-branch attention, 5.6 for Stage 1 and up to 7.0 for target alignment. (ii) Whether sample efficiency holds: the counting unit is defined and applied throughout, and the only comparative claim is against one monocular-RGB baseline on R2R-CE Val-Unseen with an explicit count — 1.4 points at about 25.6% of its reported samples, with the caveat that the two counts use different units; scale results are separate in Appendix D. (iii) Configuration: Appendix A reports backbone, stride, GPUs/batch, epochs, steps, learning rates, auxiliary weights and per-stage update scope. The Stage 0 plus same trajectory-expert control remains the one comparison not completed.
What remains open is stated explicitly: multi-seed variance in simulation and the Stage 0 plus trajectory-expert baseline that would directly test the simpler-training alternative. We name these rather than let the paper imply more than the tables show. In summary the revision adds single-mechanism, target and stage ablations (Tables 2--4), a defined counting unit, a per-stage configuration table in Appendix A and complete real-world success counts in Table 5; the missing comparison is Stage 0 with the same local trajectory expert.
Response to Reviewer UZA2 — W1 & Q1
We thank the reviewer for the balanced assessment, and we agree with the framing: the integrated architecture is better supported than its individual choices, and the comparative sample-efficiency claim was not established under matched conditions. We have tried to close both gaps with evidence rather than with description. Table 2 removes each coupling mechanism singly, Table 3 varies the targets under a fixed architecture, Table 4 removes training stages, and Section 3.1 defines the counting unit and applies it to every number. Appendix A now carries the configuration table. We also agree with your two strengths: progress-aware text and task-aligned visual targets are complementary, and removing the auxiliary decoders at inference is a practical choice rather than a hedge.
[W1 & Q1] Navigation anchor, stop-gradient, and a simpler baseline
Table 2 removes each mechanism singly with data, backbone and targets fixed: 68.3 falls to 63.2 without cross-branch K/V, 61.8 without the navigation anchor and 67.5 without cross-branch stop-gradient. The anchor is the dominant term and the stop-gradient the smallest; we report that ordering rather than presenting them as equal. Table 4 addresses simpler training: skipping Stage 1 (0→2) gives 62.7/55.43 SR / SPL and skipping Stage 2 (0→1) gives 57.9/51.21, against 68.3/63.55 for the full schedule, so Stage 1 contributes 5.6 points. Stage 0 with explicit CoT reaches 60.3/54.88, but that is a decoding comparison, not the Stage 0 plus same trajectory-expert control you specify; that matched control is still missing.
The Stage 0 plus local-trajectory-expert variant you specify is the direct control still missing: we report no number for it rather than a partial one, and explicit CoT does not stand in for it. Table 3 completes the target comparison under a fixed architecture: task-aligned semantics with progress description 64.2, against 57.2 for RGB with scene CoT, 60.2 for semantics with scene CoT and 62.6 for RGB with progress description. Together the tables attribute the gain to specific choices — anchor coupling 6.5 points, cross-branch attention 5.1, Stage 1 5.6, target alignment up to 7.0 — rather than to the integrated recipe as a whole.