- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper proposes EvoAD, which combines a latent world model, a trajectory evaluator, and retrieval-guided refinement to improve driving decisions without retraining the base planner. On NAVSIM, performance improves over repeated reflection rounds, reaching 93.4 PDMS on v1 and 91.5 EPDMS on v2; seperate experiments test memory transfer across data splits.
Critical strengths
The paper presents a coherent pipeline that combines latent future prediction, trajectory evaluation, and retrieval-guided refinement to improve driving decisions without retraining the base planner. Ablations, cross-split memory tests, evaluations across different planners provide useful evidence of the framework's effectiveness and applicability.
Critical weaknesses
-
Although the paper compares EvoAD with a GTRS-based baseline, it does not isolate the contribution of the latent world model features within the proposed FAE. An ablation that keeps the FAE unchanged while removing candidate-conditioned future latents would clarify how much of the gain comes specifically from world model predictions.
-
The evaluation lacks validation in a fully interactive closed-loop simulator. NavHard uses a two-stage pseudo-simulation protocol with pre-generated future observations, rather than a fully interactive closed-loop simulator. Evaluation in a simulator such as HUGSIM would better test whether EvoAD's gains persist when observations and surrounding-agent states evolve in response to the ego vehicle's actions.
Questions for authors
- Could the authors evaluate EvoAD in HUGSIM using a fixed memory built from NAVSIM navtrain or navval, without incorporating feedback from HUGSIM evaluation scenes? This would test whether the gains transfer to a fully interactive closed-loop setting.
- Since same-scene refinement uses each navtest scene’s own PDMS feedback from a previous round, using navtest memory raises a potential test-set leakage concern. Would it be more appropriate for Table 1 to report results using navtrain/navval memory as the primary results?
- Figures 1 and 2 be revised for clarity. Figure 1's vehicle placement appears awkward, while Figure 2 is too dense and small to read easily.
Response to Reviewer
W1
Thank you for your comment. To isolate the contribution of the latent world model features within FAE, we supplement an ablation that removes the future feature input from FAE and retrain the evaluator from scratch under the same training setup. As shown in Table A below, without future latent predictions, the variant reaches 89.92 PDMS at R1 and 92.44 PDMS at R5. Adding future latents in the main FAE raises PDMS by 0.66 points at R1 and 0.92 points at R5. These future latents help FAE better distinguish high-quality candidates beyond static scene and trajectory inputs alone, yielding consistent planning gains. We have added this ablation to the revised manuscript.
Table A: Ablation of future latents in FAE.
Revised Contents: Please see p. 19 (lines 1023–1025) and p. 20 (lines 1026–1035).
W2
Thank you for your suggestion; we add a new experiment to test EvoAD on HUGSIM. Since HUGSIM provides only camera observations, we adapt WoTE to image-only inputs and retrain the latent WM on NAVSIM visual features. During closed-loop evaluation, all model weights remain frozen while execution feedback updates the memory across rounds.
As shown in Table B, EvoAD raises HD-Score from 47.6 at R1 to 65.4 at R5 (+17.8 points), outperforming the 40.2 WoTE baseline. These results suggest that EvoAD's multi-round refinement remains effective under closed-loop execution. We have included these results in the revised manuscript.
Table B: Multi-round closed-loop evaluation on HUGSIM.
Revised Contents: Please see p. 9 (lines 435–439), p. 13 (lines 689–693), p. 20 (lines 1072–1079), and p. 21 (lines 1080–1085).
Q1
Thank you for your suggestion. To test whether the gains from a fixed NAVSIM memory transfer to a fully interactive closed-loop setting, we evaluate EvoAD on HUGSIM using a read-only memory bank built from
navtrain. All model weights remain frozen during closed-loop evaluation, with no HUGSIM trajectories or feedback incorporated; EvoAD retrieves the pre-builtnavtrainmemory bank for similar driving scenarios to perform single-pass PAR refinement and FAE selection.As shown in Table C, EvoAD achieves 55.7 HD-Score, outperforming the 40.2 WoTE baseline by 15.5 points. These results suggest that offline experiences from NAVSIM can effectively transfer to an interactive closed-loop environment without target-scene feedback. We have included this experiment in the revised manuscript.
Table C: Cross-domain single-pass evaluation on HUGSIM.
navtrainMemoryRevised Contents: Please see p. 9 (lines 437–439), p. 20 (lines 1073–1079), and p. 21 (lines 1080–1085).
Q2
Thank you for your comment. EvoAD is developed to empower a pre-trained frozen planner with post-deployment self-evolving capability. Therefore, the five-round evaluation in Table 1 aims to verify continual improvement across rounds. While cross-domain evaluation using
navtrainornavvalmemory also achieves competitive results, this setting tests memory generalization rather than continual self-evolution. We therefore retain the multi-round results as the primary results in Table 1.Regarding your concern about potential test-set leakage, we clarify that EvoAD accumulates and leverages past experiences without using them to update the parameters of the pretrained models. Such experience-driven approaches have been widely explored in autonomous driving, such as DiLu [1] and Drive Like a Human [2], where accumulated experiences are used to improve driving performance.
[1] Wen, Licheng, et al. "Dilu: A knowledge-driven approach to autonomous driving with large language models." International Conference on Learning Representations. Vol. 2024. 2024.
[2] Fu, Daocheng, et al. "Drive like a human: Rethinking autonomous driving with large language models." 2024 IEEE/CVF Winter Conference on Applications of Computer Vision Workshops (WACVW). IEEE, 2024.
Revised Contents: Please see p. 1 (lines 29–31), p. 8 (lines 378–393), p. 13 (lines 699–701), and p. 15 (lines 804–809).
Q3
Thank you for pointing this out. In the revised manuscript, we have adjusted the vehicle placement in Figure 1. We have also enlarged the text and simplified the layout in Figure 2.
Revised Contents: Please see p. 2 (lines 54–67) and p. 3 (lines 108–128).