CLOCs-R: Radar-Assisted Camera-LiDAR Fusion for Long-Range Object Detection

Richard Beuck, John Nguyen, Sudip DhakalarXiv 2026 · arXiv

TL;DR

CLOCs-R extends the candidate-level fusion framework by incorporating radar data to assist camera and LiDAR in long-range object detection. While it successfully boosts detection accuracy at mid-ranges (30–50m), the study reveals that sparse radar returns alone struggle to distinguish distant vehicles from environmental noise, highlighting a significant "recall bottleneck" in late-fusion systems.

What Problem Does This Paper Address?

For autonomous vehicles to operate safely at highway speeds, they must detect objects hundreds of meters away. However, standard sensors have a "long-range problem":

  • LiDAR becomes extremely sparse with distance; a car that returns 2,000 points at 14m might return only 39 points at 63m.
  • Cameras lose depth precision as objects get smaller in the frame.
  • Radar can see out to 250m and measure velocity directly, but its data is "noisy," lacks height information, and often produces "ghost" returns from static objects like guardrails.

The authors aim to bridge this gap by adding radar evidence to CLOCs (Camera-LiDAR Object Candidates), a framework that rescores potential detections by looking at how well 2D camera boxes and 3D LiDAR boxes overlap.

Methods

CLOCs-R uses a "candidate-level" (or late) fusion approach. Instead of fusing raw sensor data, it takes the outputs of pre-trained, "frozen" detectors and tries to improve their confidence scores.

Fig. 1. CLOCs-R architecture, shown on a frame from the aiMotive dataset [17]. The frozen camera and LiDAR detectors produce candidates before NMS, radar returns gated around each 3D candidate give its radar features ϕj, and these are appended to every cell of column j of the pair tensor before the fusion network rescores each 3D box. Candidate boxes are generated from ground-truth labels for illustration.

The pipeline works as follows:

  1. Candidate Generation: A 3D LiDAR detector (SECOND) and a 2D camera detector (Cascade R-CNN) propose potential objects.
  2. Radar Association: Radar returns are accumulated over multiple sweeps and compensated for the car's own motion. These returns are matched to 3D candidates using a "gate" that widens with distance to account for sensor error.
  3. Feature Extraction: For every 3D candidate, the system calculates five radar features:
  4. Support: How many radar points fell in the box.
  5. Doppler Speed & Spread: The median velocity and how much that velocity varies (to distinguish moving cars from static clutter).
  6. Range Residual & Offset: How well the radar's distance measurement aligns with the 3D box's position.
  7. Fusion & Rescoring: These features are appended to a "pair tensor" representing camera-LiDAR overlaps. A small neural network then learns to output a new, more accurate confidence score for each 3D box.

Datasets

  • KITTI: Used primarily to verify that the implementation could reproduce the original CLOCs results.
  • aiMotive: The primary evaluation dataset. It is specifically designed for long-range perception, featuring annotations out to 200m, which is significantly further than standard datasets like nuScenes (70m) or KITTI (70.4m).

Key Insights and Ideas

  • The "Recall Bottleneck": Because CLOCs-R is a late-fusion method, it can only rescore objects that the 3D LiDAR detector already found. If the LiDAR detector misses a distant car entirely because it only has 2 or 3 points, no amount of radar fusion can recover it.
  • Residual Scoring is Essential: The authors found that simply replacing the original 3D detector's score with a fusion score actually hurt performance at long range. They introduced "residual scoring"—adding the fusion network's output to the original score—which allowed the model to keep the 3D detector's strengths while using radar/camera data as a corrective signal.
  • Radar's Identity Crisis at Range: At 100–200m, radar returns from real cars look remarkably similar to returns from false detections (noise). The "Doppler speed" feature helps, but the signal-to-noise ratio is much lower than at closer ranges, making it a weak discriminator for the fusion network.

Key Results

  • Mid-Range Boost: Radar consistently improved Bird’s-Eye-View Average Precision (BEV AP) in the 30–50m range, raising it from 0.857 to 0.870.
  • Long-Range Marginality: Beyond 50m, the gain from radar was small (+0.003 in center-distance AP). At these distances, the system was essentially "statistically tied" with the LiDAR-only baseline.
  • Efficiency: The radar feature extraction and fusion network add only about 19ms of latency per frame (on a single CPU thread/GPU), making it a lightweight addition to existing perception stacks.

Limitations and Future Work

The primary limitation is the recall ceiling mentioned above; future work might explore "cued" detection where radar proposals tell the 3D detector where to look more closely. Additionally, the authors noted a "label shift" between training and validation data that made strict IoU metrics difficult to satisfy.

The paper suggests that better long-range performance will require more balanced training data (currently, only 5% of training positives are in the 100–200m range) and perhaps earlier-stage fusion to help the detectors propose candidates they would otherwise miss.

Summary updated

Abstract

Long-range 3D object detection remains difficult for autonomous vehicles because LiDAR returns become sparse and camera evidence weakens with distance, while automotive radar keeps returning measurements far beyond both. We present CLOCs-R, an extension of the CLOCs candidate-level fusion framework that adds radar evidence to camera-LiDAR rescoring. Radar returns are accumulated over several sweeps, compensated for ego-motion, and associated with each pre-NMS 3D candidate through a range-dependent gate. Compact features summarizing support, Doppler speed and spread, range residual, and offset are then appended to every camera-LiDAR pair before a lightweight fusion network rescores the candidates. We first verify that our fusion implementation reproduces CLOCs on KITTI. We then evaluate on the daytime clear-weather subset of the aiMotive dataset, reporting distance-binned metrics out to 200 m with frozen SECOND and Cascade R-CNN detectors. Camera-LiDAR CLOCs improves on SECOND up to 50 m but degrades beyond it. A residual scoring variant, introduced post hoc, corrects SECOND's score instead of replacing it and recovers most of this loss. Radar consistently improves BEV AP at 30-50 m (0.857 to 0.870), but beyond 50 m its gain is small (+0.003 center-distance AP), within seed variation, and CLOCs-R with residual scoring is statistically tied with LiDAR-only SECOND. Our analysis attributes the limited long-range benefit to weak separation of true and false detections by radar features, scarce far-range training positives, poor camera evidence at distance, and missing LiDAR proposals that rescoring cannot recover. We report all as-designed and post hoc results side by side.
BibTeX
@misc{beuck2026clocs,
  author = {Richard Beuck and John Nguyen and Sudip Dhakal},
  title = {{CLOCs-R: Radar-Assisted Camera-LiDAR Fusion for Long-Range Object Detection}},
  year = {2026},
  eprint = {2611.04300},
  archivePrefix = {arXiv},
  url = {https://arxiv.org/abs/2611.04300},
}
Figure