- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper introduces SRTDrive, a post-hoc trajectory refinement framework for end-to-end autonomous driving. Given the trajectory and scene features from a frozen planner, SRTDrive keeps the original trajectory as a reference candidate and generates several alternatives by applying progress, normal, and tangential deformations to it. A set-contextual selector then compares all candidates with the reference. It first excludes candidates that increase collision relative to the reference, and uses displacement error to rank equally safe candidates. The method is evaluated with seven frozen planners on nuScenes and with VAD on Bench2Drive.
Critical strengths
-
SRTDrive provides a practical post-hoc interface that does not modify the weights of the base planner. Keeping the original plan in the candidate set also gives the selector the option to retain it when the generated alternatives are unsuitable.
-
The Bench2Drive experiment shows a meaningful improvement with VAD as the base planner. SRTDrive improves both Driving Score and Route Completion while reducing collisions.
Critical weaknesses
-
My major concern is the limited novelty. Trajectory refinement around an initial plan is a well-established idea, and using a rectified-flow model to generate refined trajectories appears to be a relatively direct application of an existing generative technique. The paper should position this contribution more concretely against prior refinement methods, preferably with empirical results on Bench2Drive or nuScenes.
-
The nuScenes results do not consistently support the claimed safety benefit. Collision rate improves for only three of the seven planners. Thus, four out of seven planners receive no collision improvement, while the gains outside VAD are modest. Moreover, open-loop trajectory evaluation on nuScenes is known to be affected by ego-status shortcuts. A more informative planning benchmark such as NAVSIM would provide stronger evidence.
-
The ablation study is insufficient for a framework containing many components. For example, the paper does not study the effects of the components in candidate generation (e.g., progress/normal/tangential plan warping, path-local and global feature fusion, and rectified-flow decoder).
-
There are also some issues with presentation. Figure 1 provides little technical information beyond stating that the method generates and selects a refined trajectory.
Questions for authors
I don't have other questions. Please refer to the Critical Weaknesses section.
4 comments
Response to Reviewer SeU6 (Part 2/2)
Continued from Part 1/2.
2. Applicability on NAVSIM and component analysis
On nuScenes, collision metrics improved for only 3 of the 7 evaluated planners, with relatively small improvements outside VAD.
To complement the limitations of open-loop evaluation, including concerns about the ego-status shortcut, we applied SRTDrive trained for a 4-second prediction horizon to VADv2 [2] and evaluated it on 12,146 NAVSIM v2 inputs.
The following table summarizes the Single-Stage evaluation and additional Generator ablation and replacement experiments. For these experiments, we matched the initial weights, data, number of candidates, and training budget. The Selector was also trained for the same number of epochs for each Generator configuration.
The reported values are aggregate scores of the final selected trajectories, scaled to 100 points.
| Configuration | Non-reactive ↑ | Reactive ↑ |
|---|---|---|
| Original VADv2 | 82.167 | 81.936 |
| Full Generator | 82.166 | 81.926 |
| Without Progress | 82.136 | 81.906 |
| Without Normal | 82.132 | 81.912 |
| Without Tangential | 82.180 | 81.947 |
| Without Route-Local Features | 82.149 | 81.891 |
| Without Global Scene Features | 82.150 | 81.899 |
| Rectified Flow Replaced with Direct-Prediction Decoder | 82.097 | 81.907 |
Although NC, DAC, and TTC increased by approximately 0.02–0.03 points, the Full Generator did not improve the aggregate score over the original VADv2.
Except for removing Tangential, the ablated or replaced configurations produced slightly lower aggregate scores than the Full Generator. However, the differences are small, and we do not claim that these results establish the necessity of each component.
In particular, no additional benefit from Tangential was observed, while the direct-prediction Decoder achieved higher Comfort.
These are Single-Stage evaluation results and do not include Two-Stage evaluation. They should also be distinguished from the Bench2Drive closed-loop setting, which involves repeated replanning.
3. Clarifying the core architecture and the distinction between training and inference
We will revise Figure 1 to explicitly distinguish three components: reference-anchored trajectory deformation, the candidate set containing the unchanged original trajectory, and the Selector using inter-candidate attention and reference-relative features.
Collision information and ground-truth annotations will be connected only to the training-target computation path. This will clarify that SRTDrive does not perform explicit collision checking or collision-based rejection at inference time.
We will also align the explanations in Figure 2, Eqs. (6)–(8), and Appendix A.6 to ensure a consistent description of the training and inference procedures.
Thank you again for helping us clarify the distinction from existing approaches and the scope of our experimental validation.
References
[1] Zhang, J., Fu, Z., Xu, Z., Dai, W., Liu, Q., and Wang, Y. ResWorld: Temporal Residual World Model for End-to-End Autonomous Driving. ICLR, 2026.
[2] Jiang, B., Chen, S., Gao, H., Liao, B., Zhang, Q., Liu, W., and Wang, X. VADv2: End-to-End Vectorized Autonomous Driving via Probabilistic Planning. ICLR, 2026.
[3] Ang, S., Yang, Y., Chen, C., and Wang, Y. CLOVER: Closed-Loop Value Estimation & Ranking for End-to-End Autonomous Driving Planning. arXiv:2605.15120, 2026.
Additional Clarification on Novelty (Reviewer SeU6)
After posting our earlier response, we continued to reflect on your concern about novelty and felt that we should clarify the problem our work aims to address and how it differs from existing methods. We would therefore like to offer a further explanation of the motivation behind our approach.
As you noted, refining an initial trajectory or applying Rectified Flow is not, in itself, a new approach. SRTDrive aims to preserve the option to retain the original plan and learn whether to replace it with a generated alternative, without retraining or replacing the base planner. From this perspective, the distinction we wish to emphasize is using the original trajectory as a common reference for both alternative generation and learning whether to retain or replace the plan. We keep the original trajectory unchanged in the candidate set, and the selector learns this decision using inter-candidate relationships and reference-relative features. In particular, the training targets are constructed so that an alternative that worsens the collision metric relative to the original is not preferred merely because it has a lower L2 error. The comparisons with existing refinement methods and alternative selection designs presented in our earlier response were likewise intended to examine the effects of this design.
We recognize that this design does not guarantee improvements for every planner, and our results show limited gains or performance degradation for some planners. With these limitations in mind, we have clarified how our approach differs from prior work, the problem it seeks to address, and the scope of the contributions supported by our experiments in the revised manuscript. Reflecting further on your concern about novelty has helped us articulate our contribution more clearly. Thank you again for your valuable feedback.
Further Clarification of Our Core Contribution and Additional Experimental Evidence
Thank you very much for your careful review and thoughtful comments. We sincerely appreciate the attention you have given to the novelty and experimental validation of our work.
Your concern regarding the distinction between SRTDrive and existing trajectory refinement methods was particularly valuable to us. It encouraged us to reconsider how we communicate the central motivation of our approach and what experimental evidence is needed to support its contribution.
Following your suggestions, we have revised the related discussion and conducted several additional experiments. We would be grateful for the opportunity to briefly share the most relevant findings.
1. Clarifying the core contribution of SRTDrive
As you rightly pointed out, trajectory refinement and Rectified Flow are established techniques. We have therefore clarified that the main contribution of SRTDrive lies not in using Rectified Flow itself, but in integrating reference-anchored alternative generation with reference-relative retain-or-replace supervision.
SRTDrive preserves the original planner's trajectory unchanged as a candidate and uses it as the reference for learning whether a generated alternative should replace it. The Selector is trained to prioritize avoiding collision deterioration relative to the original trajectory, rather than simply scoring each candidate independently.
We have made this distinction more explicit in Section 2.2 and the revised architecture figures. We also added a direct comparison with ResWorld's FGTR and further clarified the differences from CLOVER (Appendix D.5).
2. Additional evidence for the proposed selection framework
To further examine whether this design provides benefits beyond conventional learned scoring, we compared the Full Selector with a Learned Pointwise Scorer using the same Generator.
In the Bench2Drive closed-loop evaluation, the Full Selector achieved a higher Driving Score (47.77 vs. 40.14) and fewer routes with collisions (86 vs. 108) (Appendix D.1, Table 8).
We believe this comparison provides meaningful empirical support for the contribution of the proposed selection framework.
3. Expanded experimental validation
We also extended our Bench2Drive evaluation to BevAD-M using the same SRTDrive checkpoint trained with VAD, without any additional training or fine-tuning. Under identical evaluation conditions, the Driving Score improved from 88.76 to 90.78, while routes with collisions decreased from 42 to 35.
In addition, we conducted NAVSIM v2 evaluations and Generator component ablations covering progress, normal, and tangential deformations, feature conditioning, and the Rectified Flow decoder (Appendix D.9.1).
We also added a new ablation isolating repair-trajectory supervision (Appendix D.9.2). Under matched 8-epoch training, repair supervision increased the collision-improving candidate generation rate from 41.27% to 55.56%.
We have reported the corresponding results and limitations in the revised manuscript to provide a more complete picture of the framework's behavior across different evaluation settings.
We would especially like to express our gratitude for your comments on novelty. They have helped us articulate more clearly the specific problem SRTDrive is designed to address and distinguish its contribution from the individual techniques on which it builds. We also appreciate your suggestions regarding broader evaluations and component-level analyses, which directly motivated several of the additional experiments.
We sincerely hope that the revised explanations and new experimental evidence help clarify the methodological contribution and practical significance of SRTDrive. If you have the opportunity, we would be truly grateful if you could kindly revisit the revised manuscript and consider these findings in your assessment.
Thank you once again for your valuable time, thoughtful feedback, and constructive suggestions. Your careful review has been especially helpful in strengthening both the clarity and experimental support of our work.
Sincerely,
The Authors
Response to Reviewer SeU6 (Part 1/2)
Thank you for your careful review and constructive suggestions. We agree that the differences from existing trajectory refinement methods and the contributions of individual components require clearer validation. The central contribution of SRTDrive is not Rectified Flow itself, but the use of the original trajectory as both an anchor for generating alternatives and a reference for learning retain-or-replace decisions based on relative collision outcomes.
1. Differences from existing refinement methods and the effect of the selection design
ResWorld's Future-Guided Trajectory Refinement (FGTR) [1] directly refines the initial trajectory using future BEV features. In contrast, SRTDrive preserves the original trajectory unchanged in the candidate set and uses inter-candidate relationships and reference-relative features to determine whether to retain or replace it.
The training target prioritizes avoiding increased collisions relative to the original and minimizing collisions, with L2 used to distinguish candidates within these priorities. This criterion is applied during training. At inference time, selection relies on learned scores without using ground-truth collision information or an additional collision threshold.
CLOVER [3] uses a Scorer that predicts evaluation metrics to improve the Generator and, when needed, reranks candidates according to their deviation from a reference trajectory. In contrast, SRTDrive preserves the frozen planner's original trajectory as both a candidate and the reference for training retain-or-replace decisions that prioritize avoiding collision deterioration.
To provide a direct comparison, we kept the official ResWorld model frozen and evaluated FGTR and an independently trained SRTDrive using the same initial trajectories. SRTDrive was trained separately using ResWorld features. The evaluation included 5,119 nuScenes inputs with valid future annotations.
SRTDrive achieved a lower collision metric than FGTR but a higher L2 error. Compared with the original trajectory, SRTDrive maintained the same collision metric while slightly increasing L2. Therefore, we do not interpret these results as an additional improvement over the original trajectory or as evidence of superiority over existing refinement methods in general.
We further evaluated the effect of the selection objective in a separate nuScenes experiment. Using identical initial weights, candidate sets, and training budgets (3 epochs), collision-prioritized supervision reduced replacements that introduced collisions absent from the original trajectory from 6 to 2 compared with L2-only training, while maintaining 10 cases in which original collisions were resolved.
Mean L2 increased from 0.6976 to 0.7076 m, while the mean collision metric decreased from 0.1519% to 0.1389%. This indicates that the collision reduction cannot be attributed simply to selecting trajectories closer to the ground truth. However, the reduction corresponds to only four inputs and does not establish a general safety guarantee.
We also compared the Full Selector with an additional Learned Pointwise Scorer in Bench2Drive over 220 routes. The Full Selector reported in Table 2 achieved a higher Driving Score (47.77 vs. 40.14) and fewer routes with collisions (86 vs. 108). The original VAD-Base results were 43.07 and 95, respectively.
Thus, simply adding a learned Scorer did not reproduce the improvements obtained with the full selection framework. This comparison evaluates the overall selection design and should not be interpreted as isolating the effect of any single component.
Continued in Part 2/2: NAVSIM evaluation, component analysis, and architecture clarification.