- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper proposes ProActiveDrive, a vision-language-action (VLA) autonomous driving framework built upon SimLingo that integrates a LiDAR-BEV encoder, a DeltaTok-based single-step latent future predictor, and heuristic-supervised fast/slow adaptive reasoning to improve closed-loop driving performance on Bench2Drive-220 and Fail2Drive.
Critical strengths
- The paper addresses a practical challenge in deploying VLA policies in closed-loop autonomous driving by attempting to balance test-time deliberation with inference throughput.
- The data-enhancement pipeline in Appendix D identifies and corrects semantic misalignments between rule-based commentary templates and expert trajectories (such as misclassifying yielding as car-following), which is a useful engineering insight for VLA dataset curation.
Critical weaknesses
- Unfair Modality Comparison and Missing Component Ablations: The main claim that ProActiveDrive outperforms its closest architectural baseline SimLingo (88.20 vs. 86.07 DS in Table 1) is confounded by sensor modality differences, as SimLingo is strictly vision-only (1x Camera) whereas ProActiveDrive adds a LiDAR-BEV encoder alongside the DeltaTok predictor and 170K relabeled CoT annotations. There is no step-by-step ablation isolating the individual gains of adding LiDAR-BEV, adding DeltaTok future tokens, and relabeling the reasoning dataset.
- Contradictory Empirical Results Between Main Text and Appendix: In Appendix D.8, the authors report that training with the template-based commentary already achieves 87.52 DS, and the first round of grounded CoT annotation reaches 88.93 DS and 73.2% SR—which actually surpasses the final reported ProActiveDrive model in Table 1 (88.20 DS and 71.30% SR). This indicates that the heavy two-stage fusion and second round of annotation may degrade performance and that the primary gains stem from offline data cleaning rather than the proposed architecture.
- Conflated Ablation of Adaptive Thinking vs. Data Relabeling: Table 5 compares "Full CoT" against "Adaptive thinking" to claim a +3.1 mean ability gain from selective reasoning, but the text states that "Full CoT" uses unrefined template-based supervision while "Adaptive thinking" uses the Qwen3-VL-2B grounded supervision. This conflates the effect of selective fast/slow inference with the effect of fixing corrupted supervision labels; furthermore, adaptive thinking degrades performance in Merging (-2.1), Emergency Braking (-1.7), and Traffic Sign handling (-2.8).
- Unsubstantiated Efficiency Claims and Hidden Visual Backbone Overhead: While claiming lightweight anticipation, the DeltaTok module requires running an additional frozen DINOv3 ViT-B/16 encoder on 512x512 images plus a 6-layer transformer predictor at every timestep on top of the main InternViT encoder. Table 4 only reports an opaque "Mean Ratio" without wall-clock latency (ms/frame), FPS, or isolated overhead of the DINOv3/DeltaTok and LiDAR branches, and in slow mode (critical scenarios like emergency braking), the agent still suffers from full autoregressive token generation latency when low reaction time is most critical.
Questions for authors
- What is the closed-loop Driving Score and Success Rate of ProActiveDrive on Bench2Drive-220 when trained without the LiDAR-BEV branch (i.e., strictly 1x Camera like SimLingo)?
- Please provide a clean, decoupled ablation table starting from the SimLingo baseline and sequentially adding: (a) LiDAR-BEV fusion, (b) DeltaTok single-step prediction, (c) grounded CoT relabeling (always-on), and (d) fast/slow adaptive switching.
- Why does the first-round grounded annotation model in Appendix D.8 (88.93 DS, 73.2% SR) outperform the final full ProActiveDrive model in Table 1 (88.20 DS, 71.30% SR)?
- What is the exact wall-clock inference latency (in ms) and GPU memory footprint of each module (InternViT, LiDAR-BEV encoder, DINOv3 + DeltaTok predictor, and Qwen2.5-0.5B under both fast and slow modes)?
Reminder: Author Response and Reviewer Discussion
Dear Reviewers,
We are halfway through the discussion period. Please review the authors’ responses, address any remaining concerns, and engage in the discussion where appropriate. If your assessment remains unchanged, please briefly acknowledge that you have considered the authors’ responses.
Thank you for your time and contributions.