Papers › Revisiting Point Cloud Shape Classification with a Simple and Effective Baseline

Revisiting Point Cloud Shape Classification with a Simple and Effective Baseline

9 Jun 2021arXiv:2106.05304archive 2025-07-28

Ankit Goyal, Hei Law, Bowei Liu, Alejandro Newell, Jia Deng

Processing point cloud data is an important component of many real-world systems. As such, a wide variety of point-based approaches have been proposed, reporting steady benchmark improvements over time. We study the key ingredients of this progress and uncover two critical results. First, we find that auxiliary factors like different evaluation schemes, data augmentation strategies, and loss functions, which are independent of the model architecture, make a large difference in performance. The differences are large enough that they obscure the effect of architecture. When these factors are controlled for, PointNet++, a relatively older network, performs competitively with recent methods. Second, a very simple projection-based method, which we refer to as SimpleView, performs surprisingly well. It achieves on par or better results than sophisticated state-of-the-art methods on ModelNet40 while being half the size of PointNet++. It also outperforms state-of-the-art methods on ScanObjectNN, a real-world point cloud benchmark, and demonstrates better cross-dataset generalization. Code is available at https://github.com/princeton-vl/SimpleView.

PaperPDFCodeCode Syntology ranMethod as code

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 12 code samples harvested from 2 repositories linked to this paper: 4 ran (of which 3 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 1 where Syntology's instrument failed) · 8 unverified. Where Syntology's instrument failed: 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 1 ran (0 with no instrument failure; 1 where Syntology's instrument failed); community (archive-listed): 3 samples from 1 repository, 3 ran (3 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-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

princeton-vl/SimpleView officialmentioned in papermentioned on GitHubpytorchSyntology: 9 samples, 1 ran (1 instrument-failed) · 8 unverified report
axeber01/point-tnt mentioned on GitHubpytorchSyntology: 3 samples, 3 ran (0 instrument-failed) · 0 unverified report
jiachens/ModelNet40-C mentioned on GitHubpytorchBSD-3-ClauseSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Benchmarking Robustness of 3D Point Cloud Recognition Against Common Corruptions (arXiv:2201.12296; that paper's own run record: 24 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 2 honoured, 0 violated, 10 with no contract checked; 12 where Syntology's instrument failed) · 5 unverified); nothing checks that they implement this paper's method. 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

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

1ran; the contract check could not run
3ran
8unverified

Licence: 0 of the 12 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”. For 3 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

princeton-vl/SimpleView official repository 9 samples, 1 ran (1 instrument-failed) · 8 unverified
fixed_padding in 28 papers ScanObjectNN/SimpleView/multi_model.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted BSD-3-Clause (permissive) · ca82893aff5e0d2e · report fixture: signature inputs:EagerTensor/4/float, kernel_size:int/0/int, data_format:str/0/str · returned EagerTensor · level recorded 2026-09-22
Model in 227 papers ScanObjectNN/SimpleView/multi_model.py unverified BSD-3-Clause (permissive) · 0aada2a0a966a06e · report
_bottleneck_block_v1 ScanObjectNN/SimpleView/multi_model.py unverified BSD-3-Clause (permissive) · b941b66d21901b83 · report
_bottleneck_block_v2 ScanObjectNN/SimpleView/multi_model.py unverified BSD-3-Clause (permissive) · bd2e7dfc294b27b6 · report
_building_block_v1 ScanObjectNN/SimpleView/multi_model.py unverified BSD-3-Clause (permissive) · 11702804c488ed55 · report
_building_block_v2 ScanObjectNN/SimpleView/multi_model.py unverified BSD-3-Clause (permissive) · d4516530837fed03 · report
batch_norm in 46 papers ScanObjectNN/SimpleView/multi_model.py unverified BSD-3-Clause (permissive) · 6cccb6ae78594ebb · report
block_layer ScanObjectNN/SimpleView/multi_model.py unverified BSD-3-Clause (permissive) · 5425aca7fe65bb0d · report
conv2d_fixed_padding in 12 papers ScanObjectNN/SimpleView/multi_model.py unverified BSD-3-Clause (permissive) · a5cb548e4b581359 · report
axeber01/point-tnt community (archive-listed) 3 samples, 3 ran (0 instrument-failed) · 0 unverified
Attention in 344 papers
census: 13 implementations from 12 papers, 10 distinct outputs across 4 buckets, one shared input per bucket
model.py ran · metamorphic tier: deterministic MIT (permissive) · 15cfb9f4479acd04 · report fixture: returned Attention · level recorded 2026-09-22
Baseline in 6 papers model.py ran · metamorphic tier: deterministic fingerprinted MIT (permissive) · fe12c37bc8cebc08 · report fixture: returned Baseline · level recorded 2026-09-22
FeedForward in 198 papers model.py ran · metamorphic tier: deterministic MIT (permissive) · bea49fdbe8f8578a · report fixture: returned FeedForward · level recorded 2026-09-22

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for SimpleView (graph method: SimpleView). 9 bricks; individually on a fixture: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 8 unverified. The assembly has not been run end-to-end.

  1. Model entry · level 0 · unverified · 0aada2a0a966a06e
  2. _bottleneck_block_v1 model · level 0 · unverified · b941b66d21901b83
  3. _bottleneck_block_v2 model · level 0 · unverified · bd2e7dfc294b27b6
  4. _building_block_v1 model · level 0 · unverified · 11702804c488ed55
  5. _building_block_v2 model · level 0 · unverified · d4516530837fed03
  6. batch_norm helper · level 0 · unverified · 6cccb6ae78594ebb
  7. block_layer model · level 0 · unverified · 5425aca7fe65bb0d
  8. conv2d_fixed_padding helper · level 0 · unverified · a5cb548e4b581359
  9. fixed_padding helper · level 1 · ran; the contract check could not run (RAISES) · ca82893aff5e0d2e

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2106.05304") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

3D Point Cloud ClassificationPoint Cloud Classification

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Point Cloud Classification ModelNet40 SimpleView-DGCNN Overall Accuracy 93.9 #37 of 111 Archive leaderboard report
Point Cloud Classification PointCloud-C SimpleView mean Corruption Error (mCE) 1.047 #19 of 24 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