- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
OccWAM combines video, 4D occupancy, and trajectory generation within a flow-matching mixture-of-transformers architecture. Its trajectory-conditioned occupancy routing mechanism selects a small subset of occupancy tokens around candidate motion corridors. Experiments on NAVSIM and nuScenes study planning quality, occupancy prediction, and the accuracy-efficiency trade-off of routing.
Critical strengths
(+) The motivation for combining appearance with explicit volumetric structure is clear. Occupancy provides a useful spatial representation for planning, and the paper implements a concrete mechanism for reducing the cost of processing it.
(+) The controlled comparisons show consistent planning improvements: the full model reaches 91.1 PDMS versus 89.9 for Video-Action, and reduces average nuScenes L2 error from 0.41 to 0.36 and collision rate from 0.16% to 0.12%.
(+) The routing study includes both full occupancy and random token selection. Selecting 64 of 625 tokens preserves most of the reported displacement accuracy while reducing latency from 4701 ms to 2841 ms. The comparison with ground-truth current occupancy also usefully exposes sensitivity to perception quality.
Critical weaknesses
(-) The existing ablations do not fully isolate the value of predicting future occupancy from the benefit of extra 3D supervision, input information, or model capacity. Static occupancy conditioning and an Occupancy-Action model without the video expert would be particularly informative controls.
(-) The current experiments are primarily conducted on nuScenes and NAVSIM. Would it be possible to consider supplementing them with experiments on NAVSIM v2, so as to further substantiate the effectiveness of the proposed method through results that are more oriented toward closed-loop evaluation?
Questions for authors
-
Can the authors add static-occupancy and Occupancy-Action controls to separate future prediction from additional perception information and the video expert?
-
How do FullOCC and routed occupancy compare on collision metrics and cases where a hazard initially lies outside the selected corridors? What fraction of relevant occupied regions is retained?
-
Which camera views are used by the current-occupancy estimator, and is its runtime included in the latency? Please report hardware, denoising steps, and component-wise inference costs.