Home › Code › bootstrap

bootstrap

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.

bootstrap 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, 10 with a sample that ran: 8 with a run with no instrument failure, 2 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 bootstrap 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 bootstrap: 8 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 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
1ran · our draft was wrong
0ran; the contract check could not run
7ran
1unverified
1fingerprinted

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

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 1 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
Max-pooling Network Revisited: Analyzing the Role of Semantic Probability in Multiple Instance Learning for Hallucination Detection added by Syntology 2026-05 (from id) FUJI1229/Hallucination_Detection/gen/generation/uncertainty/utils/eval_utils.py 4b00bf597ecfdaac ran · our draft was wrong MIT (permissive)
Semantic Entropy Probes: Robust and Cheap Hallucination Detection in LLMs 22 Jun 2024 oatml/semantic-entropy-probes/semantic_uncertainty/uncertainty/utils/eval_utils.py 4b00bf597ecfdaac ran · our draft was wrong MIT (permissive)
MoCa: Measuring Human-Language Model Alignment on Causal and Moral Judgment Tasks 30 Oct 2023 cicl-stanford/moca/experiments/causal_effect_analysis.py fd056bb65f483c64 ran no licence file found · pointer only
The Topology and Geometry of Neural Representations 20 Sep 2023 doerlbh/topologicalrsa/utils_stats.py 593a327fd9465d8e ran no licence file found · pointer only
arXiv:2307.06422 2023-07 (from id) thupchnsky/dp-gnn/core/utils.py 3083dc7c7310cba3 ran MIT (permissive)
GAP: Differentially Private Graph Neural Networks with Aggregation Perturbation 2 Mar 2022 sisaman/gap/core/utils.py 3083dc7c7310cba3 ran CC0-1.0 (permissive)
$Q^{2}$: Evaluating Factual Consistency in Knowledge-Grounded Dialogues via Question Generation and Question Answering 16 Apr 2021 orhonovich/q-squared/system_level.py be95edb39d85841d ran Apache-2.0 (permissive)
A Survey on Reproducibility by Evaluating Deep Reinforcement Learning Algorithms on Real-World Robots 9 Sep 2019 dti-research/SenseActExperiments/evaluate/evaluate.py 72d7383d8fc116f0 ran BSD-3-Clause (permissive)
Learning Temporal Coherence via Self-Supervision for GAN-based Video Generation 23 Nov 2018 thunil/TecoGAN/LPIPSmodels/util.py e5bd7d84ecd3318d unverified Apache-2.0 (permissive)
A Bayesian approach to linear regression in astronomy 2015-09 (from id) rsnemmen/BCES/bces/bces.py ade06d7c5c714e50 ran fingerprinted MIT (permissive)
Introduction to astroML: Machine Learning for Astrophysics 2014-11 (from id) LBJ-Wade/astroML/astroML/resample.py 5a73f1eddaa803ee ran BSD-2-Clause (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