Papers › SNAKE: Shape-aware Neural 3D Keypoint Field

SNAKE: Shape-aware Neural 3D Keypoint Field

3 Jun 2022arXiv:2206.01724archive 2025-07-28

Chengliang Zhong, Peixing You, Xiaoxue Chen, Hao Zhao, Fuchun Sun, Guyue Zhou, Xiaodong Mu, Chuang Gan, Wenbing Huang

Detecting 3D keypoints from point clouds is important for shape reconstruction, while this work investigates the dual question: can shape reconstruction benefit 3D keypoint detection? Existing methods either seek salient features according to statistics of different orders or learn to predict keypoints that are invariant to transformation. Nevertheless, the idea of incorporating shape reconstruction into 3D keypoint detection is under-explored. We argue that this is restricted by former problem formulations. To this end, a novel unsupervised paradigm named SNAKE is proposed, which is short for shape-aware neural 3D keypoint field. Similar to recent coordinate-based radiance or distance field, our network takes 3D coordinates as inputs and predicts implicit shape indicators and keypoint saliency simultaneously, thus naturally entangling 3D keypoint detection and shape reconstruction. We achieve superior performance on various public benchmarks, including standalone object datasets ModelNet40, KeypointNet, SMPL meshes and scene-level datasets 3DMatch and Redwood. Intrinsic shape awareness brings several advantages as follows. (1) SNAKE generates 3D keypoints consistent with human semantic annotation, even without such supervision. (2) SNAKE outperforms counterparts in terms of repeatability, especially when the input point clouds are down-sampled. (3) the generated keypoints allow accurate geometric registration, notably in a zero-shot setting. Codes are available at https://github.com/zhongcl-thu/SNAKE

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

Syntology 14 code samples harvested from 1 repository linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 0 violated, 8 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 14 samples from 1 repository, 11 ran (9 with no instrument failure; 2 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

zhongcl-thu/snake officialmentioned in papermentioned on GitHubpytorchMITSyntology: 14 samples, 11 ran (2 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

14 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 0 violated, 8 with no contract checked; 2 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 last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
1ran · our draft was wrong
1ran; the contract check could not run
8ran
3unverified

Licence: 1 of the 14 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 zhongcl-thu/snake. “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.

zhongcl-thu/snake official repository 14 samples, 11 ran (2 instrument-failed) · 3 unverified
accuracy in 872 papers
census: 8 implementations from 7 papers, 7 distinct outputs across 6 buckets, one shared input per bucket
core/utils/common.py ran MIT (permissive) · 9a8db8d09e7923d3 · report fixture: signature output:Tensor/2/float, target:Tensor/1/int, topk:tuple/1/int, v_n:int/0/int · returned list · level recorded 2026-09-24
angles2rotation_matrix core/datasets/augmentation.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) here; the stored copy is pointer only · 60f2f4207ae20ab9 · report fixture: signature angles:ndarray/1/float · returned ndarray · level recorded 2026-09-24
atomic_rotate_pytorch_batch core/datasets/augmentation.py ran MIT (permissive) · 61969ba9c876c10d · report fixture: signature data:Tensor/3/float, angles:list/1/float · returned Tensor · level recorded 2026-09-24
augment in 36 papers core/datasets/augmentation.py ran MIT (permissive) · 60c37454e2a095ce · report fixture: signature pcd_data:ndarray/2/float, grid_coords:ndarray/2/float, config:dict/0/? · returned tuple · level recorded 2026-09-24
chamfer_distance_naive in 7 papers core/nets/common.py ran · our draft was wrong fingerprinted MIT (permissive) · 8e6b5059f61d84e6 · report fixture: signature points1:Tensor/3/float, points2:Tensor/3/float · returned Tensor · level recorded 2026-09-24
compute_iou in 68 papers core/nets/common.py ran · honoured contract MIT (permissive) · 0072de07b144b152 · report fixture: signature occ1:Tensor/2/float, occ2:Tensor/2/float · returned ndarray · level recorded 2026-09-24
get_ray_directions_cam core/nets/geometry.py ran fingerprinted MIT (permissive) · dcf31906f80d979c · report fixture: signature uv:Tensor/3/float, intrinsics:Tensor/3/float · returned Tensor · level recorded 2026-09-24
load_last_iter core/utils/common.py ran MIT (permissive) · 97c47b2462e29db3 · report fixture: signature path:str/0/str · returned int · level recorded 2026-09-24
make_3d_grid core/datasets/train_dataset.py ran MIT (permissive) · 9babaac7293b5582 · report fixture: signature x_res:tuple/1/float, y_res:tuple/1/float, z_res:tuple/1/float, type:str/0/str · returned ndarray · level recorded 2026-09-24
reflect_vector_on_vector core/nets/geometry.py ran fingerprinted MIT (permissive) · 54dc24b743feff79 · report fixture: signature vector_to_reflect:Tensor/2/float, reflection_axis:Tensor/2/float · returned Tensor · level recorded 2026-09-24
sample_vertex_from_mesh core/datasets/smpl_model.py ran MIT (permissive) · 0bd31bdc88752b70 · report fixture: signature vertex:ndarray/2/float, facet:ndarray/2/int, colors:ndarray/2/float, rnd_idxs:NoneType/0/?, u:NoneType/0/?, v:NoneType/0/?, num_samples:int/0/int · returned tuple · level recorded 2026-09-24
chamfer_distance in 17 papers core/nets/common.py unverified MIT (permissive) · f4d8f4c4d0f7da71 · report
load_state in 19 papers core/utils/common.py unverified MIT (permissive) · 3777dfeb89e049b9 · report
naive_read_pcd core/datasets/train_dataset.py unverified MIT (permissive) · c994f6f4b55acda6 · report

Tasks

Keypoint 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