- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper questions the implicit assumption that end-to-end autonomous driving must rely on generative planners (e.g., diffusion or flow matching). It argues that, under comparable model complexity, a carefully designed regressive multimodal planner can approach or even surpass generative counterparts while substantially reducing inference latency and accelerating training convergence. Methodologically, the authors start from TransFuser / DiffusionDrive and progressively add anchor refinement and stronger scene interaction (deformable attention, agent/ego interaction, anchor-conditioned modulation, residual refinement). Through a Top‑k oracle analysis of candidate quality, they argue that regression is not inferior in generation upper bound; the main bottleneck is candidate scoring/selection. They then propose soft scoring labels and Scoring Label Switching (SLS: early training uses pre-refinement anchor labels; later training switches to post-refinement trajectory labels). The same regressive recipe is transferred to GoalFlow and FlowPlanner, yielding three RegAD variants. On NAVSIM, RegAD-Transfuser reaches ~87.9 PDMS (on par with one-step DiffusionDrive), and RegAD-GoalFlow reaches ~90.2 PDMS at roughly 1/5 of GoalFlow’s latency. On nuPlan, RegAD-FlowPlanner attains strong non-reactive scores (e.g., 91.34 NR) at about 1/8 of FlowPlanner’s latency, with claimed faster training convergence. Validation mainly includes tables, ablations, latency comparisons, multimodal visualizations, and a closed-loop lane-change case in the appendix.
Critical strengths
- A timely, community-relevant control question with multi-baseline empirical support. Amid the rapid default toward generative planners, the paper converts DiffusionDrive / GoalFlow / FlowPlanner into regressive counterparts and reports planning-head latency and training-convergence differences. This kind of “factor isolation” experiment is highly valuable for the community and is the main reason I lean toward weak acceptance.
- Diagnostic analysis that pins the bottleneck on the scorer, rather than merely claiming “regression can also be multimodal.” The Top‑k oracle quality curves plus Table 3 (switching is critical) disentangle generation vs. scoring, so soft labels / SLS read as targeted fixes rather than pure engineering glue. This improves both persuasiveness and testability.
Critical weaknesses
- Differentiation from existing scoring / vocabulary planning literature is not sharp enough, and the paper insufficiently characterizes regimes where generative methods may still help. Related work mentions Hydra-MDP, WoTE, SparseDriveV2, etc., but the main text does not adequately answer: what is new in RegAD relative to static vocabulary scoring or “scoring is all you need,” and under which interaction/uncertainty regimes multi-step generation remains necessary. The R-mode gap and the failure of transferring SLS to DiffusionDrive hint at such boundaries, but these are not elevated into a systematic conclusion. In addition, generative models can more readily incorporate gradient-based guidance (e.g., classifier guidance) to avoid collisions, which may help explain stronger performance in reactive simulation—an advantage that pure regression schemes generally cannot match in the same way. The authors should explicitly discuss this trade-off in the paper.
- Multimodal / safety claims are under-supported by the presented evidence. In §3.3 the authors state that their strategy achieves “lower latency and better multimodal performance.” Later, this is mainly supported by a small number of qualitative visualizations. The amount of visualization is insufficient to substantiate the multimodal claims; quantitative metrics (e.g., pairwise cosine similarity among candidate trajectories) would strengthen the argument. Moreover, in Figure 6, RegAD appears to produce many infeasible trajectories, which conflicts with phrasing such as “Our regression planner generates diverse and safe trajectory candidates.” Given that diverse and safe multimodal trajectories are a central trend in end-to-end autonomous driving, the authors need to provide stronger evidence that RegAD indeed has better multimodal characteristics.
Questions for authors
- Please report parameter counts, planning-head FLOPs, and a complete checklist of architectural differences beyond “remove denoising / flow matching and time embeddings” for RegAD-Transfuser vs. DiffusionDrive, RegAD-GoalFlow vs. GoalFlow, and RegAD-FlowPlanner vs. FlowPlanner. If you strip deformable attention / agent interaction / modulation and keep only “MLP residual + your scorer,” how large is the remaining gap to one-step DiffusionDrive?
- Implication of SLS failure on DiffusionDrive (clarification; critical): Transferring soft labels + SLS to DiffusionDrive causes a large PDMS drop. Does this imply the central conclusion should be refined to: “under deterministic regression with clean candidate–label alignment, scoring is more critical than generation,” rather than “the generative algorithm itself is unimportant”? Did you try constructing soft labels on denoised / final trajectories (instead of noisy inputs) to restore spatial alignment?
- Reactive gap (clarification; critical): What primarily causes the R-mode lag vs. FlowPlanner on nuPlan—interaction modeling, candidate diversity, scorer calibration, closed-loop error accumulation, or FlowPlanner’s ability to use classifier guidance (or similar) to avoid some collisions? Please provide NR/R breakdowns by scenario type (lane change / intersection / close interaction); otherwise the “match or surpass” wording is hard to justify.
- Same-backbone comparisons against SparseDriveV2 / Hydra-MDP-style pure scoring systems would better isolate RegAD’s unique contribution.
- Report full end-to-end system latency (including perception), not only planning-head milliseconds.