Papers › aiMotive Dataset: A Multimodal Dataset for Robust Autonomous Driving with Long-Range Perception

aiMotive Dataset: A Multimodal Dataset for Robust Autonomous Driving with Long-Range Perception

17 Nov 2022arXiv:2211.09445archive 2025-07-28

Tamás Matuszka, Iván Barton, Ádám Butykai, Péter Hajas, Dávid Kiss, Domonkos Kovács, Sándor Kunsági-Máté, Péter Lengyel, Gábor Németh, Levente Pető, Dezső Ribli, Dávid Szeghy, Szabolcs Vajna, Bálint Varga

Autonomous driving is a popular research area within the computer vision research community. Since autonomous vehicles are highly safety-critical, ensuring robustness is essential for real-world deployment. While several public multimodal datasets are accessible, they mainly comprise two sensor modalities (camera, LiDAR) which are not well suited for adverse weather. In addition, they lack far-range annotations, making it harder to train neural networks that are the base of a highway assistant function of an autonomous vehicle. Therefore, we introduce a multimodal dataset for robust autonomous driving with long-range perception. The dataset consists of 176 scenes with synchronized and calibrated LiDAR, camera, and radar sensors covering a 360-degree field of view. The collected data was captured in highway, urban, and suburban areas during daytime, night, and rain and is annotated with 3D bounding boxes with consistent identifiers across frames. Furthermore, we trained unimodal and multimodal baseline models for 3D object detection. Data are available at https://github.com/aimotive/aimotive_dataset.

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

The archive's official repositories (aimotive/aimotive-dataset-loader, aimotive/aimotive_dataset) were not harvested; the 5 samples below come from 1 community repository.

Syntology 5 code samples harvested from 1 repository linked to this paper: 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 5 samples from 1 repository, 2 ran (2 with no instrument failure; 0 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 on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

aimotive/aimotive-dataset-loader officialmentioned in papermentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
aimotive/aimotive_dataset officialmentioned in papermentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
aimotive/mm_training mentioned on GitHubpytorchMITSyntology: 5 samples, 2 ran (0 instrument-failed) · 3 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

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

2ran
3unverified

Licence: 0 of the 5 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from aimotive/mm_training. “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.

aimotive/mm_training community (archive-listed) 5 samples, 2 ran (0 instrument-failed) · 3 unverified
get_rot in 8 papers dataset/nusc_mv_det_dataset.py ran MIT (permissive) · 2dd096050170984b · report fixture: signature h:float/0/float · returned Tensor · level recorded 2026-09-25
img_transform in 10 papers dataset/nusc_mv_det_dataset.py ran MIT (permissive) · 42061d7d8a0c3f80 · report fixture: signature img:Image/0/?, resize:float/0/float, resize_dims:tuple/1/int, crop:tuple/1/int, flip:bool/0/bool, rotate:float/0/float · returned tuple · level recorded 2026-09-25
bev_transform in 5 papers dataset/nusc_mv_det_dataset.py unverified MIT (permissive) · 75bd9e91eab5963b · report
create_trainer exps/mm_training_aim.py unverified MIT (permissive) · 8b1dc97beb358b74 · report
is_parallel in 15 papers callbacks/ema.py unverified MIT (permissive) · bbbb5d6a28074b9d · report

Tasks

3D Object DetectionAutonomous DrivingAutonomous VehiclesMultimodal Deep LearningObject Detectionobject-detection

Datasets

Introduced by this paper, per the archive.

aiMotive Dataset

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Object Detection aiMotive Dataset Lidar-Radar-Camera BEV AP@0.3 Highway 0.762 #1 of 3 Archive leaderboard report
3D Object Detection aiMotive Dataset Lidar-Radar-Camera BEV AP@0.3 Night 0.730 #1 of 3 Archive leaderboard report
3D Object Detection aiMotive Dataset Lidar-Radar-Camera BEV AP@0.3 Rain 0.423 #1 of 3 Archive leaderboard report
3D Object Detection aiMotive Dataset Lidar-Radar-Camera BEV AP@0.3 Urban 0.644 #1 of 3 Archive leaderboard report
3D Object Detection aiMotive Dataset Lidar BEV AP@0.3 Highway 0.757 #2 of 3 Archive leaderboard report
3D Object Detection aiMotive Dataset Lidar BEV AP@0.3 Night 0.754 #2 of 3 Archive leaderboard report
3D Object Detection aiMotive Dataset Lidar BEV AP@0.3 Rain 0.568 #2 of 3 Archive leaderboard report
3D Object Detection aiMotive Dataset Lidar BEV AP@0.3 Urban 0.630 #2 of 3 Archive leaderboard report
3D Object Detection aiMotive Dataset Lidar-Radar BEV AP@0.3 Highway 0.741 #3 of 3 Archive leaderboard report
3D Object Detection aiMotive Dataset Lidar-Radar BEV AP@0.3 Night 0.766 #3 of 3 Archive leaderboard report
3D Object Detection aiMotive Dataset Lidar-Radar BEV AP@0.3 Rain 0.517 #3 of 3 Archive leaderboard report
3D Object Detection aiMotive Dataset Lidar-Radar BEV AP@0.3 Urban 0.638 #3 of 3 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

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