Josiah Hanna, Nicholas Corrado
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, 0 violated it and 0 have no contract verdict; 4 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/2310.17786.json · badge: /api/ran/2310.17786.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 |
|---|---|---|
| badger-rl/understandingdataaugmentationforrl | canonical (classifier label) classifier basis: census |
5 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| get_latest_run_id | Ran ran, honoured the contract we drafted |
badger-rl/understandingdataaugmentationforrl/augment/rl/utils.py pointer only (licence: NONE) · get_code("cfe272902bb5f00e") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, badger-rl/understandingdataaugmentationforrl 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_save_dir | Ran ran; our contract draft was wrong, not the code |
badger-rl/understandingdataaugmentationforrl/augment/rl/utils.py pointer only (licence: NONE) · get_code("c710e4398c11123b") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, badger-rl/understandingdataaugmentationforrl 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. |
| read_hyperparameters | Ran ran; our contract draft was wrong, not the code |
badger-rl/understandingdataaugmentationforrl/augment/rl/utils.py pointer only (licence: NONE) · get_code("e657c953c05f376f") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, badger-rl/understandingdataaugmentationforrl 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. |
| simulate | Ran ran; our contract draft was wrong, not the code |
badger-rl/understandingdataaugmentationforrl/augment/simulate.py pointer only (licence: NONE) · get_code("834be0fa22de4614") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, badger-rl/understandingdataaugmentationforrl 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. |
| simulate | Ran ran; our contract draft was wrong, not the code |
badger-rl/understandingdataaugmentationforrl/augment/rl/generate_demonstrations.py pointer only (licence: NONE) · get_code("142d0a932e09216a") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, badger-rl/understandingdataaugmentationforrl 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 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, 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 5 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.
Recently, data augmentation (DA) has emerged as a method for leveraging domain knowledge to inexpensively generate additional data in reinforcement learning (RL) tasks, often yielding substantial improvements in data efficiency. While prior work has demonstrated the utility of incorporating augmented data directly into model-free RL updates, it is not well-understood when a particular DA strategy will improve data efficiency. In this paper, we seek to identify general aspects of DA responsible for observed learning improvements. Our study focuses on sparsereward tasks with dynamics-invariant data augmentation functions, serving as an initial step towards a more general understanding of DA and its integration into RL training. Experimentally, we isolate three relevant aspects of DA: state-action coverage, reward density, and the number of augmented transitions generated per update (the augmented replay ratio). From our experiments, we draw two conclusions: (1) increasing state-action coverage often has a much greater impact on data efficiency than increasing reward density, and (2) decreasing the augmented replay ratio substantially improves data efficiency. In fact, certain tasks in our empirical study are solvable only when the replay ratio is sufficiently low.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2310.17786")
get_code_for_paper("2310.17786")
have("2310.17786")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2310.17786.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2310.17786)
Connect an agent — have() is free.