5 of 5 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; 1 honoured the contract we drafted, 2 violated it and 0 have no contract verdict; 2 failures of our instrument; 0 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/2409.12147.json · badge: /api/ran/2409.12147.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 |
|---|---|---|
| dinobby/magicore | canonical (classifier label) classifier basis: census |
5 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| floatify | Ran ran, honoured the contract we drafted |
dinobby/magicore/math_utils.py code served (permissive licence) · get_code("02f0014017b66dcb") 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 float, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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_choice | Ran ran; our contract draft was wrong, not the code |
dinobby/magicore/utils.py code served (permissive licence) · get_code("a29f1c51ddcf33d9") 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.
|
| last_boxed_only_string | Ran ran; our contract draft was wrong, not the code |
dinobby/magicore/math_utils.py code served (permissive licence) · get_code("0b14c648516c38a7") 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.
|
| std_normalize | Ran ran, violated the contract we drafted |
dinobby/magicore/utils.py code served (permissive licence) · get_code("f9bcc492a7976380") 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 ndarray, ndim 1, dtype family float, shape (4,) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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.
|
| within_eps | Ran ran, violated the contract we drafted |
dinobby/magicore/math_utils.py code served (permissive licence) · get_code("e8f6bab9810c154d") 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 bool, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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.
|
Of 5 samples lifted from this paper's linked repositories, 5 carry a function identity and 0 do not. Of the 5 distinct functions with an identity, 5 are also present in other papers whose code we hold (1 with at least one paper dated earlier, 0 the same month, 5 later) and 0 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 |
|---|---|---|---|
| last_boxed_only_string | 17 other papers 7 dated earlier, 9 later, 1 same year, order not determinable |
2309.06275 (2023-09) Re-Reading Improves Reasoning in Large Language Models |
2310.05914 (2023-10) NEFTune: Noisy Embeddings Improve Instruction Finetuning 2024.findings-emnlp.407 (2024 (year only)) MultiAgent Collaboration Attack: Investigating Adversarial Attacks in Large Language Model Collaborations via Debate and 14 more not named here |
| floatify | 1 other paper 1 later |
2025.emnlp-main.1660 (2025 (year only)) MAGICORE: Multi-Agent, Iterative, Coarse-to-Fine Refinement for Reasoning |
|
| get_choice | 1 other paper 1 later |
2025.emnlp-main.1660 (2025 (year only)) MAGICORE: Multi-Agent, Iterative, Coarse-to-Fine Refinement for Reasoning |
|
| std_normalize | 1 other paper 1 later |
2025.emnlp-main.1660 (2025 (year only)) MAGICORE: Multi-Agent, Iterative, Coarse-to-Fine Refinement for Reasoning |
|
| within_eps | 1 other paper 1 later |
2025.emnlp-main.1660 (2025 (year only)) MAGICORE: Multi-Agent, Iterative, Coarse-to-Fine Refinement for Reasoning |
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.
Large Language Models' (LLM) reasoning can be improved using test-time aggregation strategies, i.e., generating multiple samples and voting among generated samples. While these improve performance, they often reach a saturation point. Refinement offers an alternative by using LLM-generated feedback to improve solution quality. However, refinement introduces 3 key challenges: (1) Excessive refinement: Uniformly refining all instances can over-correct and reduce the overall performance. (2) Inability to localize and address errors: LLMs have a limited ability to self-correct and struggle to identify and correct their own mistakes. (3) Insufficient refinement: Deciding how many iterations of refinement are needed is non-trivial, and stopping too soon could leave errors unaddressed. To tackle these issues, we propose MAgICoRe, which avoids excessive refinement by categorizing problem difficulty as easy or hard, solving easy problems with coarse-grained aggregation and hard ones with fine-grained and iterative multi-agent refinement. To improve error localization, we incorporate external step-wise reward model (RM) scores. Moreover, to ensure effective refinement, we employ a multi-agent loop with three agents: Solver, Reviewer (which generates targeted feedback based on step-wise RM scores), and the Refiner (which incorporates feedback). To ensure sufficient refinement, we re-evaluate updated solutions, iteratively initiating further rounds of refinement. We evaluate MAgICoRe on Llama-3-8B and GPT-3.5 and show its effectiveness across 5 math datasets. Even one iteration of MAgICoRe beats Self-Consistency by 3.4%, Best-of-k by 3.2%, and Self-Refine by 4.0% while using less than half the samples. Unlike iterative refinement with baselines, MAgICoRe continues to improve with more iterations. Finally, our ablations highlight the importance of MAgICoRe's RMs and multi-agent communication.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2409.12147")
get_code_for_paper("2409.12147")
have("2409.12147")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2409.12147.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2409.12147)
Connect an agent — have() is free.