- Rating
- 4(+1)
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper presents GeoWAM, a geometry-centric world-action model for autonomous driving. A pretrained visual geometry encoder and a future decoder predict dense future point maps and features, which are used by a trajectory decoder. The method is evaluated on geometric forecasting, NAVSIM v2, and zero-shot nuScenes planning, with additional experiments on pretraining data scale.
Critical strengths
(+) The use of explicit metric geometry provides a clear connection between future prediction and motion planning. The architecture and its supervision are reasonably motivated, and the current-only versus future-geometry ablation directly examines an important design choice.
(+) The planning results are promising. Without additional PAI data, future geometry improves the reported navhard score from 31.7 to 36.6; the full model reaches 39.6. The zero-shot nuScenes results also show improvements in average displacement and collision metrics over the reported DVGT-2 baseline.
Critical weaknesses
(-) Explicit future-geometry prediction introduces additional computation and memory requirements, but its practical cost remains unclear. Table 7 reports parameter counts, while Table 6 demonstrates planning gains from longer prediction horizons without quantifying the corresponding inference overhead. Could the authors report end-to-end latency and peak GPU memory for the current-only baseline and different prediction horizons under the same hardware and input settings? Please also clarify whether dense point-map decoding is required during planning inference or whether the planner operates solely on future geometry tokens. These results would help establish whether the planning gains justify the additional computational cost.
(-) Could the authors explore whether the planning benefits of future-geometry modeling can be retained through training-time distillation, inspired by future-prior distillation approaches such as AMap? Specifically, a student planner could learn from the full GeoWAM teacher while omitting the future-geometry prediction branch at inference. Comparing this student with the full model in planning performance, latency, and peak memory would help clarify how much of the benefit requires explicit future prediction at deployment.
[1] AMap: Distilling Future Priors for Ahead-Aware Online HD Map Construction, CVPR 2026
Questions for authors
Q1: What are the end-to-end inference latency and peak memory at the reported input resolution, and how does performance change under a practical inference budget?
Q2: How does geometric accuracy vary between static and moving objects?