Home › Code › load_poses

load_poses

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.

load_poses appears in the code Syntology harvested for 11 papers, as 8 distinct code bodies found in 11 places (a place is one code body under one paper). Of the 11 papers, 10 with a sample that ran: 10 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument. 1 of the code bodies carries 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 load_poses 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 8 distinct code bodies named load_poses: 7 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 with no contract checked; 0 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:

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

Licence is a property of each copy, so it is counted per place: 1 of the 11 places is pointer only (Syntology does not serve that copy's text). 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

11 papers shown of 11, newest first; 11 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, and the graph's for 2 papers added by Syntology; 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
LiFlow: Flow Matching for 3D LiDAR Scene Completion added by Syntology 2026-02 (from id) matteandre/LiFlow/liflow/utils/eval_path.py 21cd8e2f060ce50c ran · honoured contract MIT (permissive)
VA-GS: Enhancing the Geometric Representation of Gaussian Splatting via View Alignment added by Syntology 2025-10 (from id) LeoQLi/VA-GS/scene/dataset_readers.py ac53f2d3e9abe6b5 ran no licence file found · pointer only
Towards Generating Realistic 3D Semantic Training Data for Autonomous Driving 27 Mar 2025 prbonn/3diss/diss/utils/collations.py ee48797f1ee1aafe ran MIT (permissive)
Scaling Diffusion Models to Real-World 3D LiDAR Scene Completion 20 Mar 2024 prbonn/lidiff/lidiff/map_from_scans.py 21cd8e2f060ce50c ran · honoured contract MIT (permissive)
ObjectSDF++: Improved Object-Compositional Neural Implicit Surfaces 15 Aug 2023 qianyiwu/objectsdf_plus/scannet_eval/evaluate.py b5dfc40a6055fa6b ran MIT (permissive)
PCPNet: An Efficient and Semantic-Enhanced Transformer Network for Point Cloud Prediction 16 Apr 2023 blurryface0814/pcpnet/pcpnet/utils/utils.py ad221712326a962d ran fingerprinted 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/datasets/load_scannet.py c30c27242d09e709 ran MIT (permissive)
DPM-Solver: A Fast ODE Solver for Diffusion Probabilistic Model Sampling in Around 10 Steps 2 Jun 2022 astra-vision/LiDPM/lidpm/utils/pcd_preprocess.py dd375501c42dd070 ran Apache-2.0 (permissive)
MonoSDF: Exploring Monocular Geometric Cues for Neural Implicit Surface Reconstruction 1 Jun 2022 autonomousvision/monosdf/scannet_eval/evaluate.py b5dfc40a6055fa6b ran MIT (permissive)
Self-supervised Point Cloud Prediction Using 3D Spatio-temporal Convolutional Networks 28 Sep 2021 prbonn/point-cloud-prediction/pcf/utils/utils.py ad221712326a962d ran fingerprinted MIT (permissive)
CVF open access id Nunes_Temporal_Consistent_3D_LiDAR_Representation_Learning_for_Semantic_Perception_in_CVPR_2023_paper PRBonn/TARL/tarl/utils/pcd_preprocess.py 0dedf9ada0ee691b unverified 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