- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper proposes FreqLift, a BEV-based 3D object detection method for LiDAR--camera fusion. CameraBEVRefiner first refines camera BEV features generated by LSS using smooth and detail residual branches with a gating mechanism, before fusing them with LiDAR BEV features. WaveLift then performs cross-frequency interactions through a three-level Haar wavelet decomposition, while Freq-Mamba models spatial features using four-directional scanning and state-parameter modulation. The detection head follows a TransFusion-style design and incorporates high-frequency responses as a bias in the candidate heatmap.
Critical strengths
S1. The Refiner shows clear gains in the internal comparison. In Table 4, adding the Refiner increases mAP from 68.5 to 71.2 and NDS from 71.7 to 73.1 while sharing the LiDAR checkpoint, WaveLift, detection head, and training settings. This supports the value of refining camera BEV features before fusion.
S2. Effective use of complementary information from the camera modality. The method addresses feature uncertainty after camera view transformation and the multiscale structure of BEV features without relying on an external camera-only 3D detector. The camera branch's ResNet-50 still uses ImageNet pretraining.
Critical weaknesses
W1. The WaveLift/Freq-Mamba ablations are not sufficiently convincing. All ablations in Table 3 retain DWT, WCG, and Freq-Mamba, varying only the number of levels, heatmap bias, or modulation. They are also conducted only in the LiDAR-only configuration. Without comparisons against no WaveLift, a capacity-matched CNN, and a standard Mamba without wavelets under the full fusion setting, the gains from cross-frequency modeling cannot be separated from those due to additional capacity or receptive field. Given precedents such as WaveMamba and VoxelMamba, this directly affects the assessment of the added contribution.
W2. The scope of applicability and cost-benefit trade-off remain unclear. The method is evaluated only on nuScenes validation and the current architecture, while the high-frequency heatmap bias may depend on a specific detection head. Could the authors test on other benchmarks and verify whether the modules can be integrated into another BEV detector? Latency/FPS, memory usage, and the overhead of the main modules should also be reported under the same hardware, batch size, and numerical precision. In Table 1, IS-Fusion (CVPR 2024) achieves 72.8 mAP / 74.0 NDS, compared with 71.2 / 73.1 for this method.
Questions for authors
- What advantage does the Refiner offer over a residual convolutional module of equal capacity? Can results under controlled depth errors or extrinsic calibration perturbations support its intended noise-suppression role?
- The paper does not report inference speed. Could the authors provide end-to-end latency or FPS under the same hardware, batch size, and inference precision, and compare against the baseline to quantify the speed overhead of the added modules?
- Figure clarity and typesetting: The module hierarchy and connections in Figure 2 should be clearer. In Sec. 3.1.1 on page 3, MambaGu & Dao (2023) lacks a separator between the model name and the citation.
3 comments
Thank you very much for your interest in our work; we are truly delighted by it.
Regarding the contribution of "bevrefiner," we have already provided a response within our overall official comments. Subsequent validation experiments indicate that the contribution of the "refiner" module could not be substantiated, which we find quite regrettable.
Although we initially considered not responding further, we decided to provide a reply out of respect.
Your other suggestions have been invaluable in enhancing the completeness of our work, and we have learned a great deal from them. We will address these issues in future versions.
Thank you once again.
Thanks to the authors for their candid response. Wish you all the best in your future research.
As the discussion phase is drawing to a close, I would be very glad to discuss with the authors if they are willing to respond. If the authors do not reply, I will keep my recommendation score unchanged.