Papers › Scalability in Perception for Autonomous Driving: Waymo Open Dataset

Scalability in Perception for Autonomous Driving: Waymo Open Dataset

10 Dec 2019CVPR 2020 6arXiv:1912.04838archive 2025-07-28

Pei Sun, Henrik Kretzschmar, Xerxes Dotiwalla, Aurelien Chouard, Vijaysai Patnaik, Paul Tsui, James Guo, Yin Zhou, Yuning Chai, Benjamin Caine, Vijay Vasudevan, Wei Han, Jiquan Ngiam, Hang Zhao, Aleksei Timofeev, Scott Ettinger, Maxim Krivokon, Amy Gao, Aditya Joshi, Sheng Zhao, Shuyang Cheng, Yu Zhang, Jonathon Shlens, Zhifeng Chen, Dragomir Anguelov

The research community has increasing interest in autonomous driving research, despite the resource intensity of obtaining representative real world data. Existing self-driving datasets are limited in the scale and variation of the environments they capture, even though generalization within and between operating regions is crucial to the overall viability of the technology. In an effort to help align the research community's contributions with real-world self-driving problems, we introduce a new large scale, high quality, diverse dataset. Our new dataset consists of 1150 scenes that each span 20 seconds, consisting of well synchronized and calibrated high quality LiDAR and camera data captured across a range of urban and suburban geographies. It is 15x more diverse than the largest camera+LiDAR dataset available based on our proposed diversity metric. We exhaustively annotated this data with 2D (camera image) and 3D (LiDAR) bounding boxes, with consistent identifiers across frames. Finally, we provide strong baselines for 2D as well as 3D detection and tracking tasks. We further study the effects of dataset size and generalization across geographies on 3D detection methods. Find data, code and more up-to-date information at http://www.waymo.com/open.

PaperPDFConference PDFCodeCode 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 10 code samples harvested from 2 repositories linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 1 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): 10 samples from 2 repositories, 9 ran (9 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

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

JdeRobot/BehaviorSuite mentioned on GitHubtfGPL-3.0Syntology: not harvested report
JdeRobot/NeuralBehaviors mentioned on GitHubtfGPL-3.0Syntology: not harvested report
kav-institute/mdn_trajectory_forecasting mentioned on GitHubpytorchApache-2.0Syntology: 7 samples, 6 ran (0 instrument-failed) · 1 unverified report
p-mc-grath/DMMFODS mentioned on GitHubpytorchMITSyntology: 3 samples, 3 ran (0 instrument-failed) · 0 unverified report
pmcgrath249/DMMFODS mentioned on GitHubpytorchMITSyntology: not harvested report
pmcgrath249/DeepCVLab mentioned on GitHubpytorchMITSyntology: not harvested report
pmcgrath249/DeepCV_Lab mentioned on GitHubpytorchMITSyntology: not harvested report
open-mmlab/mmdetection3d pytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to An Empirical Study of Training State-of-the-Art LiDAR Segmentation Models (arXiv:2405.14870; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
tianweiy/CenterPoint pytorchMITSyntology: not harvested 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

10 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 1 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.

9ran
1unverified

Licence: 0 of the 10 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

kav-institute/mdn_trajectory_forecasting community (archive-listed) 7 samples, 6 ran (0 instrument-failed) · 1 unverified
NLL_MDN_loss base_mdn/base_lstm.py ran Apache-2.0 (permissive) · 3717e065bc9276e7 · report fixture: signature output:Tensor/3/float, target:Tensor/3/float, num_gaussians:int/0/int · returned tuple · level recorded 2026-09-24
bat_mat_vec_mult base_mdn/utils/helper.py ran Apache-2.0 (permissive) · 27ef93ceffbfa03c · report fixture: signature a:ndarray/2/float, M:ndarray/3/float · returned ndarray · level recorded 2026-09-24
build_R base_mdn/utils/helper.py ran Apache-2.0 (permissive) · 077ed2a538596f6d · report fixture: signature rotation_angle:ndarray/2/float · returned ndarray · level recorded 2026-09-24
build_R_inv base_mdn/utils/helper.py ran Apache-2.0 (permissive) · 9826de48ee00a089 · report fixture: signature rotation_angle:ndarray/1/float · returned ndarray · level recorded 2026-09-24
plot_aee_over_time base_mdn/vis.py ran Apache-2.0 (permissive) · 0ae92c0cae8a4b86 · report fixture: signature data:ndarray/2/float, dst_dir:str/0/str, epoch:int/0/int, dt:float/0/float, steps:ndarray/1/int, num_steps:int/0/int · returned float64 · level recorded 2026-09-24
plot_sharpness_over_time base_mdn/vis.py ran Apache-2.0 (permissive) · 2e8c4d6b7823eb92 · report fixture: signature data:ndarray/3/float, dst_dir:str/0/str, epoch:NoneType/0/?, dt:float/0/float, confidence_levels:list/1/float, steps:list/1/int, num_steps:int/0/int · returned list · level recorded 2026-09-24
plot_reliability_calibration base_mdn/vis.py unverified Apache-2.0 (permissive) · 03aadfa8f4527320 · report
p-mc-grath/DMMFODS community (archive-listed) 3 samples, 3 ran (0 instrument-failed) · 0 unverified
load_config in 389 papers dmmfods/utils/Dense_U_Net_lidar_helper.py ran fingerprinted MIT (permissive) · 2abaaa6c376398fe · report fixture: signature loading_dir:str/0/str, file_name:str/0/str · returned dict · level recorded 2026-09-24
load_json_file in 35 papers dmmfods/utils/Dense_U_Net_lidar_helper.py ran MIT (permissive) · 997cebe631653a7b · report fixture: signature filepath:str/0/str · returned dict · level recorded 2026-09-24
save_json_file dmmfods/utils/Dense_U_Net_lidar_helper.py ran MIT (permissive) · 62545dfcd7165317 · report fixture: signature filepath:str/0/str, save_file:dict/0/?, indent:int/0/int · returned int · level recorded 2026-09-24

Tasks

Autonomous DrivingDiversity

Datasets

Introduced by this paper, per the archive.

Waymo Open Dataset

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