Papers › Pillar-based Object Detection for Autonomous Driving

Pillar-based Object Detection for Autonomous Driving

20 Jul 2020ECCV 2020 8arXiv:2007.10323archive 2025-07-28

Yue Wang, Alireza Fathi, Abhijit Kundu, David Ross, Caroline Pantofaru, Thomas Funkhouser, Justin Solomon

We present a simple and flexible object detection framework optimized for autonomous driving. Building on the observation that point clouds in this application are extremely sparse, we propose a practical pillar-based approach to fix the imbalance issue caused by anchors. In particular, our algorithm incorporates a cylindrical projection into multi-view feature learning, predicts bounding box parameters per pillar rather than per point or per anchor, and includes an aligned pillar-to-point projection module to improve the final prediction. Our anchor-free approach avoids hyperparameter search associated with past methods, simplifying 3D object detection while significantly improving upon state-of-the-art.

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 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 10 samples from 1 repository, 10 ran (10 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.

WangYueFt/pillar-od officialmentioned in papertfMITSyntology: 10 samples, 10 ran (0 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

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

10ran

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 WangYueFt/pillar-od. “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.

WangYueFt/pillar-od official repository 10 samples, 10 ran (0 instrument-failed) · 0 unverified
add_points_bboxes waymo_loader.py ran MIT (permissive) · b200fdbce22c84fb · report fixture: signature points_xyz:EagerTensor/2/float, bboxes:EagerTensor/2/float, bboxes_label:EagerTensor/1/int, bboxes_mask:EagerTensor/1/float, is_2d:bool/0/bool · returned tuple · level recorded 2026-09-25
assign_bboxes waymo_loader.py ran MIT (permissive) · 425c4b336ed9b1ca · report fixture: signature pillar_map_size:tuple/1/int, pillar_map_range:tuple/1/float, bboxes:EagerTensor/2/float, bboxes_mask:EagerTensor/1/float, bboxes_label:EagerTensor/1/int · returned tuple · level recorded 2026-09-25
conv1d in 31 papers network.py ran MIT (permissive) · ae08fa5021cce887 · report fixture: signature odims:int/0/int, kernel_size:int/0/int, stride:int/0/int, use_bias:bool/0/bool · returned Conv1D · level recorded 2026-09-25
conv2d in 119 papers network.py ran MIT (permissive) · af683bf5fadd331e · report fixture: signature odims:int/0/int, kernel_size:tuple/1/int, stride:int/0/int, use_bias:bool/0/bool · returned Conv2D · level recorded 2026-09-25
dense in 22 papers network.py ran MIT (permissive) · b1471476d6fe5102 · report fixture: signature odims:int/0/int, use_bias:bool/0/bool · returned Dense · level recorded 2026-09-25
get_shape in 27 papers tf_util.py ran MIT (permissive) · 73717934286fbf5a · report fixture: signature tensor:EagerTensor/2/float, ndims:NoneType/0/? · returned list · level recorded 2026-09-25
pad_or_trim_to tf_util.py ran MIT (permissive) · f42ac0146c825dcc · report fixture: signature x:EagerTensor/2/float, shape:EagerTensor/1/int, pad_val:int/0/int · returned EagerTensor · level recorded 2026-09-25
raval_index tf_util.py ran MIT (permissive) · cf255a3dd2896681 · report fixture: signature coords:EagerTensor/2/int, dims:EagerTensor/1/int · returned EagerTensor · level recorded 2026-09-25
sigmoid_cross_entropy_focal_loss loss.py ran MIT (permissive) · eddf699a8d1e9e30 · report fixture: signature logits:EagerTensor/2/float, labels:EagerTensor/2/float, alpha:float/0/float, gamma:float/0/float · returned EagerTensor · level recorded 2026-09-25
smooth_l1_loss in 28 papers loss.py ran fingerprinted MIT (permissive) · cf26f601b7f98582 · report fixture: signature predictions:EagerTensor/2/float, labels:EagerTensor/2/float, sigma:float/0/float · returned EagerTensor · level recorded 2026-09-25

Tasks

3D Object DetectionAutonomous DrivingObjectObject 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