- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes DriveAnchor, a three-stage autonomous driving planning framework built on a real-trajectory vocabulary: first, it learns trajectory residual correction via flow matching; then it uses road-corridor conditioning to guide trajectory initialization; finally, it applies trajectory-anchor-guided zeroth-order optimization to incorporate non-differentiable reward feedback for fine-tuning the deterministic generator. The authors validate the method on nuPlan, an internal dataset, and real-vehicle scenarios. Overall, the main contribution of this work lies in the integration of the planning system and engineering practice, while the innovation at the machine learning methodological level is relatively limited.
Critical strengths
-
Real-vehicle deployment demonstrates good engineering practicality. The authors show scenarios such as lane changes, pedestrian interactions, intersection turns, and construction zones, and report trajectory generation efficiency on an onboard Orin platform. These results demonstrate the ability to integrate generative planning methods into an actual driving system, which is the most commendable part of this paper.
-
Black-box reward adaptation has practical value, and the internal experiments also show clear gains. For deterministic generators without an explicit probability density, using external rewards to improve candidate trajectories has a reasonable application motivation. Table 2 shows that reward fine-tuning can significantly reduce the static collision ratio among candidate trajectories; corridor guidance also improves the corresponding geometric compliance metrics. These results support the practical value of the framework to some extent.
Critical weaknesses
-
Limited ML novelty; necessity of the complex design is insufficiently justified. The three stages are largely a task-specific combination of existing ideas (trajectory priors, conditional guidance, reward optimization). The trajectory-vocabulary search direction in Stage 3 is somewhat distinctive, but the paper does not clearly articulate what generalizable learning mechanism or new insight it provides, nor does it show that the full pipeline is clearly superior to simpler alternatives with comparable training budgets.
-
Insufficient benchmark coverage and strong-baseline comparison. nuPlan experiments cover only sampled Val14 and Test14-hard scenarios and omit Test14. Diffusion Planner and Flow Planner are cited but not included in the main closed-loop comparison; public reports show their non-reactive Test14-hard scores without refinement are 75.99 and 76.47, versus 63.37 here. The authors need to clarify the core contribution given this clear SOTA gap. Diffusion Planner, Flow Planner
-
Candidate-level gains are not shown to translate into final closed-loop driving benefits. Ablations mainly focus on candidate-set static collision ratio, minimum trajectory error, and corridor compliance. But actual driving executes one selected trajectory; a better candidate set does not necessarily imply safer or more efficient final driving. The paper lacks a unified closed-loop ablation of the three stages, making it hard to assess each stage’s independent contribution and whether the gains justify the added complexity.
-
Lack of systematic closed-loop validation in high-interaction scenarios. The paper emphasizes closed-loop planning but does not evaluate on interaction-rich benchmarks such as Bench2Drive, which explicitly tests overtaking, merging, yielding, and emergency braking. Since the main ablations concern static collisions and corridor compliance, it remains unclear whether these improvements transfer to complex interactive decision-making. The authors should add such evaluation or justify why the method is unsuitable for Bench2Drive. Bench2Drive
Overall, I appreciate the value of this paper in autonomous driving system integration and real-vehicle deployment, and its contribution form is closer to application and system research in robotics or intelligent transportation. Measured by ICLR's requirements for machine learning contributions, the current methodological novelty and mainstream benchmark evidence are still insufficient to form a convincing case for acceptance. IMHO, in terms of either algorithmic innovation or benchmark metrics, at least one of them should be sufficiently outstanding.
Questions for authors
-
Limited ML novelty; necessity of the complex design is insufficiently justified. The three stages are largely a task-specific combination of existing ideas (trajectory priors, conditional guidance, reward optimization). The trajectory-vocabulary search direction in Stage 3 is somewhat distinctive, but the paper does not clearly articulate what generalizable learning mechanism or new insight it provides, nor does it show that the full pipeline is clearly superior to simpler alternatives with comparable training budgets.
-
Insufficient benchmark coverage and strong-baseline comparison. nuPlan experiments cover only sampled Val14 and Test14-hard scenarios and omit Test14. Diffusion Planner and Flow Planner are cited but not included in the main closed-loop comparison; public reports show their non-reactive Test14-hard scores without refinement are 75.99 and 76.47, versus 63.37 here. The authors need to clarify the core contribution given this clear SOTA gap. Diffusion Planner, Flow Planner
-
Candidate-level gains are not shown to translate into final closed-loop driving benefits. Ablations mainly focus on candidate-set static collision ratio, minimum trajectory error, and corridor compliance. But actual driving executes one selected trajectory; a better candidate set does not necessarily imply safer or more efficient final driving. The paper lacks a unified closed-loop ablation of the three stages, making it hard to assess each stage’s independent contribution and whether the gains justify the added complexity.
-
Lack of systematic closed-loop validation in high-interaction scenarios. The paper emphasizes closed-loop planning but does not evaluate on interaction-rich benchmarks such as Bench2Drive, which explicitly tests overtaking, merging, yielding, and emergency braking. Since the main ablations concern static collisions and corridor compliance, it remains unclear whether these improvements transfer to complex interactive decision-making. The authors should add such evaluation or justify why the method is unsuitable for Bench2Drive. Bench2Drive
11 comments
Response to Reviewer EadH (Part 2/2): Closed-Loop Ablations and Interactive Scenarios (W3/Q3, W4/Q4)
W3 & Q3: Do candidate-level improvements translate into closed-loop gains? Component ablations are missing.
A3. We add public closed-loop comparisons for EF and RL.
The original public BASE model uses Stage 1 + Stage 2 without Stage 3; the new RL model adds two epochs of reward adaptation. All three configurations keep the scoring head and execution post-processing and use 3,000 candidates and FM×2 (EF×2 when enabled), on the paper's scenario lists.
| Configuration | Val14 NR | Val14 R | Test14-hard NR | Test14-hard R | Overall |
|---|---|---|---|---|---|
| BASE: EF + scoring head | 84.89 | 81.31 | 64.01 | 65.95 | 74.08 |
| No EF | 81.34 | 79.13 | 64.13 | 64.35 | 72.28 |
| RL | 83.11 | 81.15 | 66.90 | 66.89 | 74.55 |
Common valid counts: 99/99/99/97 (394 total). Overall is weighted by these counts. The same exception tokens are excluded across configurations; completed zero scores are kept. Deltas use unrounded means.
EF adds 1.80 points to the pooled score. Two RL epochs change Test14-hard NR/R by +2.89/+0.94 points and Val14 NR/R by −1.79/−0.15 points, yielding +0.47 points overall. Sub-metric means on the reported scenarios (0–100, higher is better):
| Sub-metric | BASE | No EF | RL | No EF − BASE | RL − BASE |
|---|---|---|---|---|---|
| No at-fault collision | 92.77 | 92.89 | 94.16 | +0.13 | +1.40 |
| Drivable-area compliance | 96.45 | 96.19 | 96.95 | −0.25 | +0.51 |
| Making progress | 91.88 | 90.86 | 91.62 | −1.02 | −0.25 |
| Progress along route | 67.01 | 66.14 | 67.39 | −0.88 | +0.37 |
| Driving direction | 98.73 | 98.60 | 98.98 | −0.13 | +0.25 |
| Time to collision (TTC) | 87.31 | 87.31 | 88.58 | 0.00 | +1.27 |
| Speed limit | 99.28 | 99.23 | 99.28 | −0.05 | 0.00 |
| Comfort | 91.12 | 90.10 | 91.37 | −1.02 | +0.25 |
The RL gains are concentrated in the safety-related items (collision +1.40, TTC +1.27, drivable area +0.51) while mean route progress changes by +0.37 and making progress by −0.25; on Test14-hard NR these three safety items are +2.53, +3.03, and +1.01. This matches the Stage 3 reward, which penalizes collisions with static obstacles and road boundaries. Removing EF mainly lowers making progress, route progress, and comfort. These comparisons evaluate the closed-loop task after downstream selection and execution, which directly addresses your question.
In addition, the internal closed-loop evaluation before and after RL covers 21,082 cases: passing cases rise from 9,441 to 9,656 and the pass rate from 44.78% to 45.80%; the pass rates for nudging and lane changing rise by 3.00 and 2.03 percentage points.
W4 & Q4: No closed-loop validation in complex interactive scenarios; Bench2Drive is suggested.
A4. The existing evidence already covers interactive closed-loop scenarios; Bench2Drive would be additional validation.
nuPlan includes non-reactive and reactive (R) settings; Val14 covers 14 scenario types, and Test14-hard consists of hard scenarios selected from them. The internal evaluation covers nudging, lane changing, merging, and intersection turns, and also overtaking, yielding, and emergency braking. Real-vehicle operation across cities further supports usability in a production system.
Bench2Drive offers a complementary CARLA-based evaluation of sensor-to-control driving. Integrating our planning module would add a perception front end and adapt the map/navigation and control interfaces, evaluating the combined system. The current Stage 3 reward targets static obstacles and road boundaries. In our deployment workflow, reward adaptation supports short updates targeting specific failure types and can be extended through other black-box rewards. Real-vehicle videos illustrating interactive situations can also supplement the anonymous project website.
The public reactive evaluation and internal interactive cases address executed behavior in the evaluated planning setting, while real-vehicle deployment demonstrates practical integration. Bench2Drive would extend this evidence to another sensor-to-control pipeline.
If these responses and the additional experiments have changed your view, we hope you will consider raising your score. Thank you for your time and your review.
Follow-up on Our Responses
Dear Reviewer,
Thank you again for your detailed and constructive review. In our response, we have clarified the positioning of this work as controllable trajectory generation for real-vehicle deployment and short-cycle black-box reward adaptation of an existing planner. We have also explained the distinct role that each of the three stages plays on the shared trajectory representation, and discussed how our training scale and setting differ from those of Diffusion Planner and Flow Planner.
In addition, we have added closed-loop component ablations of EF and RL on nuPlan, with the candidate count, decoder-call budget, and scoring head held fixed, to examine whether candidate-level improvements translate into execution-level benefits. We have further included a large-scale internal closed-loop evaluation covering interactive scenarios such as nudging, lane changing, merging, intersection turns, overtaking, yielding, and emergency braking, and clarified the relationship between Bench2Drive and our setting.
As the discussion period has now passed its halfway point, we would be grateful to know whether these additional results and clarifications have adequately addressed your main concerns. If any issue remains unresolved, or if any additional experimental details or analyses would be helpful for your assessment, please feel free to let us know. We would be very happy to provide further clarification and continue the discussion.
Thank you again for your time and consideration.
Best regards,
The Authors
Response to Reviewer EadH (Part 1/2): Contribution and Benchmark Positioning (W1/Q1, W2/Q2)
We thank the reviewer for recognizing the practical value of the real-vehicle deployment and of black-box reward adaptation.
W1 & Q1: Limited machine-learning novelty; the necessity of the three-stage design.
A1. Our contribution is a compositional planning framework built for real-vehicle deployment, with evidence for each component. The three components work on a shared trajectory representation and solve different problems:
(i) FM generates the candidates. A vocabulary of real trajectories supplies initial trajectories, and FM learns scene-conditioned continuous residuals.
(ii) EF applies geometric requirements such as corridors. Corridor compliance of the final output rises from 62.02% to 73.42% (Sec. 4.5). In the new nuPlan closed-loop runs (tables in Part 2), the overall score is 74.08 with EF and 72.28 without it; removing EF lowers the making-progress, route-progress, and comfort sub-scores by 1.02, 0.88, and 1.02 points.
(iii) RL improves candidates from black-box feedback. With FM×2 fixed, candidate static collision rates fall from 27.22% / 56.54% to 2.94% / 7.15% and minADE@80 from 2.27 m to 1.34 m (Table 2 of the paper). In the new nuPlan runs, two epochs of RL raise Test14-hard NR / R by 2.89 / 0.94 points and the overall score from 74.08 to 74.55; the no-at-fault-collision and TTC sub-scores rise by 1.40 and 1.27 points. On 21,082 internal cases, the pass rate rises from 44.78% to 45.80%.
(iv) Real-vehicle deployment. To balance trajectory diversity and the real-time compute budget, the on-vehicle system randomly samples six anchors from the vocabulary, generates six candidates, and uses a rule-based selector to choose the executed trajectory. The system operates on thousands of autonomous vehicles in urban areas across dozens of cities, with millions of kilometers of autonomous driving accumulated. The autonomous-driving share is 99%.
Stage 3 supports efficient and extensible reward adaptation. After generating a center trajectory, we construct exploration probes directly in output space and query their rewards without rerunning the generator for each probe. The vocabulary, neighbor-selection rule, and perturbation scale provide explicit interfaces for incorporating motion constraints and driving preferences while retaining the generator architecture and decoding procedure. With the same initialization and query budget, standard ZO gives 1.97% all-candidate static collision vs. 0.28% for ours (Appendix I.3, Table 8).
The adaptation stages reuse the existing generator and frozen scene encoder. Stages 1, 2, and 3 use 120M, 7.5M, and 2.5M samples and cost 902, 541, and 243 GPU·hours (Table 5). On nuPlan, the base FM uses about 21k samples; EF adaptation and the scoring head use 4,608 of them. This organization supports targeted updates to an existing planner with an explicit additional training budget.
The contribution combines a shared trajectory interface, measurable component effects, and execution-level evidence from public and internal closed-loop tests and real deployment. This deployment-oriented scope is consistent with the primary area under which the paper was submitted: "applications to robotics, autonomy, planning".
W2 & Q2: Limited benchmark coverage; a gap to the state of the art.
A2. We study controllable generation and feedback adaptation for real-world operation, and nuPlan serves to validate the approach under a public protocol.
On Test14-hard NR, Diffusion Planner and Flow Planner report non-refined scores of 75.99 and 76.47. Our paper reports 63.37 on its sampled subset (Table 1). On the common valid scenarios used in this round, BASE scores 64.01 and the model after two RL epochs scores 66.90.
There is also a sim-to-real gap: perception errors, the behavior of other traffic participants, control tracking errors, and on-board real-time constraints are not fully reproduced by any single simulation protocol. We therefore read public evaluation, internal closed-loop testing, and real-vehicle operation together.
Our public study examines the additional cost and benefit of adapting an existing generator. The base FM uses about 21k nuPlan samples for 3 epochs; EF adaptation and the scoring head use 4,608 of them for 7 and 12 epochs; this round adds 2 RL epochs. Diffusion Planner and Flow Planner report a different training regime: about one million scenarios, with 500 and more than 200 epochs, respectively. For a deployed planner, a practical question is how an existing model can be updated through a short training cycle targeting newly observed failures. The public EF/RL comparisons evaluate this incremental adaptation capability alongside base planning performance. The original model is on par with PlanTF on Val14 NR (84.80 vs. 84.72) and has the highest R score among the compared methods on both sampled subsets.