Home › Code › analyze

analyze

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.

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

Licence is a property of each copy, so it is counted per place: 4 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 3 papers added by Syntology. 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
Context Convergence Improves Answering Inferential Questions added by Syntology 2026-05 (from id) DataScienceUIBK/Context-Convergence-Inferential-QA/experiments/order.py ccb09f79705369bd unverified MIT (permissive)
Identity as Attractor: Geometric Evidence for Persistent Agent Architecture in LLM Activation Space added by Syntology 2026-04 (from id) b102e/yar-attractor-experiment/bootstrap_experiment/bootstrap_analysis.py 6139c8c16a58411b ran · our draft was wrong no licence file found · pointer only
LIVECLIN: A Live CLINICAL BENCHMARK WITHOUT LEAKAGE added by Syntology 2026-02 (from id) AQ-MedAI/LiveClin/liveclin/analyzer.py 18565766a3c280c4 unverified Apache-2.0 (permissive)
FragFM: Hierarchical Framework for Efficient Molecule Generation via Fragment-Level Discrete Flow Matching 19 Feb 2025 datamol-io/safe/safe/_connect.py 520a0786e56b4db4 unverified Apache-2.0 (permissive)
Generalization v.s. Memorization: Tracing Language Models' Capabilities Back to Pretraining Data 20 Jul 2024 EleutherAI/the-pile/processing_scripts/lang_len_analysis_pass1.py fc867bf5f0532c70 unverified MIT (permissive)
CausalFormer: An Interpretable Transformer for Temporal Causal Discovery 24 Jun 2024 lingbai-kong/causalformer/interpret.py 0b0c090a1a2a5ec6 ran GPL-3.0 (copyleft) · pointer only
Position: Rethinking Post-Hoc Search-Based Neural Approaches for Solving Large-Scale Traveling Salesman Problems 2 Jun 2024 xyfffff/rethink_mcts_for_tsp/default_mcts/summarize.py 071321bfe70783a2 ran · our draft was wrong no licence file found · pointer only
M4GT-Bench: Evaluation Benchmark for Black-Box Machine-Generated Text Detection 17 Feb 2024 mbzuai-nlp/m4gt-bench/src/GLTR/server.py c3dfa77d1a3ca4e1 ran · our draft was wrong no licence file found · pointer only
GLTR: Statistical Detection and Visualization of Generated Text 10 Jun 2019 HendrikStrobelt/detecting-fake-text/server.py c3dfa77d1a3ca4e1 ran · our draft was wrong Apache-2.0 (permissive)
PixelDefend: Leveraging Generative Models to Understand and Defend against Adversarial Examples 30 Oct 2017 Microsoft/PixelDefend/utils.py 8444dfceccf614a8 ran fingerprinted MIT (permissive)
TinyLFU: A Highly Efficient Cache Admission Policy 2015-12 (from id) ben-manes/caffeine/.claude/skills/climber-gate/blindlock.py 7c4d4500251649a1 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