- Rating
- 1
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper introduces MindDrive, a framework that converts HD maps into retrievable text descriptions. Built on the Qwen2.5-VL-3B backbone, the model dynamically selects between direct trajectory generation and Chain-of-Thought reasoning according to the scenario. Planning performance is further optimized through reinforcement fine-tuning (RFT) with a dual-mode paired-sampling strategy. The experiments use the NAVSIM and nuScenes datasets. After RFT, the NAVSIM PDMS improves from 83.0 to 90.0; on nuScenes, the average L2 error decreases from 0.67 to 0.51 and the average collision rate decreases from 0.14% to 0.08%. The approach has practical engineering value, but the paper does not yet establish its incremental contribution over existing adaptive-reasoning methods or provide direct measurements supporting the claim of improved efficiency.
Critical strengths
-
The textual map representation has clear practical value and is supported by preliminary ablations. Map descriptions can be generated offline and retrieved online with limited storage overhead. In Table 3, adding map data improves the SFT model's PDMS from 79.5 to 81.9, and adding CoT reasoning further increases it to 83.0. These results indicate that map information contributes to planning performance.
-
The complete system shows substantial internal improvements on two benchmarks. RFT improves NAVSIM PDMS by 7.0 points and also improves trajectory error and collision metrics on nuScenes. The analysis of 548 failure scenarios provides useful information about the system's limitations.
Critical weaknesses
-
The core framework overlaps substantially with existing work, and the remaining contributions are not independently validated. AutoVLA already combines direct action and Chain-of-Thought modes with reinforcement fine-tuning. AdaThinkDrive (2025) (https://arxiv.org/html/2509.13769v1) uses the planning quality of both modes to train adaptive reasoning. Converting map topology into text has also been explored in prior work such as PlanAgent. The authors should clarify the incremental contribution of their particular text-based map construction and forced paired-sampling mechanism. The current experiments do not compare different representations of the same map information, nor do they compare forced paired sampling against standard RFT under matched backbone, data, and training budgets. Consequently, the paper does not yet show why these specific design choices are important.
-
The main experiments do not establish a fair comparison or substantiate the claim of efficiency. The original NAVSIM protocol (https://www.cvlibs.net/publications/Dauner2024NEURIPS_supplementary.pdf) designates HD map data as privileged information for simulation and metric computation and makes it inaccessible to the driving agent. MindDrive consumes map-based text during inference, yet Table 1 labels its input simply as Cam. Its PDMS of 90.0 therefore cannot be directly compared with baselines using standard non-privileged inputs. Results under equivalent map-input conditions are needed. In addition, the map and CoT ablations are limited to SFT and do not isolate the corresponding gains in the final RFT model. The paper reports no direct measurements of latency, throughput, or generated-token count, and it does not provide a performance-versus-compute comparison for the final model across direct-planning, reasoning, and adaptive modes. CoT trigger rates in Table 4 are insufficient to establish end-to-end efficiency. Finally, the TTC metric decreases from 93.7 to 91.8 in Table 1, so the results should not be described as an across-the-board improvement in safety.
Questions for authors
-
Input protocol and fairness: Where do the map and global-localization data used during inference originate? Please provide baselines using the same map inputs, together with results for the final RFT model when map inputs are removed.
-
Incremental innovation: With the backbone, data, and training budget held constant, what performance gain does forced pairwise sampling provide over standard grouped sampling? What advantages does the text-based map representation offer over structured map encodings containing the same information?
-
Training mechanism: Are the mandated mode tokens included in the policy-gradient loss? If not, how does RFT directly optimize the model's own mode-selection process?
-
Efficiency and trade-offs: For the final model under always-direct, always-reasoning, and adaptive settings, what are the PDMS, generated-token count, and end-to-end latency? Does the latency include map retrieval, input prefill, and trajectory refinement?