Niels Ipsen, Pierre-Alexandre Mattei, Jes Frellsen
5 of 6 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 4 have no contract verdict; 1 failure of our instrument; 1 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/2006.12871.json · badge: /api/ran/2006.12871.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 |
|---|---|---|
| falaaharifkhan/data-cleaning-stability | community (classifier label) classifier basis not recorded on the link |
5 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| cost_function | Ran ran; our contract draft was wrong, not the code |
falaaharifkhan/data-cleaning-stability/external_dependencies/HIVAE/model_HIVAE_inputDropout.py code served (permissive licence) · get_code("4d4a3a21633920ba") 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. 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.
|
| impute_with_deletion | Ran ran on a synthesized input |
falaaharifkhan/data-cleaning-stability/source/null_imputers/imputation_methods.py code served (permissive licence) · get_code("b709e4c4775dfc69") 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. 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.
|
| impute_with_simple_imputer | Ran ran on a synthesized input |
falaaharifkhan/data-cleaning-stability/source/null_imputers/imputation_methods.py code served (permissive licence) · get_code("b8d20a70ee596725") 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. 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.
|
| read_repaired_datasets | Ran ran on a synthesized input |
falaaharifkhan/data-cleaning-stability/source/null_imputers/joint_cleaning_and_training_methods.py code served (permissive licence) · get_code("cb953ffd6bfb3c39") 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 dict. 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.
|
| sample_inducing_points | Ran ran on a synthesized input |
falaaharifkhan/data-cleaning-stability/external_dependencies/azua/utils/data_mask_utils.py code served (permissive licence) · get_code("1ecc51330c6c3519") 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. 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.
|
| transform_from_configs | Not yet run unverified (harvested, no recorded run) |
falaaharifkhan/data-cleaning-stability/external_dependencies/azua/utils/data_transform.py code served (permissive licence) · get_code("41f83405ac2136e0") How it ranno invocation recorded. |
Of 6 samples lifted from this paper's linked repositories, 6 carry a function identity and 0 do not. Of the 6 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, 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.
| Function | Also present in | Earliest-dated | Others named |
|---|---|---|---|
| cost_function | 1 other paper 1 dated earlier |
1807.03653 (2018-07) Handling Incomplete Heterogeneous Data using VAEs |
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.
When a missing process depends on the missing values themselves, it needs to be explicitly modelled and taken into account while doing likelihood-based inference. We present an approach for building and fitting deep latent variable models (DLVMs) in cases where the missing process is dependent on the missing data. Specifically, a deep neural network enables us to flexibly model the conditional distribution of the missingness pattern given the data. This allows for incorporating prior information about the type of missingness (e.g. self-censoring) into the model. Our inference technique, based on importance-weighted variational inference, involves maximising a lower bound of the joint likelihood. Stochastic gradients of the bound are obtained by using the reparameterisation trick both in latent space and data space. We show on various kinds of data sets and missingness patterns that explicitly modelling the missing process can be invaluable.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2006.12871")
get_code_for_paper("2006.12871")
have("2006.12871")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2006.12871.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2006.12871)
Connect an agent — have() is free.