Home › Code › rigid_transform

rigid_transform

Syntologyentry name in harvested code

Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record.

rigid_transform appears in the code Syntology harvested for 13 papers, as 7 distinct code bodies found in 13 places (a place is one code body under one paper). Of the 13 papers, 12 with a sample that ran: 9 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument. 0 of the code bodies carry a behaviour fingerprint.

What this page is not. Routines are grouped here by the exact string of their function or class name. Nothing asserts that two samples named rigid_transform do the same thing, share code, or are comparable; the name is a string, not an identity. Behaviour outputs (what a fingerprinted sample returned on the shared battery) are not in this export and are not shown here; get_code(code_sha256="…") returns this sample's fingerprint on the shared battery, with the battery's shuffled null and lift; not shown on this site (how to connect). "Ran" means executed on a synthesized fixture, not that the code is correct or reproduces a paper.

Samples Syntology

The 7 distinct code bodies named rigid_transform: 6 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. One tile per status, in the site's fixed vocabulary, each code body counted once:

0ran · honoured contract
0ran · violated contract
0ran · our draft was wrong
1ran; the contract check could not run
5ran
1unverified
0fingerprinted

Licence is a property of each copy, so it is counted per place: 4 of the 13 places are pointer only (Syntology does not serve that copy's text); at 2 of those this paper's copy is under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text (hover the licence cell for why). This site shows no code text for any sample; every row below links to the file in its repository where the record names one.

“Ran” means the sample executed on a synthesized input; it does not mean the output is correct. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “the contract check could not run” (RAISES, DEP_MISSING or TIMEOUT; hover a row's label for which) are failures of Syntology's instrument, not of the code, and those samples did run. The ran count above is every status except unverified, the same rule as each paper page; “with no instrument failure” is honoured, violated and ran with no contract checked. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Papers

13 papers shown of 13, newest first; 13 places in the table. A paper with no recorded date is placed by the month its arXiv id encodes, shown in the Date column as YYYY-MM (from id). One row per place: a paper whose repository defines the name more than once appears more than once, and the same code body held for several papers appears once under each, with the same status. Titles and dates are the archive's archive 2025-07-28 for papers in the archive; 1 papers have no page here and are shown by their id only (arXiv: for an arXiv id; an id from another venue, such as ACL Anthology or AAAI, is named as that venue's id, never as an arXiv id). Status and fingerprint are Syntology's record of each code body; licence is recorded for each place. The File cell ends with the code body's 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.

PaperDateFileStatus SyntologyLicence
Omni-Recon: Harnessing Image-based Rendering for General-Purpose Neural Radiance Fields 17 Mar 2024 GATECH-EIC/Omni-Recon/evaluation/tsdf_fusion.py 8cb59f68a976f8ba ran; the contract check could not run (RAISES) MIT (permissive)
UFORecon: Generalizable Sparse-View Surface Reconstruction from Arbitrary and UnFavOrable Sets 8 Mar 2024 Youngju-Na/UFORecon/tsdf_fusion.py 8cb59f68a976f8ba ran; the contract check could not run (RAISES) MIT (permissive)
Scaling Up and Distilling Down: Language-Guided Robot Skill Acquisition 2023-07 (from id) real-stanford/scalingup/scalingup/algo/tsdf.py dc7f3e9cf45d3d8b ran no licence file found · pointer only
Introducing Competition to Boost the Transferability of Targeted Adversarial Examples through Clean Feature Mixup 24 May 2023 dreamflake/cfm/attacks.py 422be6728d89fc79 ran MIT (permissive)
InFusionSurf: Refining Neural RGB-D Surface Reconstruction Using Per-Frame Intrinsic Refinement and TSDF Fusion Prior Learning 8 Mar 2023 ROKIT-Healthcare/FastSurf/optimize.py 11f8b23014d15eb0 unverified MIT (permissive)
3D Former: Monocular Scene Reconstruction with 3D SDF Transformers 31 Jan 2023 alibaba-damo-academy/former3d/former3d/tsdf_fusion.py dc7f3e9cf45d3d8b ran MIT recorded; this copy not marked cleared · pointer only
Unsupervised Protein-Ligand Binding Energy Prediction via Neural Euler's Rotation Equation 25 Jan 2023 wengong-jin/dsmbind/bindenergy/utils/utils.py 1dbce577791aca7c ran MIT (permissive)
Semantic Abstraction: Open-World 3D Scene Understanding from 2D Vision-Language Models 23 Jul 2022 columbia-ai-robotics/semantic-abstraction/fusion.py dc7f3e9cf45d3d8b ran MIT (permissive) here; the stored copy is pointer only
BNV-Fusion: Dense 3D Reconstruction using Bi-level Neural Volume Fusion 3 Apr 2022 likojack/bnv_fusion/third_parties/fusion.py a1150c1b03c31b42 ran MIT (permissive)
VoRTX: Volumetric 3D Reconstruction With Transformers for Voxelwise View Selection and Fusion 1 Dec 2021 noahstier/vortx/vortx/tsdf_fusion.py dc7f3e9cf45d3d8b ran MIT (permissive) here; the stored copy is pointer only
Full-Body Visual Self-Modeling of Robot Morphologies 11 Nov 2021 BoyuanChen/visual-selfmodeling/fusion.py a1150c1b03c31b42 ran MIT (permissive)
NeuralRecon: Real-Time Coherent 3D Reconstruction from Monocular Video 1 Apr 2021 zju3dv/NeuralRecon/datasets/transforms.py a93502ff16e426c4 ran Apache-2.0 (permissive)
CVF open access id Ren_VolRecon_Volume_Rendering_of_Signed_Ray_Distance_Functions_for_Generalizable_CVPR_2023_paper IVRL/VolRecon/tsdf_fusion.py 8cb59f68a976f8ba ran; the contract check could not run (RAISES) MIT (permissive)

This site shows no code text; each File cell links to the file on GitHub at the repository's current default branch, which may have changed since the 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 under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text. 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 cell for the reason. Per-sample records for a paper are on its paper page under "Code Syntology ran".

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