4 of 4 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 2 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/2005.08131.json · badge: /api/ran/2005.08131.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 |
|---|---|---|
| microsoft/nanotune | community (classifier label) classifier basis not recorded on the link |
4 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| get_recursively | Ran ran on a synthesized input |
microsoft/nanotune/nanotune/utils.py code served (permissive licence) · get_code("ecae517f80f46b8f") 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 list, ndim 1, 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.
|
| register_vcs_handler | Ran ran; our contract draft was wrong, not the code |
microsoft/nanotune/nanotune/_version.py code served (permissive licence) · get_code("b06b3b57c757198b") 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 function. 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.
|
| run_command | Ran ran on a synthesized input |
microsoft/nanotune/nanotune/_version.py code served (permissive licence) · get_code("c568a8377abe39e7") 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 1, 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.
|
| versions_from_parentdir | Ran ran; our contract draft was wrong, not the code |
microsoft/nanotune/nanotune/_version.py pointer only (licence: MIT); the stored copy get_code serves, from Hhuangsj/GREX, is pointer only (licence: NONE) · get_code("b9a1535d27f2a9fb") How it ranThe body of this sample is withheld: this paper's link allows the body inline (MIT), but get_code serves the stored copy, first harvested from Hhuangsj/GREX, 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. |
Of 4 samples lifted from this paper's linked repositories, 4 carry a function identity and 0 do not. Of the 4 distinct functions with an identity, 3 are also present in other papers whose code we hold (2 with at least one paper dated earlier, 3 the same month, 2 later) and 1 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 |
|---|---|---|---|
| register_vcs_handler | 26 other papers 7 dated earlier, 1 the same month, 18 later |
1806.00550 (2018-06) A Swiss Army Infinitesimal Jackknife |
1806.03146 (2018-06) Neural Message Passing with Edge Updates for Predicting Properties of Molecules and Materials 1806.03720 (2018-06) Stochastic seismic waveform inversion using generative adversarial networks as a geological prior and 23 more not named here |
| versions_from_parentdir | 16 other papers 6 dated earlier, 1 the same month, 9 later |
1806.00550 (2018-06) A Swiss Army Infinitesimal Jackknife |
1806.03720 (2018-06) Stochastic seismic waveform inversion using generative adversarial networks as a geological prior 1812.01719 (2018-12) Knowing what you know in brain segmentation using Bayesian deep neural networks and 13 more not named here |
| run_command | 1 other paper 1 the same month |
2005.03788 (2020-05) ProSelfLC: Progressive Self Label Correction for Training Robust Deep Neural Networks |
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.
Automated tuning of gate-defined quantum dots is a requirement for large scale semiconductor based qubit initialisation. An essential step of these tuning procedures is charge state detection based on charge stability diagrams. Using supervised machine learning to perform this task requires a large dataset for models to train on. In order to avoid hand labelling experimental data, synthetic data has been explored as an alternative. While providing a significant increase in the size of the training dataset compared to using experimental data, using synthetic data means that classifiers are trained on data sourced from a different distribution than the experimental data that is part of the tuning process. Here we evaluate the prediction accuracy of a range of machine learning models trained on simulated and experimental data and their ability to generalise to experimental charge stability diagrams in two dimensional electron gas and nanowire devices. We find that classifiers perform best on either purely experimental or a combination of synthetic and experimental training data, and that adding common experimental noise signatures to the synthetic data does not dramatically improve the classification accuracy. These results suggest that experimental training data as well as realistic quantum dot simulations and noise models are essential in charge state detection using supervised machine learning.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2005.08131")
get_code_for_paper("2005.08131")
have("2005.08131")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2005.08131.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2005.08131)
Connect an agent — have() is free.