- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes Vault, a framework for autonomous driving planning. It replaces diffusion planner to one-step latent drifting, then repeatedly collects maximum-scoring self-generated trajectories under official evaluator as imitation goals for efficient planning and maintaining multimodality. The proposed method achieves state-of-the-art performance on both NAVSIM v1 and v2.
Critical strengths
- The proposed method achieves both SOTA PDMS scores on both NAVSIM v1 and v2 compared with substantial amount of recent baselines.
- The proposed Vault framework's design utilize the efficiency of one-step generation to avoid the iterative denoising procedure of Diffusion planner via Drifting, also with a self-imitation mechanism to expand imitation target pool using high-quality self-generated trajectories.
Critical weaknesses
- The Vault use the V-JEPA 2.1 pretrained visual backbone and other competitive baselines use different backbones, which make it difficult to attribute the improvements from proposed planning modules and backbone. Given that Valut only surpass the best baseline by 0.1 and 0.2 PDMS score on v1 PDMS and v2 EPDMS respectively, a more controlled comparison and ablation on both v1 and v2 could further strengthen the proposed method.
- The presentation of the method could improve for clarity. Vault integrated several components from previous work, but the motivation for combining these components and their individual roles are not always very clear, especially in the introduction. A clearer presentation of the overall method and the motivation behind each component would make the methodological contribution easier to understand.
Questions for authors
- The authors could add more related citations like End-to-End Driving with Online Trajectory Evaluation via BEV World Model (ICCV25), Driving on Registers: Simple and efficient transformer based end-to-end driving (CVPR 2026).
- Vault achieves notable higher EP on both v1 and v2 compared with most baselines. The paper attributes part of this improvement to the reward-gated positive pool providing higher-progress imitation targets. Could author provide more analysis or intuition on why Vault particularly improves on EP instead of TTC or other sub metrics?
- The paper could provide more analysis on Vault design to better explain why works. For example, it is helpful to understand the method by showing how the positive imitation pool evolves during training, visualization on distributions of the positive and negative points in latent space, and more detailed comparison of multimodality planning results with original diffusion planner.
3 comments
Thank you to the authors for their detailed response and additional experiments, particularly on NavHard and the controlled-backbone ablation. However, I remain concerned about the limited improvements on NAVSIM v1 and v2 and the missing v2 ablations. In particular, the new Vault variant achieves the same PDMS as the strongest baseline. Given the remaining concerns, I find it difficult to justify raising my score. Therefore, I will maintain my score.
Margins against the published baselines, consistency across v1, v2, and NavHard, and the cost of v2 ablations
Thank you for re-reading our response and for stating the remaining concerns so plainly. We would like to add one observation about the margins before turning to the two open points.
The 0.1 and 0.2 gaps mentioned in the review are gaps to the two newest preprints, CLOVER and SUV. Against the baselines that have been through peer review, the margins are not close. DrivoR (CVPR 2026) trails by 0.9 on v1 navtest (93.7 vs. 94.6), by 0.8 under its own backbone family (93.7 vs. 94.5 for our DINOv2-S control), and by 1.0 on NavHard (48.3 vs. 49.3). DriveSuprim (AAAI 2026) trails by 1.1 on v1 (93.5 vs. 94.6). In Table 3 it reports only under the original evaluator, where it trails by 2.3 (86.0 vs. 88.3). The compressed top of the table therefore involves only the two most recent entries, and we stay ahead of both on every split they report.
The pattern we care more about is consistency. Vault leads v1 (94.6), v2 navtest (91.2 corrected, with the highest mean ego progress at 92.1), and NavHard (49.3, against 48.3 for DrivoR and CLOVER). The closest competitors each fall away somewhere. CLOVER, the strongest overall, gives back a full point on NavHard. SUV, closest on v2 at 91.0, runs v2-only experiments in its main paper. The v1 number in its supplementary is 90.8, which is 3.8 behind ours. DrivoR is behind on every split we share. On v1 the top method scores sit within 0.3 of the human reference (94.8), so the headroom there is thin. Ego progress is where the methods still separate, and Vault leads it on both versions (92.9 and 92.1).
On the DINOv2-S variant, we added this run during the discussion period in response to CW1. The swap is deliberately plain. We replace the visual encoder with a LoRA-fine-tuned DINOv2-S at 756×1344 input and change nothing else in the pipeline. There is no DINO-specific tuning, and we did not adjust the decoder, the scorer, or any capacity to accommodate the new encoder. The variant still reaches 94.5 under the baselines' own backbone family, on par with CLOVER and 0.8 above DrivoR, with ego progress again higher (92.8 vs. 91.7). Losing only 0.1 to the default model after a drop-in swap tells us two things. The gain sits in the planning design, not the backbone. And the pipeline takes to a new visual stack easily, which we take as a practical strength of the method.
On simplicity, the deployment story is identical across the three systems. One forward pass generates the candidates and a scorer picks one. The difference is the training wrapped around it. DrivoR keeps its generator on plain imitation and lets evaluator feedback reach the scorer only. CLOVER needs more machinery. It builds pseudo-expert trajectories from privileged metric-cache information (route centerlines, drivable-area maps, future occupancy), then runs thirty cycles of alternating scorer fitting and generator self-distillation. For v2 it further adds a separately trained anchor model with a tuned soft reranking, which supplies 1.1 of its reported 90.4 (89.3 without it). Vault trains the whole planner in one loop. The evaluator only decides which self-generated samples become anchors for the drift loss. The scorer never sits in the generator's training path, and nothing is attached at inference. Our 91.2 on v2 carries no reranking. Reaching these numbers with less machinery is a fair part of what the paper argues for.
On the missing v2 ablations, the v1 and v2 planners are separate runs. Each run has its own evaluator-gated pool, and its scorer learns from that evaluator's labels. EPDMS is also a different objective, adding DDC, TLC, LK, HC, and EC on top of the v1 terms. An ablation cell on v2 is therefore a full second training campaign, not a re-evaluation. Within the discussion window we put the controls on v1, where the mechanism was designed. NavHard served as a second, harder split, and the gains persist there. This is also where the published baselines place their ablations. CLOVER's component ablations (its Tables 6–8) are all on v1, with only the v2-specific reranking ablated on v2. DrivoR goes further and computes all ablation scores on v1 navval, not even on the test split.
We hope the consistency across the three settings, together with the attribution controls, makes both the size and the origin of the improvements easier to judge.
Controlled backbone test, clarified design motivation, and mechanism analyses
We thank the reviewer for the careful summary and suggestions. The revision adds a controlled backbone experiment, a matched-budget pool control, a NavHard two-stage evaluation, and a quantitative diversity appendix, and rewrites the introduction. All changes are marked in blue.
CW1: We agree this needed a controlled test and have added one (Sec. 4.2, blue). Replacing the visual stack with a LoRA-fine-tuned DINOv2-S at 756×1344 (the backbone of DrivoR and CLOVER), with the planning pipeline otherwise unchanged, reaches 94.5 PDMS with EP 92.8: it matches CLOVER, exceeds DrivoR by 0.8, and sits only 0.1 below the V-JEPA variant, within the five-seed spread (94.52–94.60). The visual stack thus contributes about 0.1, and the planning design carries the performance. The ego-progress margin over CLOVER (92.8/92.9 vs. 91.7) holds on both backbones. All other controls likewise hold the backbone fixed. The controls are on v1, where the strongest baselines report. On v2, Vault's corrected 91.2 exceeds SparseDriveV2 (90.1), CLOVER (90.4), and SUV (91.0) with the highest mean EP (92.1), and on NavHard Vault leads DrivoR and CLOVER by 1.0 (49.3 vs. 48.3) with the highest stage-1 EP (79.5).
CW2: Vault rests on two coupled ideas. First, existing generative planners run or compress the denoising chain at inference. Drifting instead learns the scene-conditional distribution directly during training, so a single forward pass yields multimodal samples. Second, this is what makes reward guidance natural: drifting's supervision is an anchor set, so the reward acts simply by deciding which samples become anchors. The pool stores every self-discovered perfect-score trajectory and lets supervision evolve with the policy, with no policy gradients, learned reward models, or extra interaction. The remaining components are deliberate adoptions: the pipeline follows the mainstream generate-and-select paradigm, and the backbone follows Drive-JEPA in adopting a V-JEPA, since a predictive representation of the image stream suits an anticipatory task. The VAE/PCA drift spaces are engineering instantiations (Sec. 3.2, App. B–C). The introduction now states this causal chain explicitly.
Q1: WoTE is now cited in Related Work (blue): it evaluates candidates online through BEV world-model rollouts, whereas Vault's scorer predicts the official metric directly from the current observation, without simulation. DrivoR was already cited in six places. We use its no-SimScale variant for comparability.
Q2: The perfect-score gate explains the pattern, in two steps. First, the maximum score admits any collision-free trajectory that advances at least as far as the reference, so the pool can contain and the generator can learn farther-advancing trajectories. This matters because the human reference itself scores only EP 87.5 on navtest (the simulated rollout travels less far than planned), so longer certified anchors directly raise the progress the planner can express. Second, the supervision is nearly flat along safety dimensions: among feasible candidates, satisfying versus violating TTC differs only marginally, and NC, DAC, TTC are near their ceilings (99.0/98.8/96.4), while progress varies widely among perfect-score trajectories. Comfort is honestly traded (99.0 vs. 99.9 human). Three results support this:
Q3: We added a quantitative diversity analysis (App. D, blue). With the pool, candidate sets are roughly five times wider (pairwise ADE 1.95 vs. 0.38 m) and span 10.75 certified endpoint clusters (Q-Cluster@2 m over candidates with true PDMS ≥ 0.8) versus 1.71, and the oracle ceiling rises from 98.0 to 99.3. The expert-only model in fact has more high-scoring candidates (895.7 vs. 774.5; mean score 0.853 vs. 0.792): the pool contributes certified mode coverage, not candidate count or average quality, which is why quality and multimodality improve together. Against iterative denoising at the same backbone, scorer, and budget (Sec. 4.3), the diffusion decoder trades progress for comfort (92.0 vs. 94.6; EP 86.5 vs. 92.9; comfort 100.0 vs. 99.0). On pool evolution: the pool refreshes once per epoch (App. G) and per-scene anchor coverage saturates within the first 2–3 epochs, reaching the steady-state branches of Fig. 2 (later epochs only add density), and since each iteration subsamples at most M = 32 anchors, the effective supervision stabilizes early. App. C (Fig. 5, Table 4) already visualizes the VAE latent space against physical and PCA spaces. We are happy to post per-epoch pool statistics or latent anchor plots during the discussion period.