- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
This paper presents STEER, a diffusion-based end-to-end driving framework designed to improve the geometric and kinematic feasibility of generated trajectories. STEER consists of four main components:
- Scene-Conditioned Anchor generation (SCA), which adapts trajectory anchors to the current scene;
- Graph Attention-based Agent Interaction (GAI), which introduces distance-based locality into agent interaction;
- Adaptive Dual-Path Trajectory Refinement (ADPT), which combines one-shot global prediction with segment-wise autoregressive refinement;
- Hierarchical Trajectory Selection (HTS), which applies learned scoring, kinematic penalties, hard constraints, and PDM-based reranking. The paper reports a PDMS of 93.8 on NAVSIM-v1 and an EPDMS of 87.2 on the reported NAVSIM-v2 navtest protocol. And it operates at 128.36 ms per frame, corresponding to 7.79 FPS on an NVIDIA A100.
Critical strengths
- The paper addresses a practical limitation of diffusion planners.、
- This paper is easy to understand and follow.
- The paper reports useful performance-latency ablations.
Critical weaknesses
- I find the paper to be a reasonable engineering integration of several physically motivated techniques such as map informations and hard constraints. I am not convinced that it constitutes a sufficiently novel or rigorously validated contribution for ICLR. In this context, describing STEER as “a next-generation diffusion framework” seems overstated.
- compared with recent strong baselines such as DrivoR (CVPR 2026), STEER does not show a clear advantage. The experimental results on NAVSIM are also not sufficiently compelling to support the claimed state-of-the-art performance.
- The paper lacks generalization and reactive closed-loop validation in stronger simulators such as AlphaSim or HUGSIM.
Questions for authors
- Is STEER camera-only or camera-LiDAR? What exactly is meant by the “shared image-LiDAR backbone”?
- Can the authors report multiple runs with standard deviations and a leave-one-out ablation starting from the full system?
- Does the 128.36 ms latency include perception and all selection stages?
- How much of the improvement remains when all methods use the same number of candidate trajectories and the same PDM reranking budget?