Home › Code › get_local_dir

get_local_dir

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.

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

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

14 papers shown of 14, newest first; 14 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. 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
Beyond Toxic Neurons: A Mechanistic Analysis of DPO for Toxicity Reduction 10 Nov 2024 yushi-y/dpo-toxic-neurons/train_dpo/dpo_utils.py 8ab43db002bf984d ran · our draft was wrong MIT (permissive)
On Extending Direct Preference Optimization to Accommodate Ties 25 Sep 2024 eric-mitchell/direct-preference-optimization/utils.py 8ab43db002bf984d ran · our draft was wrong Apache-2.0 (permissive)
Learning Dynamics of LLM Finetuning 15 Jul 2024 joshua-ren/learning_dynamics_llm/src/utils.py 8ab43db002bf984d ran · our draft was wrong Apache-2.0 (permissive)
$β$-DPO: Direct Preference Optimization with Dynamic $β$ 11 Jul 2024 junkangwu/beta-dpo/utils.py 8ab43db002bf984d ran · our draft was wrong no licence file found · pointer only
Towards Robust Alignment of Language Models: Distributionally Robustifying Direct Preference Optimization 10 Jul 2024 junkangwu/dr_dpo/utils.py 8ab43db002bf984d ran · our draft was wrong no licence file found · pointer only
Group Robust Preference Optimization in Reward-free RLHF 30 May 2024 rsshyam/Group-robust-preference-optimization/src/utils.py 8ab43db002bf984d ran · our draft was wrong Apache-2.0 (permissive)
Token-level Direct Preference Optimization 18 Apr 2024 vance0124/token-level-direct-preference-optimization/utils.py 8ab43db002bf984d ran · our draft was wrong Apache-2.0 (permissive)
A Critical Evaluation of AI Feedback for Aligning Large Language Models 19 Feb 2024 architsharma97/dpo-rlaif/utils.py 2a9c061a2b1c35cf ran · our draft was wrong fingerprinted Apache-2.0 (permissive)
Relative Preference Optimization: Enhancing LLM Alignment through Contrasting Responses across Identical and Diverse Prompts 12 Feb 2024 yinyueqin/relative-preference-optimization/utils.py c17340586a6311f0 ran · our draft was wrong Apache-2.0 (permissive)
Direct Preference Optimization with an Offset 16 Feb 2024 rycolab/odpo/utils.py 8ab43db002bf984d ran · our draft was wrong Apache-2.0 (permissive)
Can AI Assistants Know What They Don't Know? 24 Jan 2024 openmoss/say-i-dont-know/src/dpo/utils.py 8ab43db002bf984d ran · our draft was wrong no licence file found · pointer only
A Mechanistic Understanding of Alignment Algorithms: A Case Study on DPO and Toxicity 3 Jan 2024 ajyl/dpo_toxic/toxicity/train_dpo/dpo_utils.py 8ab43db002bf984d ran · our draft was wrong MIT (permissive)
Sample Efficient Preference Alignment in LLMs via Active Exploration 1 Dec 2023 belakaria/active-llm-alignment/utils.py f66e1f726f4fa9d6 ran · our draft was wrong MIT (permissive)
Beyond Reverse KL: Generalizing Direct Preference Optimization with Diverse Divergence Constraints 28 Sep 2023 alecwangcq/f-divergence-dpo/utils.py 8ab43db002bf984d ran · our draft was wrong 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