Papers › REGTR: End-to-end Point Cloud Correspondences with Transformers

REGTR: End-to-end Point Cloud Correspondences with Transformers

28 Mar 2022CVPR 2022 1arXiv:2203.14517archive 2025-07-28

Zi Jian Yew, Gim Hee Lee

Despite recent success in incorporating learning into point cloud registration, many works focus on learning feature descriptors and continue to rely on nearest-neighbor feature matching and outlier filtering through RANSAC to obtain the final set of correspondences for pose estimation. In this work, we conjecture that attention mechanisms can replace the role of explicit feature matching and RANSAC, and thus propose an end-to-end framework to directly predict the final set of correspondences. We use a network architecture consisting primarily of transformer layers containing self and cross attentions, and train it to predict the probability each point lies in the overlapping region and its corresponding position in the other point cloud. The required rigid transformation can then be estimated directly from the predicted correspondences without further post-processing. Despite its simplicity, our approach achieves state-of-the-art performance on 3DMatch and ModelNet benchmarks. Our source code can be found at https://github.com/yewzijian/RegTR .

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 16 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) · 6 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 16 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 between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

yewzijian/regtr officialmentioned in paperpytorchMITSyntology: 16 samples, 10 ran (0 instrument-failed) · 6 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

16 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) · 6 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
6unverified

Licence: 0 of the 16 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 yewzijian/regtr. “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.

yewzijian/regtr official repository 16 samples, 10 ran (0 instrument-failed) · 6 unverified
all_isfinite src/cvhelpers/torch_helpers.py ran fingerprinted MIT (permissive) · b16bf332b47d6d18 · report fixture: signature x:Tensor/2/float · returned bool · level recorded 2026-09-24
collate_pair src/data_loaders/collate_functions.py ran MIT (permissive) · 6c01815b97cb00fc · report fixture: signature list_data:list/1/dict · returned dict · level recorded 2026-09-24
compute_rte src/benchmark/benchmark_3dmatch.py ran fingerprinted MIT (permissive) · e5d44638e7b011b6 · report fixture: signature t:ndarray/1/float, t_est:ndarray/1/float · returned float64 · level recorded 2026-09-24
dcm2euler src/benchmark/benchmark_modelnet.py ran MIT (permissive) · 5b694f7ba87b048f · report fixture: signature mats:ndarray/3/float, seq:str/0/str, degrees:bool/0/bool · returned ndarray · level recorded 2026-09-24
pretty_time_delta src/cvhelpers/misc.py ran fingerprinted MIT (permissive) · 519457a60a677d35 · report fixture: signature seconds:int/0/int · returned str · level recorded 2026-09-24
rotation_error in 5 papers src/benchmark/benchmark_predator.py ran fingerprinted MIT (permissive) · 3344db52a0beedde · report fixture: signature R1:Tensor/3/float, R2:Tensor/3/float · returned Tensor · level recorded 2026-09-24
summarize_metrics src/benchmark/benchmark_modelnet.py ran MIT (permissive) · 14b119a1f275889c · report fixture: signature metrics:dict/0/? · returned dict · level recorded 2026-09-24
to_numpy in 103 papers
census: 24 implementations from 29 papers, 2 distinct outputs across 2 buckets, one shared input per bucket
src/cvhelpers/torch_helpers.py ran MIT (permissive) · 2fa7b4714e1f9d24 · report fixture: signature tensor:Tensor/2/float · returned ndarray · level recorded 2026-09-24
translation_error src/benchmark/benchmark_predator.py ran fingerprinted MIT (permissive) · 81b265a618542b54 · report fixture: signature t1:Tensor/3/float, t2:Tensor/3/float · returned Tensor · level recorded 2026-09-24
uniform_2_sphere src/data_loaders/modelnet_transforms.py ran fingerprinted MIT (permissive) · a020832e85dfd32f · report fixture: signature num:int/0/int · returned ndarray · level recorded 2026-09-25
all_to_device src/cvhelpers/torch_helpers.py unverified MIT (permissive) · e7aaf57404c17d96 · report
get_test_datasets src/data_loaders/modelnet.py unverified MIT (permissive) · 43be91adb1cc94fa · report
get_train_datasets src/data_loaders/modelnet.py unverified MIT (permissive) · a149b629c86cfa52 · report
get_transforms in 40 papers src/data_loaders/modelnet.py unverified MIT (permissive) · e659b44bcc28934a · report
read_trajectory in 5 papers src/benchmark/benchmark_3dmatch.py unverified MIT (permissive) · 48f96ab357b5c0e0 · report
read_trajectory_info src/benchmark/benchmark_3dmatch.py unverified MIT (permissive) · 59dff5c1fef3d449 · report

Tasks

Point Cloud RegistrationPose Estimation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Point Cloud Registration 3DLoMatch (10-30% overlap) REGTR Recall ( correspondence RMSE below 0.2) 64.8 #4 of 13 Archive leaderboard report
Point Cloud Registration 3DMatch (at least 30% overlapped - sample 5k interest points) REGTR Recall ( correspondence RMSE below 0.2) 92 #2 of 11 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