Home › Code › process_csv

process_csv

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.

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

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

5 papers shown of 5, newest first; 6 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
Nsanku: Evaluating Zero-Shot Translation Performance of LLMs for Ghanaian Languages added by Syntology 2026-05 (from id) GhanaNLP/nsanku/repo/main-with-similarity-bk.py dceffe868db232be ran · our draft was wrong no licence file found · pointer only
Sycophancy Hides Linearly in the Attention Heads added by Syntology 2026-01 (from id) rifoagenadi/sycophancy/extension/judge.py 97c9e69ad485811e unverified no licence file found · pointer only
Revisiting VerilogEval: A Year of Improvements in Large-Language Models for Hardware Code Generation 20 Aug 2024 nvlabs/verilog-eval/count_failures.py 0b9143f06db3374a ran · our draft was wrong fingerprinted licence not identified · pointer only
The Music Maestro or The Musically Challenged, A Massive Music Evaluation Benchmark for Large Language Models 22 Jun 2024 zcli-charlie/ziqi-eval/src/five-shot.py 93be72957cb84414 unverified no licence file found · pointer only
The Music Maestro or The Musically Challenged, A Massive Music Evaluation Benchmark for Large Language Models 22 Jun 2024 zcli-charlie/ziqi-eval/src/zero-shot-eval.py 6b015217d6b3400c unverified no licence file found · pointer only
IJCAI id ijcai2025_1031 yczju/cycseq/dataset/preprocess.py c9f8d4041f56441a 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