5 of 6 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 5 failures of our instrument; 1 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2402.10571.json · badge: /api/ran/2402.10571.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| rycolab/odpo | canonical (classifier label) classifier basis: census |
5 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| extract_anthropic_prompt | Ran ran; our contract draft was wrong, not the code |
rycolab/odpo/preference_datasets.py pointer only (licence: Apache-2.0); the stored copy get_code serves, from junkangwu/beta-DPO, is pointer only (licence: NONE) · get_code("12f6803880f9b17e") How it ranThe body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from junkangwu/beta-DPO, and GitHub detected no licence in that repository when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| get_local_dir | Ran ran; our contract draft was wrong, not the code |
rycolab/odpo/utils.py code served (permissive licence) · get_code("8ab43db002bf984d") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned str. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| get_local_run_dir | Ran ran; our contract draft was wrong, not the code |
rycolab/odpo/utils.py code served (permissive licence) · get_code("10ab71f27ffd7de8") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned str. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| get_remote_file | Ran ran; our contract draft was wrong, not the code |
rycolab/odpo/utils.py code served (permissive licence) · get_code("e7ce4c19888c6df6") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned str. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| preference_loss | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
rycolab/odpo/trainers.py code served (permissive licence) · get_code("86c5aaf696fc2128") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple, ndim 2, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| get_pos_sentiment_rewards | Not yet run unverified (harvested, no recorded run) |
rycolab/odpo/imdb_sentiment.py code served (permissive licence) · get_code("2e4ab4d5b3f6d465") How it ranno invocation recorded. |
Of 6 samples lifted from this paper's linked repositories, 6 carry a function identity and 0 do not. Of the 6 distinct functions with an identity, 4 are also present in other papers whose code we hold (4 with at least one paper dated earlier, 3 the same month, 4 later) and 2 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
| Function | Also present in | Earliest-dated | Others named |
|---|---|---|---|
| extract_anthropic_prompt | 15 other papers 5 dated earlier, 1 the same month, 9 later |
2309.16240 (2023-09) Beyond Reverse KL: Generalizing Direct Preference Optimization with Diverse Divergence Constraints |
2310.08164 (2023-10) Interpreting Learned Feedback Patterns in Large Language Models 2311.08380 (2023-11) Direct Preference Optimization for Neural Machine Translation with Minimum Bayes Risk Decoding and 12 more not named here |
| get_remote_file | 15 other papers 4 dated earlier, 3 the same month, 8 later |
2309.16240 (2023-09) Beyond Reverse KL: Generalizing Direct Preference Optimization with Diverse Divergence Constraints |
2312.00267 (2023-12) Sample Efficient Preference Alignment in LLMs via Active Exploration 2401.01967 (2024-01) A Mechanistic Understanding of Alignment Algorithms: A Case Study on DPO and Toxicity and 12 more not named here |
| get_local_run_dir | 11 other papers 3 dated earlier, 2 the same month, 6 later |
2309.16240 (2023-09) Beyond Reverse KL: Generalizing Direct Preference Optimization with Diverse Divergence Constraints |
2312.00267 (2023-12) Sample Efficient Preference Alignment in LLMs via Active Exploration 2401.13275 (2024-01) Can AI Assistants Know What They Don't Know? and 8 more not named here |
| get_local_dir | 10 other papers 3 dated earlier, 7 later |
2309.16240 (2023-09) Beyond Reverse KL: Generalizing Direct Preference Optimization with Diverse Divergence Constraints |
2401.01967 (2024-01) A Mechanistic Understanding of Alignment Algorithms: A Case Study on DPO and Toxicity 2401.13275 (2024-01) Can AI Assistants Know What They Don't Know? and 7 more not named here |
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
Direct preference optimization (DPO) is a successful fine-tuning strategy for aligning large language models with human preferences without the need to train a reward model or employ reinforcement learning. DPO, as originally formulated, relies on binary preference data and fine-tunes a language model to increase the likelihood of a preferred response over a dispreferred response. However, not all preference pairs are equal. Sometimes, the preferred response is only slightly better than the dispreferred one. In other cases, the preference is much stronger. For instance, if a response contains harmful or toxic content, the annotator will have a strong preference for that response. In this paper, we propose a generalization of DPO, termed DPO with an offset (ODPO), that does not treat every preference pair equally during fine-tuning. Intuitively, ODPO requires the difference between the likelihood of the preferred and dispreferred response to be greater than an offset value. The offset is determined based on the extent to which one response is preferred over another. Our experiments on various tasks suggest that ODPO significantly outperforms DPO in aligning language models, especially when the number of preference pairs is limited.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2402.10571")
get_code_for_paper("2402.10571")
have("2402.10571")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2402.10571.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2402.10571)
Connect an agent — have() is free.