Home › Code › read_text_file

read_text_file

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.

read_text_file 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, 8 with a sample that ran: 5 with a run with no instrument failure, 3 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 read_text_file 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 read_text_file: 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 3 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:

0ran · honoured contract
0ran · violated contract
3ran · our draft was wrong
0ran; the contract check could not run
5ran
2unverified
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 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
AutoFigure: Generating and Refining Publication-Ready Scientific Illustrations added by Syntology 2026-02 (from id) ResearAI/AutoFigure/autofigure/utils/file_utils.py 885a9be17bd669b0 ran · our draft was wrong fingerprinted MIT (permissive)
Publishing FAIR and Machine-actionable Reviews in Materials Science: The Case for Symbolic Knowledge in Neuro-symbolic Artificial Intelligence added by Syntology 2026-01 (from id) sciknoworg/ald-ale-orkg-review/llm-experiments/neurosymbolic_table_qa.py 0021168124eb1741 ran · our draft was wrong Apache-2.0 (permissive)
VIS-Shepherd: Constructing Critic for LLM-based Data Visualization Generation 16 Jun 2025 bopan3/vis-shepherd/Evaluation/run_single_autoEvaluateLikert.py e9dedc0a23670508 ran · our draft was wrong no licence file found · pointer only
Liar, Liar, Logical Mire: A Benchmark for Suppositional Reasoning in Large Language Models 18 Jun 2024 mainlp/TruthQuest/metareasoning/utils/utils.py c387ce2fd70d9c06 unverified CC-BY-SA-4.0 (copyleft) · pointer only
Comparing Inferential Strategies of Humans and Large Language Models in Deductive Reasoning 20 Feb 2024 mainlp/inferential-strategies/reasoning_strategies/utils/utils.py c387ce2fd70d9c06 unverified CC-BY-SA-4.0 (copyleft) · pointer only
EvalCrafter: Benchmarking and Evaluating Large Video Generation Models 17 Oct 2023 EvalCrafter/EvalCrafter/metrics/ocr_score.py afc709e407f0b256 ran no licence file found · pointer only
Chat Vector: A Simple Approach to Equip LLMs with Instruction Following and Model Alignment in New Languages 7 Oct 2023 augmxnt/deccp/upload-dataset.py 00d5313d11630f56 ran Apache-2.0 (permissive)
TLDR: Extreme Summarization of Scientific Documents 30 Apr 2020 allenai/scitldr/SciTLDR-Data/make_datafiles.py 8175760b8eddec2b ran Apache-2.0 (permissive)
Learning Temporal Coherence via Self-Supervision for GAN-based Video Generation 23 Nov 2018 thunil/TecoGAN/LPIPSmodels/util.py 276eacceee671652 unverified Apache-2.0 (permissive)
Structured Neural Summarization 5 Nov 2018 CoderPat/structured-neural-summarization/parsers/naturallanguage/dmcnn/splitfiles.py cb13d80aaaa6db14 ran MIT (permissive)
ACL Anthology id 2023.findings-emnlp.384 JHL-HUST/SparseMA/dataloader/mvsa_dataset.py e58ad7fa2214cbf0 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