- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper proposes F2-Planner, which reduces redundant computation in autonomous driving by reusing the unexecuted portion of the previous trajectory. It first aligns the previous trajectory with the vehicle’s actual motion, then predicts waypoint-wise inheritance weights to jointly control its blending with current candidates and the sampling noise. A few generative refinement steps produce the new trajectory.On Bench2Drive, the method outperforms a four-evaluation baseline with only two neural function evaluations, reducing planning-head latency by 27.77%.
Critical strengths
- The problem is practically relevant. The paper addresses redundant generation costs in receding-horizon planning by leveraging the unexecuted portion of the previous trajectory to improve initialization, offering a reasonable approach to reducing inference costs in generative planning.
- The method is clearly designed and delivers measurable gains. Waypoint-wise inheritance weights jointly control the source distribution’s center and sampling spread, preserving existing driving intent while allowing outdated plans to be revised. With only two neural function evaluations, the method achieves a higher Driving Score than the four-evaluation baseline while reducing planning-head latency.
Critical weaknesses
- Response and recovery capabilities under a low computational budget are insufficiently evaluated. The paper’s main efficiency gains are demonstrated with two neural function evaluations, whereas event-response and recovery experiments involving erroneous history use four evaluations. It therefore remains unclear whether the highlighted low-latency configuration can promptly revise outdated or incorrect plans.
- Generalizability and system-level benefits remain unclear. The experiments use the same perception and control stack, and the results with a second generator do not establish transfer across different system architectures. Moreover, latency measurements cover only the planning head and are therefore insufficient to quantify the actual speedup of the complete driving system.
Questions for authors
- How does reducing inference from four to two NFEs affect event response and recovery from erroneous history? Do you have results for the two-NFE configuration showing whether the reported efficiency gains preserve these capabilities?
- What fraction of the complete sensor-to-control latency does the planning head account for, and what end-to-end latency reduction does the two-NFE configuration achieve?
3 comments
We would like to highlight two findings from the revision that directly address your main concerns: F2 can revise stale history at the two-NFE budget, and its computational savings remain measurable beyond the planning head.
At two NFEs, F2 responds and recovers faster than same-budget aligned warm-start. Each configuration uses its own closed-loop history under matched event and fault settings. F2 reduces response RMST by 39 ms and 25 ms in the longitudinal and abrupt-intent suites, and recovery RMST by 0.95 s and 1.14 s under single faults and sustained drift. All four paired 95% confidence intervals lie below zero (Tables A35–A38). RMST includes nonresponding and unrecovered cases, so these improvements are not restricted to successful cases.
Some RMST estimates increase when reducing F2 from four to two NFEs. Nevertheless, the direct two-NFE comparisons show that F2 retains the ability to revise outdated plans and improves on conventional aligned history reuse under the same refinement budget. This supplies the responsiveness evidence that was missing from our original quality–compute comparison.
The planning-head savings translate into an 11.58% reduction in measured observation-to-control-command latency. The baseline planning head accounts for 40.18% of total mean latency. After including input preparation, perception, control computation, command submission, and waiting time, F2-2 reduces the mean from 117.74 ms to 104.10 ms relative to Cycle-local-4. Its measured P95 and P99 latencies are also lower (Tables A50–A52). Thus, the broader processing costs reduce the relative speedup, but a system-level benefit remains under the measured setup.
The added Diffusion Planner/nuPlan evaluation also extends the evidence beyond the original stack. With the adaptation interface and two-NFE budget held fixed, F2 improves over aligned warm-start by 0.9–1.5 score points across all four settings, with each paired confidence interval above zero (Tables A39–A40). This supports applicability after adaptation and matched training.
We hope these results address the main concerns behind your assessment, and would appreciate your reconsideration of the rating in light of the revised evidence. Thank you for reviewing these additions.
Thank you for asking us to evaluate response and recovery at the same budget used for our efficiency results. Reducing F2 from four to two generator evaluations per cycle cuts mean system latency by 13.93% and increases the response and recovery time estimates. At the same two-NFE budget, F2 still achieves lower response and recovery RMST than aligned warm-start in all four tests.
Each configuration uses its own closed-loop history. RMST averages the time to respond or recover across all cases, counting cases with no response or recovery at the evaluation window limit. AWS denotes aligned warm-start.
| Metric ↓ | F2-4 | F2-2 | AWS-2 | F2-2 − F2-4 | F2-2 − AWS-2 (paired 95% CI where available) |
|---|---|---|---|---|---|
| Longitudinal response RMST | 0.463 s | 0.473 s | 0.513 s | +10 ms | −39 ms [−58, −17] |
| Abrupt-intent response RMST | 0.464 s | 0.493 s | 0.518 s | +29 ms | −25 ms [−42, −5] |
| Single-fault recovery RMST | 1.54 s | 1.84 s | 2.79 s | +0.30 s | −0.95 s [−1.33, −0.55] |
| Sustained-drift recovery RMST | 1.46 s | 1.75 s | 2.89 s | +0.29 s | −1.14 s [−1.54, −0.73] |
| Mean observation-to-control-command latency | 120.95 ms | 104.10 ms | 103.35 ms | −16.85 ms (−13.93%) | +0.75 ms |
All four paired RMST intervals for F2-2 versus AWS-2 lie below zero. The comparisons across NFE budgets and all latency differences are descriptive. The −39 ms longitudinal effect uses unrounded values (Tables A27, A31, A35–A38, and A50–A52).
Your question about the planning head’s share of total latency also prompted us to measure the full chain from observation to control-command submission. The planning head accounts for 40.18% of mean latency in Cycle-local-4. Compared with that baseline, F2-2 reduces the mean from 117.74 to 104.10 ms (11.58%), while increasing the Bench2Drive Driving Score from 96.01 to 96.65.
To address dependence on the original stack, we also evaluated F2 in Diffusion Planner on nuPlan. After adaptation and matched training, F2 improves over the same-budget aligned warm-start by 0.9–1.5 score points across both test splits and both traffic modes, with the adaptation interface held fixed (Tables A39–A40).
We hope these comparisons answer your question about what is gained and what is lost at two NFEs. Thank you for prompting us to measure that trade-off directly.
Response to Reviewer dGjB
Thank you for recognizing the practical motivation, methodological design, and computational benefits of our work. Following your feedback, we evaluated response and recovery at 2 NFEs, measured system-level latency, and validated our method on an independent planning system (references denote the revised manuscript).
1. Response and recovery when reducing from 4 to 2 NFEs.
We repeated the event-response and corrupted-history recovery experiments at 2 NFEs using the original event definitions, criteria, fault injections, and evaluation windows. Each configuration evolves using its own closed-loop history under matched event identities and exogenous conditions, with exactly two generator evaluations per cycle and no extra calls for F2 (Appendix K.1, p. 34). Compared against same-budget aligned warm-start (AWS), F2 reduces longitudinal and abrupt-intent response RMST by 39 ms and 25 ms (Tables A35–A36, pp. 34–35), and reduces single-fault and sustained-drift recovery RMST by 0.95 s and 1.14 s (Tables A37–A38, p. 35). All four paired 95% CIs lie strictly below zero, with RMST accounting for all non-responding and unrecovered cases.
Reducing F2 from 4 to 2 NFEs modestly increases RMST point estimates—for example, from 0.464 to 0.493 s for abrupt-intent response (Tables A27, A35, pp. 29, 34) and from 1.46 to 1.75 s for sustained-drift recovery (Tables A31, A37, pp. 33, 35). Because these cross-budget comparisons are descriptive (paired CIs for F2-2 vs. F2-4 are not reported), we do not claim that halving the budget is behaviorally cost-free or statistically equivalent to 4 NFEs. Rather, these results directly verify that F2 maintains effective response and recovery at 2 NFEs while achieving consistently lower RMST than same-budget AWS.
2. Planning-head contribution and end-to-end latency benefits.
We profiled the complete observation-to-control-command chain—covering input transfer and preparation, perception, planning, control computation and submission, and waiting time—excluding physical actuator dynamics (Appendix Q.1, p. 40). In Cycle-local-4, the planning head takes 47.31 ms, accounting for 40.18% of its 117.74 ms mean total latency (Table A50, p. 41). F2-2 lowers mean total latency from 117.74 to 104.10 ms, yielding an end-to-end reduction of 13.64 ms (11.58%; Tables A50, A52, p. 41). Of this reduction, 13.14 ms comes directly from the planning head, while the remaining 0.50 ms reflects minor non-planning runtime variance rather than algorithmic acceleration of perception or control.
Because perception and other non-planning stages remain fixed in the chain, the 11.58% end-to-end reduction is naturally smaller than the 27.77% relative reduction within the planning head. Within F2, moving from 4 to 2 NFEs lowers mean total latency from 120.95 to 104.10 ms (13.93%). At the matched 2-NFE budget, F2-2 takes 0.75 ms longer than AWS-2 due to the source constructor, so we do not claim a same-budget speed advantage (Tables A50–A52, p. 41). Table A51 (p. 41) reports P50, P95, and P99 latencies as descriptive runtime measurements under our test setup, not confidence intervals or cross-hardware guarantees.
3. Applicability beyond the original planning stack.
To evaluate cross-system applicability beyond replacing a generator within the same stack, we integrated F2 into Diffusion Planner on the nuPlan closed-loop benchmark, retaining its native scene encoding, joint prediction architecture, and control interface (2 NFEs, 8 matched training seeds, identical training data, budgets, post-processing, and controllers; Appendix L.1, pp. 35–36). Across Test14-random and Test14-hard under both non-reactive and reactive traffic, F2 improves over AWS by 0.9–1.5 points on the 100-point scale, with all four pointwise paired 95% CIs strictly above zero (Tables A39–A40, p. 36). Using a shared adaptation interface isolates the adaptive source update from aligned history reuse. These results extend our empirical validation to a distinct planning system and benchmark, supporting application after adaptation and matched source–refiner training rather than training-free transfer to arbitrary planners.
Thank you again for prompting us to connect planning-head efficiency with measured system-level latency and to directly evaluate response and recovery under the low-budget regime. We hope these additions thoroughly address your concerns.