Martha White, Csaba Szepesvári, Claire Vernade, Florian Dörfler, Michael Muehlebach, Onno Eberhard, Miroslav Krstic
2 of 2 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; 2 failures of our instrument; 0 no recorded run), measured 2026-11-22; 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/2608.02433.json · badge: /api/ran/2608.02433.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 |
|---|---|---|
| onnoeberhard/forlac-tutorial | canonical (classifier label) classifier basis: census |
2 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| f | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
onnoeberhard/forlac-tutorial/mrac.py pointer only (licence: NONE) · get_code("2560d2fda0296f12") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, onnoeberhard/forlac-tutorial 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. |
| ff | Ran ran; our contract draft was wrong, not the code |
onnoeberhard/forlac-tutorial/mrac.py pointer only (licence: NONE) · get_code("2a6a49cc5ec09513") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, onnoeberhard/forlac-tutorial 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. |
Of 2 samples lifted from this paper's linked repositories, 2 carry a function identity and 0 do not. Of the 2 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 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.
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.
Reinforcement learning and control theory are two adjacent scientific fields that focus on optimizing the controller of unknown dynamical systems using feedback. While both fields have common roots in dynamic programming, they have evolved with distinct methodologies, goals, and cultures. Despite decades of mutual influence, a significant gap persists between the two communities. This tutorial introduces adaptive control, actor-critic reinforcement algorithms, and a new way to combine these two paradigms for data-driven decision making on a classical locomotion control problem. Our aim is to provide a foundation for understanding the core differences between the two approaches and insights to help experts in each field better understand and engage with the tools and approaches of the other.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2608.02433")
get_code_for_paper("2608.02433")
have("2608.02433")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2608.02433.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2608.02433)
Connect an agent — have() is free.