- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper introduces RoleDrive, which categorizes scene representations for end-to-end autonomous driving into three types: Context, which captures global scene context; Map, which provides local geometric structure; and Evolution, which represents temporal changes through residuals of historical features aligned with the ego vehicle's motion. Planning queries first attend to Context and then jointly attend to Map and Evolution, enabling staged interaction with different types of information. The authors evaluate the method on NAVSIM and HUGSIM, reporting a PDMS of 94.9 on NAVSIM v1, an EPDMS of 91.5 on the NAVSIM v2 navtest single-stage evaluation, and an HD-Score of 34.2 on HUGSIM. The paper also includes ablations of representation combinations, temporal fusion, and interaction order.
Critical strengths
-
The architecture is coherent and addresses a practically important problem. Global scene information, local geometric constraints, and historical dynamics correspond to distinct information requirements in trajectory planning. Organizing these elements into representations that can be directly used for planning is sensible. The explicit motion alignment used to reduce ego-motion effects in temporal residuals is also well motivated.
-
The ablations provide consistent, although relatively modest, evidence for the proposed components. In Table 4, the Context + Map configuration achieves a validation PDMS of 92.5, which increases to 92.9 after adding Evolution. Aligned residuals outperform unaligned residuals (92.7), and progressive interaction outperforms joint interaction (92.5). These results suggest that the gains are not attributable solely to the final configuration. However, the stability and precise source of these gains require further verification, as discussed below.
Critical weaknesses
-
The paper does not yet isolate the contribution of its proposed division of roles. The main innovation appears to be a combination of existing mechanisms. ResWorld (https://arxiv.org/html/2602.10884v1) already uses motion-aligned temporal residuals, while DiffRefiner employs staged global and local interactions. The authors should clarify what capabilities are enabled specifically by the three-way division into Context, Map, and Evolution and by the proposed interaction pattern, beyond what could be obtained by combining these prior mechanisms. The improvements in the key ablations are small (approximately 0.2–0.5 PDMS), and all experiments appear to use a single random seed. The paper also does not clarify whether Joint versus Progressive and Fusion versus Evolution are matched in parameter count, decoder depth, or computational budget. In addition, the residual-weighted visualization of Evolution and the CKA analysis only establish statistical differences between representations; they do not by themselves demonstrate a semantic division of labor. Finally, the paper does not discuss CLOVER (https://arxiv.org/abs/2605.15120, May 2026), which uses a DrivoR-style planning framework and reports a PDMS of 94.5 and a navtest EPDMS of 90.4 under a revised protocol. This is an important reference point for assessing the actual improvement.
-
The evaluation protocols raise concerns about the validity of the main conclusions. Appendix B states that both K=2 and K=3 obtain a validation score of 92.9, but K=3 was selected because the test-set results favored it. If the test set was used to select the default configuration, the reported test performance is no longer independent of model selection. The HUGSIM comparison also contains important confounding factors. RoleDrive is initialized with the V0 policy for 1.5 seconds before taking control, whereas DrivoR starts driving from the first step. The two methods also use different treatments of extrinsic parameters and lateral-acceleration inputs. More importantly, the original DrivoR paper reports RC/HD-Score values of 49.8/35.7, whereas the reproduction in this paper obtains 46.4/31.0, compared with 48.0/34.2 for RoleDrive. Until these reproduction discrepancies are explained and the system configurations are standardized, the observed closed-loop difference cannot be reliably attributed to the proposed architecture. The EPDMS of 91.5 should also be explicitly contextualized as a single-stage navtest result and should not be directly compared with navhard or full two-stage evaluation results.
Questions for authors
-
Configuration selection: Was K=3 fixed before the navtest results were first accessed? Please describe the exact experimental sequence leading to the statement that “test set results favor K=3,” including how many configurations were evaluated or selected using test-set performance.
-
Closed-loop comparison: Why does the reproduced DrivoR HD-Score decrease from the original 35.7 to 31.0? Does RoleDrive retain an advantage when initialization policy, extrinsic-parameter handling, vehicle-state inputs, and simulator corrections are standardized across both methods?
-
Verification of the claimed contributions: Are model capacity and computational budget matched between Fusion and Evolution and between Joint and Progressive? Are the reported gains stable across multiple random seeds? If the interaction order is reversed, or if representational interventions are designed around different information needs, do the claimed roles and division of labor remain valid?
10 comments
Response to W1 (Part 2/2): Multi-Seed Ablations, Model Capacity, and Functional Evidence
Multi-seed ablations and controlled comparisons. We repeated two ablations with training seeds 0 and 1 in addition to the original seed 2. All runs used the same data split, 25-epoch training budget, and checkpoint-selection rule based on validation PDMS. The full Progressive model is the common reference. Each gain below is computed between runs with the same seed.
Adding Evolution Tokens (validation PDMS)
| Seed | Context + Map | Context + Map + Evolution (Progressive) | Gain |
|---|---|---|---|
| 0 | 92.598 | 93.023 | +0.425 |
| 1 | 92.680 | 93.133 | +0.453 |
| 2 | 92.536 | 92.869 | +0.333 |
| Mean | 92.605 | 93.008 | +0.404 |
Progressive versus Joint interaction with all three token groups (validation PDMS)
| Seed | Joint | Progressive | Gain |
|---|---|---|---|
| 0 | 92.453 | 93.023 | +0.570 |
| 1 | 92.492 | 93.133 | +0.641 |
| 2 | 92.500 | 92.869 | +0.369 |
| Mean | 92.482 | 93.008 | +0.527 |
Both gains were positive for all three seeds. The paired gains were 0.404 ± 0.063 PDMS points for adding Evolution and 0.527 ± 0.141 for Progressive over Joint (mean ± sample standard deviation across seeds).
| Variant | Total parameters | Trainable parameters |
|---|---|---|
| Full Joint | 36,853,791 | 13,810,719 |
| Full Progressive (with Evolution) | 36,853,791 | 13,810,719 |
| Direct Fusion | 36,517,663 | 13,474,591 |
Joint and Progressive match in parameter count and decoder depth. Both have five trajectory interaction layers. Joint reads all three token groups in every layer. Progressive reads Context in the first two layers and all three groups in the final three.
Direct Fusion and Evolution each use five trajectory interaction layers and supply 5,120 spatial tokens in addition to 48 Context Tokens. Direct Fusion aggregates aligned historical Maps. Evolution first computes differences between the current and aligned historical Maps. In the original ablation, their validation PDMS scores were 92.4 and 92.9, respectively. Direct Fusion has 336,128 fewer parameters (0.91% of Evolution's total), so this comparison is close in capacity but not exactly matched. We will report measured computational costs under the same conditions. Additional multi-seed ablations are underway, and we will report their per-seed results alongside the two comparisons above in the supplementary material.
Functional evidence for role separation. To test whether the planner uses the information carried by each representation, we froze a model trained on navtrain. We replaced one token group at a time with its position-wise mean computed on navtrain and evaluated the model on navval. When replacing Context, we retained the visual initialization of the trajectory queries. We evaluated all 18,179 validation scenarios and the subset of 8,237 curved-driving scenarios in which the maximum absolute deviation of future ego heading from the current heading exceeds 10°.
| Replaced tokens | ΔPDMS, all scenarios | ΔPDMS, curved-driving subset |
|---|---|---|
| Context | −0.98 | −1.43 |
| Map | −32.15 | −39.27 |
| Evolution | −4.41 | −6.11 |
Each change is relative to the unmodified model on the same subset. Replacing any group reduced PDMS, with larger drops in the curved-driving subset. The interventions show that the trained planner relies on scene-specific information from each group. The visualizations provide evidence about what the groups attend to, and CKA measures differences in their learned feature structure. Together, these findings support the proposed complementary roles of global context, current local geometry, and recent change. We will add the intervention results to the main ablation section and document the intervention settings and curved-driving analysis in the supplementary material.
Response to W2: Configuration Selection and Evaluation Protocols
(1) History-length selection and independence of test evaluation. Thank you for asking us to clarify this choice. We chose K=3 because it retains a longer history window at little additional cost, while both K=2 and K=3 achieve a validation PDMS of 92.9 at the reported precision. With historical Maps already cached, K=3 increased measured inference latency by only 0.04 ms, peak GPU memory by 0.003 GB, and cache size by 2.62 MB relative to K=2. We fixed K=3 before first inspecting the navtest results.
- We compared K=0, 1, 2, and 3 on the validation set.
- We selected and fixed K=3 based on validation performance and resource use.
- For this history-length study, we evaluated only K=3 on navtest. Test performance did not influence the choice.
| Metric | K=2 | K=3 | Change |
|---|---|---|---|
| Validation PDMS | 92.9 | 92.9 | 0.0 |
| Parameters (M) | 36.854 | 36.854 | 0.000 |
| Forward latency with cached historical Maps (ms) | 78.69 | 78.73 | +0.04 |
| Peak GPU memory (GB) | 0.414 | 0.417 | +0.003 |
| Historical Map cache (MB) | 5.24 | 7.86 | +2.62 |
During continuous driving, each historical Map can be reused once encoded. Each planning step still retrieves and aligns the cached Maps. The reported latency includes these operations and excludes the initial encoding of a newly added historical frame. We will revise the appendix statement that “test-set results favor K=3” to describe the validation-based selection procedure and include the comparison above alongside the history-length ablation.
(2) HUGSIM reproduction and updated comparison. We aligned the initialization policy, camera extrinsic conventions, vehicle-state processing, controller settings, simulator corrections, and scoring protocol between RoleDrive and our DrivoR reproduction. Both take control from the first simulation step without V0 warmup. RoleDrive uses three forward-facing cameras, whereas DrivoR uses four cameras, including a rear camera. The other evaluation settings are consistent across our runs.
To handle missing history at startup, we fine-tuned RoleDrive for five epochs using only NAVSIM-v1 training data. In each batch, we randomly assigned samples to four equally sized groups retaining the most recent 0, 1, 2, or 3 historical frames, respectively. Every sample retained the current frame. Validity masks excluded missing observations from temporal differencing and aggregation.
Our earlier DrivoR reproduction obtained 46.4 RC and 31.0 HD-Score. After aligning the evaluation settings, our updated reproduction yielded scores close to the original report. Because several settings changed together, we cannot attribute the earlier discrepancy to a single factor. We therefore cite DrivoR’s published scores of 49.8 RC and 35.7 HD-Score as the reference below.
| Method | Camera views | Average RC | Average HD-Score |
|---|---|---|---|
| DrivoR (original paper) | 4 | 49.8 | 35.7 |
| RoleDrive (updated evaluation) | 3 | 51.6 | 36.6 |
| Gain over published DrivoR scores | — | +1.8 | +0.9 |
With one fewer camera, RoleDrive exceeded the published DrivoR scores by 1.8 points in average RC and 0.9 points in average HD-Score. We will update the HUGSIM table and document the shared settings, camera views, missing-history fine-tuning procedure, and score sources in the revised manuscript.
(3) Evaluation protocol for 91.5 EPDMS. We obtained 91.5 EPDMS on single-stage NAVSIM-v2 navtest by averaging the corrected evaluator’s scores over all 12,146 scenarios. Navhard and full two-stage evaluation use different protocols.
As stated in the Table 2 footnote, rescoring the same RoleDrive predictions yielded 87.8 before the evaluator fix and 91.5 after it. We evaluated our DrivoR reproduction under the corresponding pre-fix and corrected protocols. For literature comparisons, we retain the reported settings and identify the evaluator version where known. We will make the single-stage navtest scope explicit in the main text and table caption and retain the evaluator-version details in the table notes.
Response to W1 (Part 1/2): Novelty and Comparison with Prior Work
Ego-motion alignment, temporal differencing, and staged attention are established techniques. Prior work has paid less attention to how the roles of different types of scene information in trajectory planning should guide their representation. RoleDrive’s contribution is to assign explicit planning roles to intermediate scene representations and use those roles to determine how each representation is constructed and when the planner reads it. This design reflects how drivers assess the overall traffic situation while paying particular attention to the road they are about to enter. Context first guides the trajectory queries with an overview of the scene. During refinement, the planner retains Context and reads Map and Evolution at corresponding locations in the region ahead. Map provides the current local geometry, while Evolution captures recent changes, allowing the planner to use both “what is here now” and “what has recently changed here” to refine the trajectory.
Comparison with ResWorld. Compared with ResWorld, RoleDrive gives the planner more direct access to recent changes at specific locations ahead and saves the computation required to predict future BEV features. ResWorld pools aligned BEV features across the full grid into sparse scene queries using a shared spatial attention mask. Its world model uses differences between queries at adjacent time steps to predict future BEV features for trajectory refinement. RoleDrive retains an overview of the visible scene through Context. On the forward local grid, it subtracts each aligned historical Map from the current Map at cells with valid overlap and preserves each cell’s location during temporal aggregation. Figure 3 of our paper illustrates the benefit during a turn. Map immediately provides the geometry of a region that has just come into view. The validity mask excludes missing historical observations from differencing, so entering the field of view does not itself register as a scene change. Where coverage overlaps, the planner reads current geometry from Map and recent change from Evolution at the same cell. Our paper already cites ResWorld in its discussion of future scene prediction. We will make this comparison explicit in the revision.
Comparison with DiffRefiner. Compared with DiffRefiner, RoleDrive gives the planner separate access to overall scene context, current local geometry, and recent changes, so each can guide trajectory refinement according to its planning role. In DiffRefiner’s semantic interaction module, global and local attention draw from the same pool of BEV-derived features. In RoleDrive, the three inputs already differ in construction and physical structure before attention. Context summarizes the scene without fixed BEV locations. Map and Evolution share a local grid, allowing the planner to first use Context for an overall view, then retain it while reading current geometry and recent changes at corresponding cells to refine the trajectory. We will cite DiffRefiner and clarify these architectural differences in the revision.
Comparison with CLOVER. CLOVER reports 94.5 PDMS on NAVSIM-v1 and 90.4 EPDMS on NAVSIM-v2 navtest under the revised protocol. RoleDrive achieves 94.9 and 91.5, respectively. We have added CLOVER to both comparison tables.
CLOVER uses evaluator-filtered pseudo-expert trajectories to expand supervision beyond a single logged trajectory, then refines the generator through conservative self-distillation. We particularly appreciate how ranking feedback helps the generator produce better candidates. The approaches are complementary. CLOVER focuses on generating and ranking candidate trajectories. RoleDrive focuses on assigning distinct planning roles to intermediate scene representations and using those roles to guide trajectory refinement. We will cite CLOVER and discuss this relationship in the revision.