RCQFusion
3D object detection from camera and radar data
2 min readupdated
A model for 3D object detection in driving scenes that fuses camera and radar data (Camera–Radar 3D Detection). It outputs 3D coordinates and class predictions across three categories: Pedestrian, Cyclist, and Car. Built on MMDetection3D (a library for 3D object detection), the solution was released as part of an anonymous ICLR submission. Unlike vision-only detectors, it uses radar data and temporal links across frames to more accurately estimate the distance and position of road users. Useful for autonomous driving researchers and developers looking to reproduce experiments on the View of Delft (VoD) dataset.
Key features
- Camera and 5-frame radar modality fusion accounting for temporal relationships across sequence frames.
- Detection of three core road object classes: Pedestrian, Cyclist, and Car.
- Complete inference and validation pipeline included: a ready-to-use checkpoint, VoD data conversion scripts, and a bundled version of MMDetection3D 1.0.0rc6.
- Single- and multi-GPU execution support with half-precision (FP16) computation.
What you can do
- Evaluate 3D detection performance on the View of Delft validation split using the official AP11 metric.
- Use the provided checkpoint and data preparation scripts as a baseline for benchmarking your own camera–radar fusion algorithms.
- Run distributed inference across multiple GPUs to speed up generating 3D predictions for driving scenes.
Example
export VOD_DATA_ROOT=/path/to/vod
CUDA_VISIBLE_DEVICES=0 bash tools/infer_vod.shRead more
DetailsValidation (1,296 VoD frames, 3D AP11): overall mAP — 61.35% (Pedestrian 53.64%, Cyclist 76.23%, Car 54.18%), driving corridor (ROI) mAP — 77.92% (Cyclist up to 90.84%).
Environment: Linux, Python 3.8, PyTorch 1.9.1+cu111, mmcv-full 1.6.0 with CUDA operators; tested on an NVIDIA RTX A5000.
Limitations: the VoD dataset itself is not included in the repository and must be downloaded separately under a research license.










Comments