9 of 9 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 5 have no contract verdict; 4 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/0905.2635.json · badge: /api/ran/0905.2635.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| siavashk/pycpd | community (classifier label) classifier basis not recorded on the link |
5 ran · 0 no recorded run |
| bing-jian/gmmreg | reimplementation (classifier label) classifier basis: classifier_2025 |
4 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| gaussian_kernel | Ran ran on a synthesized input |
siavashk/pycpd/pycpd/utility.py code served (permissive licence) · get_code("4f1931c292e385c7") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned ndarray, ndim 2, dtype family float, shape (2, 3) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| get_all_depth_files | Ran ran; our contract draft was wrong, not the code |
bing-jian/gmmreg/expts/lounge_expts.py pointer only (licence: GPL-3.0) · get_code("c6200a94efe2504f") How it ranThe body of this sample is withheld: GPL-3.0, as GitHub detects it on this paper's repository, bing-jian/gmmreg, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| initialize_sigma2 | Ran ran on a synthesized input |
siavashk/pycpd/pycpd/emregistration.py code served (permissive licence) · get_code("0daf328762616aa0") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned float64, ndim 0, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| is_positive_semi_definite | Ran ran on a synthesized input |
siavashk/pycpd/pycpd/utility.py code served (permissive licence) · get_code("450b52b2868095cc") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned bool, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| load_dragon_conf | Ran ran; our contract draft was wrong, not the code |
bing-jian/gmmreg/expts/dragon_expts.py pointer only (licence: GPL-3.0) · get_code("fbb317e15933ad51") How it ranThe body of this sample is withheld: GPL-3.0, as GitHub detects it on this paper's repository, bing-jian/gmmreg, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| lookup_ground_truth | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
bing-jian/gmmreg/expts/dragon_expts.py pointer only (licence: GPL-3.0) · get_code("3cfb735736ac67dc") How it ranThe body of this sample is withheld: GPL-3.0, as GitHub detects it on this paper's repository, bing-jian/gmmreg, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| low_rank_eigen | Ran ran on a synthesized input |
siavashk/pycpd/pycpd/utility.py code served (permissive licence) · get_code("178f55aff7e2a1f5") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| lowrankQS | Ran ran on a synthesized input |
siavashk/pycpd/pycpd/emregistration.py code served (permissive licence) · get_code("6fd86a3e72cbbb60") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| parse_ground_truth | Ran ran; our contract draft was wrong, not the code |
bing-jian/gmmreg/expts/lounge_expts.py pointer only (licence: GPL-3.0) · get_code("b681159f7c462b42") How it ranThe body of this sample is withheld: GPL-3.0, as GitHub detects it on this paper's repository, bing-jian/gmmreg, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
Of 9 samples lifted from this paper's linked repositories, 9 carry a function identity and 0 do not. Of the 9 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 9 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
Point set registration is a key component in many computer vision tasks. The goal of point set registration is to assign correspondences between two sets of points and to recover the transformation that maps one point set to the other. Multiple factors, including an unknown non-rigid spatial transformation, large dimensionality of point set, noise and outliers, make the point set registration a challenging problem. We introduce a probabilistic method, called the Coherent Point Drift (CPD) algorithm, for both rigid and non-rigid point set registration. We consider the alignment of two point sets as a probability density estimation problem. We fit the GMM centroids (representing the first point set) to the data (the second point set) by maximizing the likelihood. We force the GMM centroids to move coherently as a group to preserve the topological structure of the point sets. In the rigid case, we impose the coherence constraint by re-parametrization of GMM centroid locations with rigid parameters and derive a closed form solution of the maximization step of the EM algorithm in arbitrary dimensions. In the non-rigid case, we impose the coherence constraint by regularizing the displacement field and using the variational calculus to derive the optimal transformation. We also introduce a fast algorithm that reduces the method computation complexity to linear. We test the CPD algorithm for both rigid and non-rigid transformations in the presence of noise, outliers and missing points, where CPD shows accurate results and outperforms current state-of-the-art methods.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("0905.2635")
get_code_for_paper("0905.2635")
have("0905.2635")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/0905.2635.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/0905.2635)
Connect an agent — have() is free.