Home › Code › convert_to_ndc

convert_to_ndc

Syntologyentry name in harvested 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.

convert_to_ndc appears in the code Syntology harvested for 11 papers, as 9 distinct code bodies found in 11 places (a place is one code body under one paper). Of the 11 papers, 11 with a sample that ran: 11 with a run with no instrument failure, 0 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 convert_to_ndc 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 9 distinct code bodies named convert_to_ndc: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 0 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
0ran; the contract check could not run
9ran
0unverified
0fingerprinted

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

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. 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
HDRSplat: Gaussian Splatting for High Dynamic Range 3D Scene Reconstruction from Raw Images 23 Jul 2024 shreyesss/hdrsplat/internal/camera_utils.py f4dbe624cddbd165 ran no licence file found · pointer only
FPO++: Efficient Encoding and Rendering of Dynamic Neural Radiance Fields by Analyzing and Enhancing Fourier PlenOctrees 31 Oct 2023 saskiarabich/fpoplusplus/svox/svox/renderer.py 0591ba2ee60fe30e ran MIT (permissive)
ExBluRF: Efficient Radiance Fields for Extreme Motion Blurred Images 16 Sep 2023 taekkii/exblurf/plenoxel/utils.py d114323f9841fe66 ran MIT (permissive)
Where and How: Mitigating Confusion in Neural Radiance Fields from Sparse Inputs 5 Aug 2023 bbbbby-99/wah-nerf/WaHNeRF/ray_utils.py 2530cb2ea3170f45 ran no licence file found · pointer only
FlipNeRF: Flipped Reflection Rays for Few-shot Novel View Synthesis 30 Jun 2023 shawn615/FlipNeRF/internal/datasets.py 9bf161da38d57d6d ran MIT (permissive)
SeaThru-NeRF: Neural Radiance Fields in Scattering Media 16 Apr 2023 deborahLevy130/seathru_NeRF/internal/camera_utils.py 37786d257d8feb6f ran Apache-2.0 (permissive)
Zip-NeRF: Anti-Aliased Grid-Based Neural Radiance Fields 13 Apr 2023 SuLvXiangXin/zipnerf-pytorch/internal/camera_utils.py 3f7d7d7a2f4ba014 ran Apache-2.0 (permissive)
MixNeRF: Modeling a Ray with Mixture Density for Novel View Synthesis from Sparse Inputs 17 Feb 2023 shawn615/MixNeRF/internal/datasets.py 9bf161da38d57d6d ran MIT (permissive)
Exact-NeRF: An Exploration of a Precise Volumetric Parameterization for Neural Radiance Fields 22 Nov 2022 kostadinovshalon/exact-nerf/internal/camera_utils.py f4dbe624cddbd165 ran Apache-2.0 (permissive) here; the stored copy is pointer only
Block-NeRF: Scalable Large Scene Neural View Synthesis 10 Feb 2022 dvlab-research/LargeScaleNeRFPytorch/FourierGrid/camera_utils.py ce266e17c5088b07 ran MIT (permissive)
Mip-NeRF: A Multiscale Representation for Anti-Aliasing Neural Radiance Fields 24 Mar 2021 google/mipnerf/internal/datasets.py 7115b692e467d100 ran Apache-2.0 (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