Aishwarya Balwani, Jakob Krzyston
2 of 2 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (2 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; 0 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/2206.06563.json · badge: /api/ran/2206.06563.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 |
|---|---|---|
| ganguli-lab/Synaptic-Flow | community Papers with Code archive |
2 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| Mag | Ran ran on a synthesized input · constructed an object; no result was computed |
ganguli-lab/Synaptic-Flow/Pruners/pruners.py pointer only (licence: NONE) · get_code("482f4c47b4e2c46e") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, ganguli-lab/Synaptic-Flow 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. |
| Pruner | Ran ran on a synthesized input · constructed an object; no result was computed |
ganguli-lab/Synaptic-Flow/Pruners/pruners.py pointer only (licence: NONE) · get_code("25100e43d36881c9") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, ganguli-lab/Synaptic-Flow 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, 1 are also present in other papers whose code we hold (1 with at least one paper dated earlier, 0 the same month, 1 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 |
|---|---|---|---|
| Pruner brick of this paper's assembly: helper |
3 other papers 2 dated earlier, 1 later · 3 only as an assembly brick |
1810.02340 (2018-10) SNIP: Single-shot Network Pruning based on Connection Sensitivity |
2006.05467 (2020-06) Pruning neural networks without any data by iteratively conserving synaptic flow 2304.02840 (2023-04) NTK-SAP: Improving neural network pruning by aligning training dynamics |
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.
Modern-day neural networks are famously large, yet also highly redundant and compressible; there exist numerous pruning strategies in the deep learning literature that yield over 90% sparser sub-networks of fully-trained, dense architectures while still maintaining their original accuracies. Amongst these many methods though -thanks to its conceptual simplicity, ease of implementation, and efficacy -Iterative Magnitude Pruning (IMP) dominates in practice and is the de facto baseline to beat in the pruning community. However, theoretical explanations as to why a simplistic method such as IMP works at all are few and limited. In this work, we leverage the notion of persistent homology to gain insights into the workings of IMP and show that it inherently encourages retention of those weights which preserve topological information in a trained network. Subsequently, we also provide bounds on how much different networks can be pruned while perfectly preserving their zeroth order topological features, and present a modified version of IMP to do the same.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2206.06563")
get_code_for_paper("2206.06563")
have("2206.06563")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2206.06563.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2206.06563)
Connect an agent — have() is free.