Papers › Dual Radar: A Multi-modal Dataset with Dual 4D Radar for Autonomous Driving

Dual Radar: A Multi-modal Dataset with Dual 4D Radar for Autonomous Driving

11 Oct 2023arXiv:2310.07602archive 2025-07-28

Xinyu Zhang, Li Wang, Jian Chen, Cheng Fang, Lei Yang, Ziying Song, Guangqi Yang, Yichen Wang, Xiaofei Zhang, Jun Li, Zhiwei Li, Qingshan Yang, Zhenlin Zhang, Shuzhi Sam Ge

Radar has stronger adaptability in adverse scenarios for autonomous driving environmental perception compared to widely adopted cameras and LiDARs. Compared with commonly used 3D radars, the latest 4D radars have precise vertical resolution and higher point cloud density, making it a highly promising sensor for autonomous driving in complex environmental perception. However, due to the much higher noise than LiDAR, manufacturers choose different filtering strategies, resulting in an inverse ratio between noise level and point cloud density. There is still a lack of comparative analysis on which method is beneficial for deep learning-based perception algorithms in autonomous driving. One of the main reasons is that current datasets only adopt one type of 4D radar, making it difficult to compare different 4D radars in the same scene. Therefore, in this paper, we introduce a novel large-scale multi-modal dataset featuring, for the first time, two types of 4D radars captured simultaneously. This dataset enables further research into effective 4D radar perception algorithms.Our dataset consists of 151 consecutive series, most of which last 20 seconds and contain 10,007 meticulously synchronized and annotated frames. Moreover, our dataset captures a variety of challenging driving scenarios, including many road conditions, weather conditions, nighttime and daytime with different lighting intensities and periods. Our dataset annotates consecutive frames, which can be applied to 3D object detection and tracking, and also supports the study of multi-modal tasks. We experimentally validate our dataset, providing valuable results for studying different types of 4D radars. This dataset is released on https://github.com/adept-thu/Dual-Radar.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 14 code samples harvested from 1 repository linked to this paper: 14 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 1 honoured, 0 violated, 11 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 14 samples from 1 repository, 14 ran (12 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

adept-thu/dual-radar officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 14 samples, 14 ran (2 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

14 samples harvested: 14 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 1 honoured, 0 violated, 11 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
2ran · our draft was wrong
11ran

Licence: 1 of the 14 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from adept-thu/dual-radar. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

adept-thu/dual-radar official repository 14 samples, 14 ran (2 instrument-failed) · 0 unverified
calib_to_matricies pcdet/datasets/dual_radar/dual_radar_utils.py ran Apache-2.0 (permissive) · 12f2abeb508c73e6 · report fixture: signature calib:Calibration/0/? · returned tuple · level recorded 2026-09-24
cfg_from_yaml_file in 59 papers pcdet/config.py ran · our draft was wrong Apache-2.0 (permissive) · 44db2351bcc0bffe · report fixture: signature cfg_file:str/0/str, config:dict/0/? · returned EasyDict · level recorded 2026-09-25
clean_data in 13 papers pcdet/datasets/dual_radar/kitti_object_eval_python/eval1.py ran Apache-2.0 (permissive) · 7a89af4cf8defd62 · report fixture: signature gt_anno:dict/0/?, dt_anno:dict/0/?, current_class:int/0/int, difficulty:int/0/int · returned tuple · level recorded 2026-09-24
cls_type_to_id in 7 papers pcdet/utils/object3d_dual_radar.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 68d59bd1b88d6e20 · report fixture: signature cls_type:str/0/str · returned int · level recorded 2026-09-24
div_up in 10 papers pcdet/datasets/dual_radar/kitti_object_eval_python/rotate_iou.py ran fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 20fbfa2279e1ce4b · report fixture: signature m:int/0/int, n:int/0/int · returned int · level recorded 2026-09-24
get_calib_from_file in 7 papers pcdet/utils/calibration_dual_radar.py ran Apache-2.0 (permissive) · 35de1acbb1176d93 · report fixture: signature calib_file:str/0/str · returned dict · level recorded 2026-09-24
get_image_index_str in 7 papers pcdet/datasets/dual_radar/kitti_object_eval_python/kitti_common.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 3415a0d1c950c1c7 · report fixture: signature img_idx:int/0/int · returned str · level recorded 2026-09-24
get_image_path in 15 papers pcdet/datasets/dual_radar/kitti_object_eval_python/kitti_common.py ran Apache-2.0 (permissive) · 8714a17f7bf0c1af · report fixture: signature idx:int/0/int, prefix:str/0/str, training:bool/0/bool, relative_path:bool/0/bool · returned str · level recorded 2026-09-24
get_kitti_info_path in 7 papers pcdet/datasets/dual_radar/kitti_object_eval_python/kitti_common.py ran Apache-2.0 (permissive) · 9ba61b01f573b5e4 · report fixture: signature idx:int/0/int, prefix:str/0/str, info_type:str/0/str, file_tail:str/0/str, training:bool/0/bool, relative_path:bool/0/bool · returned str · level recorded 2026-09-24
get_objects_from_label pcdet/utils/object3d_dual_radar.py ran Apache-2.0 (permissive) · 745fc20e6b5a2f30 · report fixture: signature label_file:str/0/str · returned list · level recorded 2026-09-24
get_thresholds in 7 papers pcdet/datasets/dual_radar/kitti_object_eval_python/eval1.py ran Apache-2.0 (permissive) · ea171bd4f1407f14 · report fixture: signature scores:ndarray/1/float, num_gt:int/0/int, num_sample_pts:int/0/int · returned list · level recorded 2026-09-24
image_box_overlap pcdet/datasets/dual_radar/kitti_object_eval_python/eval1.py ran fingerprinted Apache-2.0 (permissive) · 45f3e1c5466de4e5 · report fixture: signature boxes:ndarray/2/float, query_boxes:ndarray/2/float, criterion:int/0/int · returned ndarray · level recorded 2026-09-24
merge_new_config in 59 papers pcdet/config.py ran Apache-2.0 (permissive) · 50e8e8cdfc5129f0 · report fixture: signature config:dict/0/?, new_config:dict/0/? · returned EasyDict · level recorded 2026-09-25
transform_annotations_to_kitti_format pcdet/datasets/dual_radar/dual_radar_utils.py ran Apache-2.0 (permissive) · 43e0ea59c03fa906 · report fixture: signature annos:list/1/dict, map_name_to_kitti:dict/0/?, info_with_fakelidar:bool/0/bool · returned list · level recorded 2026-09-24

Tasks

3D Object DetectionAutonomous DrivingObject Detectionobject-detection

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections