- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
RoadOcc predicts occupancy from fixed roadside cameras using current and historical features. Its routing module combines fixed-coordinate history (Persist), motion-compensated history (Transport), and current observations (Refresh), supervised by motion state and semantic support. It achieves 65.29 mIoU and 32.37 dynamic mIoU on InfraOcc, outperforming STCOcc.
Critical strengths
- I find the P/T/R formulation well motivated for fixed roadside cameras. It separates motion compensation from the decision to reuse history.
- The evaluation is reasonably extensive, including component and routing ablations, transfer to other temporal models, and tests on Occ3D-nuScenes and with longer frame intervals.
- The paper is clearly written and easy to follow. The visualizations help explain motion compensation and the behavior of the three routes.
Critical weaknesses
- Table 6 shows that supervised routing helps, but the contribution of semantic support beyond motion-state supervision is harder to assess. A motion-only labeling baseline would be useful, particularly for slow objects whose P/T candidates may have similar support. Sensitivity to the support radius and 0.8 m/s velocity threshold is not reported. The paper acknowledges that support does not distinguish same-class instances, but does not evaluate the effect on history reuse.
- In Table 2, Other improves by 18.82 IoU points, accounting for roughly 30% of the overall mIoU gain. It is unclear which components produce this large improvement on a static class. Excluding Other still leaves a 3.34-point gain over STCOcc. Per-class voxel counts and results before and after adding P/T/R would make this result easier to interpret.
- The baseline adaptations need more detail. CRT-Fusion was developed for radar-camera detection, and Let Occ Flow uses self-supervised training. Please clarify the architecture and supervision used to adapt them. ST-Occ and GDFusion are cited but not evaluated. The Occ3D-nuScenes and temporal-gap tests assess the full model, leaving the generalization of P/T/R itself less clear.
Questions for authors
- For slow objects, how often do P and T yield different support outcomes? How sensitive are the results to the support radius and velocity threshold?
- Which components explain the large gain on Other? Can you provide per-class results before and after adding P/T/R?
- How were CRT-Fusion and Let Occ Flow adapted for camera-only occupancy prediction in terms of architecture and training supervision?