Papers › TetraSphere: A Neural Descriptor for O(3)-Invariant Point Cloud Analysis

TetraSphere: A Neural Descriptor for O(3)-Invariant Point Cloud Analysis

26 Nov 2022CVPR 2024 1arXiv:2211.14456archive 2025-07-28

Pavlo Melnyk, Andreas Robinson, Michael Felsberg, Mårten Wadenbäck

In many practical applications, 3D point cloud analysis requires rotation invariance. In this paper, we present a learnable descriptor invariant under 3D rotations and reflections, i.e., the O(3) actions, utilizing the recently introduced steerable 3D spherical neurons and vector neurons. Specifically, we propose an embedding of the 3D spherical neurons into 4D vector neurons, which leverages end-to-end training of the model. In our approach, we perform TetraTransform--an equivariant embedding of the 3D input into 4D, constructed from the steerable neurons--and extract deeper O(3)-equivariant features using vector neurons. This integration of the TetraTransform into the VN-DGCNN framework, termed TetraSphere, negligibly increases the number of parameters by less than 0.0002%. TetraSphere sets a new state-of-the-art performance classifying randomly rotated real-world object scans of the challenging subsets of ScanObjectNN. Additionally, TetraSphere outperforms all equivariant methods on randomly rotated synthetic data: classifying objects from ModelNet40 and segmenting parts of the ShapeNet shapes. Thus, our results reveal the practical value of steerable 3D spherical neurons for learning in 3D Euclidean space. The code is available at https://github.com/pavlo-melnyk/tetrasphere.

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: 9 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 3 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 10 samples from 1 repository, 9 ran (6 with no instrument failure; 3 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-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

pavlo-melnyk/tetrasphere officialmentioned in papermentioned on GitHubpytorchMITSyntology: 10 samples, 9 ran (3 instrument-failed) · 1 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: 9 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 3 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.

1ran · our draft was wrong
2ran; the contract check could not run
6ran
1unverified

Licence: 1 of the 10 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 pavlo-melnyk/tetrasphere. “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. 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.

pavlo-melnyk/tetrasphere official repository 10 samples, 9 ran (3 instrument-failed) · 1 unverified
build_datasets tetrasphere/runner.py ran MIT (permissive) · 6550b40e98377f7d · report fixture: signature train_dset:dict/0/?, train_xform:dict/0/?, val_dset:dict/0/?, val_xform:dict/0/?, test_dset:dict/0/?, test_xform:dict/0/?, batch_size:int/0/int, num_workers:int/0/int · returned LightningDataModule · level recorded 2026-09-25
cal_loss in 20 papers tetrasphere/utils.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant MIT (permissive) · c6c2758c0c2fa756 · report fixture: signature pred:Tensor/2/float, gold:Tensor/1/int, smoothing:bool/0/bool · returned Tensor · level recorded 2026-09-22
calculate_shape_IoU in 5 papers tetrasphere/utils.py ran MIT (permissive) · ed28493d8df0a024 · report fixture: signature pred_np:ndarray/2/int, seg_np:ndarray/2/int, label:ndarray/2/int, class_choice:bool/0/bool · returned list · level recorded 2026-09-25
embed in 13 papers tetrasphere/models/spheres.py ran fingerprinted MIT (permissive) · e4b543f085e11201 · report fixture: signature x:Tensor/4/float · returned Tensor · level recorded 2026-09-25
embed_spheres tetrasphere/models/spheres.py ran MIT (permissive) · c8619d0a79c0c42d · report fixture: signature centers:Tensor/2/float, radii:Tensor/1/float, gamma:Tensor/1/float · returned Tensor · level recorded 2026-09-25
get_graph_feature in 51 papers
census: 6 implementations from 5 papers, 4 distinct outputs across 2 buckets, one shared input per bucket
tetrasphere/models/utils.py ran MIT (permissive) · e146f86f54b1a708 · report fixture: signature x:Tensor/4/float, k:int/0/int, idx:NoneType/0/?, x_coord:NoneType/0/? · returned Tensor · level recorded 2026-09-25
knn in 87 papers
census: 12 implementations from 17 papers, 6 distinct outputs across 4 buckets, one shared input per bucket this sample: bucket 1 of 4, arg 1: rank 3, kind float, dtype float32
tetrasphere/models/utils.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · cdd0141594039dcb · report fixture: signature x:Tensor/3/float, k:int/0/int · returned Tensor · level recorded 2026-09-22
mean_pool in 13 papers tetrasphere/models/vnn.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 19b639ea820e6dbc · report fixture: signature x:Tensor/3/float, dim:int/0/int, keepdim:bool/0/bool · returned Tensor · level recorded 2026-09-22
nd_get_graph_feature tetrasphere/models/utils.py ran MIT (permissive) · 111defecda8c385d · report fixture: signature x:Tensor/4/float, k:int/0/int, idx:NoneType/0/?, x_coord:NoneType/0/? · returned Tensor · level recorded 2026-09-25
append_ones tetrasphere/models/spheres.py unverified MIT (permissive) · 3a71074992fa1e26 · report

Tasks

3D Point Cloud ClassificationPoint Cloud Classification

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

DGCNN

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