Home › Code › r2

r2

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.

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

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

Licence is a property of each copy, so it is counted per place: 2 of the 10 places are 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

10 papers shown of 10, newest first; 10 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 3 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
The Granularity Gap: A Multi-Dimensional Cross-Generational Audit of Sycophancy in Gemini Models added by Syntology 2026-06 (from id) pskeough/The-Granularity-Gap/pipeline/03_analyse.py c191541542b916a3 ran · honoured contract fingerprinted licence not identified · pointer only
Do Deep Ensembles Actually Capture Uncertainty in Graph Neural Networks? added by Syntology 2026-05 (from id) PedrV/gnn-uq-inspector/inspector/metrics/metrics.py d207a9fb1d8b350c ran · honoured contract fingerprinted Apache-2.0 (permissive)
Which Leakage Types Matter? A Quantitative Landscape Across 2,047 Benchmark Datasets added by Syntology 2026-04 (from id) epagogy/ml/al/benchmarks/bench_vs_sklearn.py 8057ced46afec5dc ran · violated contract fingerprinted MIT (permissive)
A path-dependent PDE solver based on signature kernels 2024-03 (from id) crispitagorico/sigppde/utils.py 7499638ce4557e09 ran fingerprinted MIT (permissive)
Density of States Prediction of Crystalline Materials via Prompt-guided Multi-Modal Transformer 24 Oct 2023 HeewoongNoh/DOSTransformer/utils.py d49884152e6f65bb ran fingerprinted no licence file found · pointer only
PARC: Physics-Aware Recurrent Convolutional Neural Networks to Assimilate Meso-scale Reactive Mechanics of Energetic Materials 4 Apr 2022 stephenbaek/parc/parc/losses.py b6f78266a0720d6a ran MIT (permissive)
Data-driven derivation of stellar properties from photometric time series data using convolutional neural networks 2020-05 (from id) kblancato/theia-net/theia-net/regression/modules/evaluate.py ff541345c9f09342 ran fingerprinted MIT (permissive)
Deep Learning for Time Series Forecasting: The Electric Load Case 22 Jul 2019 albertogaspar/dts/dts/utils/losses.py e2dc8141ba835fb9 unverified MIT (permissive)
T-GCN: A Temporal Graph ConvolutionalNetwork for Traffic Prediction 12 Nov 2018 martinwhl/T-GCN-PyTorch/utils/metrics.py aad50acb99c1b62c ran fingerprinted MIT (permissive)
AAAI id aaai_16101 sustainlab-group/mapillarygcn/models/clusterwise_regressor.py fe4d69f38e021800 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