- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
CausalDrive addresses “motion inertia” in VLA-based autonomous driving, where a model recognizes a hazard but continues to follow historical motion patterns. The framework combines sparse historical memory through SSTF, Ego Query-based temporal modeling, and language-guided Causal-Intervention Attention (CIA) to adjust actions by suppressing historical features and emphasizing current hazard cues. It is trained using supervised fine-tuning (SFT) and constrained GRPO. The paper reports action classification, trajectory prediction, and vehicle control results on DriveAction, DriveLM, and BDDA.
Critical strengths
The problem is practically relevant. The failure to promptly adjust actions despite recognizing hazards warrants investigation, and directly incorporating language signals into action generation is well motivated.
- The approach is intuitive. Selectively downweighting historical information based on the current level of risk is well suited to sudden hazards, compared with prioritizing temporal continuity alone.
- The evaluation covers multiple output levels. The reported trajectory error of 0.30 m on DriveLM and steering MAE of 0.0142 on BDDA provide preliminary evidence of effectiveness.
Critical weaknesses
- The core contributions are insufficiently differentiated from existing techniques. SSTF primarily consists of a FIFO cache of frozen features, while Ego Query attends to historical queries; DriveTransformer already employs sparse task queries and streaming history propagation. CIA appears closer to language-conditioned key/value gating, and the paper does not establish its substantive advantages over standard gating, history resets, or attention bias. The use of the term “causal” also lacks support from controlled intervention experiments.
- The lack of decisive component ablations prevents attribution of the reported gains. The paper does not individually remove SSTF, Ego Query, or CIA, nor does it compare SFT-only training against GRPO using the same backbone. The modality ablations in Table 1 cannot distinguish whether improvements arise from a stronger backbone, additional training, reinforcement learning, or the proposed inertia suppression mechanism.
- The experiments do not directly validate the central safety claims. Aggregate accuracy, L2 error, and MAE do not establish that the model overrides motion inertia more quickly in emergencies. The paper lacks evaluation on a dedicated hazard-event subset, braking latency, collision rate, TTC, and closed-loop performance. Figure 3 presents only a scene sequence, without baseline trajectories, speed profiles, or comparisons with the intervention enabled versus disabled; it therefore cannot substantiate the claim that the model performs “causal reasoning.” Likewise, keeping the learned cost below a threshold does not directly establish real-world safety.
- The performance gains are limited, and the comparison settings lack transparency. On DriveAction, the reported accuracy of 87.41% is lower than GPT-4o’s 88.84% and Qwen-Max’s 91.32% in the same table. On DriveLM, the improvement over EMMA is only 0.02 m, with no variance estimates or statistical significance analysis reported. On BDDA, the method is compared against only a single FCN-LSTM baseline, whose results are presented as ranges without a clearly specified, consistent reproduction protocol. The data splits, prediction horizons, and units of the control outputs are also insufficiently specified.
Questions for authors
- With the same backbone, data, and training budget, how much additional benefit does CIA provide over standard gating, hazard-triggered history resets, and attention enhancement applied only to the current frame?
- Could you hold the current observation fixed while varying historical motion states in sudden-hazard scenarios, and report braking latency, collision rate, and false braking rate in normal scenarios, to verify whether the gains can be attributed to suppressing misleading motion inertia?
- Please clarify the DriveAction input protocol, the DriveLM data splits and prediction horizon, and the source of the BDDA labels. Please also explain the relationship between the 0.05 m error reported in the appendix and the 0.30 m error in the main results table.