Home › Code › read_annotations

read_annotations

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

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

7 papers shown of 7, newest first; 7 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. 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
DeTracker: Motion-decoupled Vehicle Detection and Tracking in Unstabilized Satellite Videos added by Syntology 2026-01 (from id) alex-chenjiajun/DeTracker/cropdata.py 1cdbe0121d1e28eb ran · our draft was wrong fingerprinted licence not identified · pointer only
Are CLIP features all you need for Universal Synthetic Image Origin Attribution? 17 Aug 2024 ciodar/universalattribution/utils/common.py ce24138500c16e6a ran no licence file found · pointer only
Are current long-term video understanding datasets long-term? 22 Aug 2023 ombretta/longterm_datasets/user_studies/analyze_results_segments.py d25d7a7df31b3bb3 unverified GPL-3.0 (copyleft) · pointer only
Evaluating Open-Domain Question Answering in the Era of Large Language Models 11 May 2023 ehsk/openqa-eval/src/oqaeval/data_utils.py 31c47735d7c5be2a ran MIT (permissive)
MKQA: A Linguistically Diverse Benchmark for Multilingual Open Domain Question Answering 30 Jul 2020 apple/ml-mkqa/mkqa_eval.py d866f827b0e9464d ran Apache-2.0 (permissive)
Measuring Information Propagation in Literary Social Networks 29 Apr 2020 dbamman/litbank/tagger/sequence_layered_reader.py 8f2280fa6d13b997 ran · our draft was wrong no licence file found · pointer only
StackGAN++: Realistic Image Synthesis with Stacked Generative Adversarial Networks 19 Oct 2017 akanimax/T2F/implementation/data_processing/TextExtractor.py dbb904b43aad3c12 ran 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