8 of 9 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, 1 violated it and 5 have no contract verdict; 2 failures 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/1904.02639.json · badge: /api/ran/1904.02639.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 |
|---|---|---|
| donggong1/memae-anomaly-detection | community (classifier label) classifier basis not recorded on the link |
6 ran · 0 no recorded run |
| YeongHyeon/MemAE | community (classifier label) classifier basis not recorded on the link |
2 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| crop_image | Ran ran on a synthesized input |
donggong1/memae-anomaly-detection/utils/utils.py code served (permissive licence) · get_code("dbb1ce6b9400bd85") 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 Tensor, ndim 3, dtype family float, shape (2, 6, 6) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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.
|
| dat2canvas | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
YeongHyeon/MemAE/source/tf_process.py code served (permissive licence) · get_code("9a083fc9c5cd9850") 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 ndarray, ndim 3, dtype family float, shape (56, 56, 3) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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.
|
| feature_map_permute | Ran ran on a synthesized input |
donggong1/memae-anomaly-detection/models/entropy_loss.py code served (permissive licence) · get_code("81f7962015e0eda6") 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 Tensor, ndim 2, dtype family float, shape (30, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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.
|
| get_subdir_list | Ran ran on a synthesized input |
donggong1/memae-anomaly-detection/utils/utils.py code served (permissive licence) · get_code("edff0ecdd8e380de") 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.
|
| gray2rgb | Ran ran on a synthesized input |
YeongHyeon/MemAE/source/tf_process.py code served (permissive licence) · get_code("aa166086c035e6eb") 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 ndarray, ndim 3, dtype family float, shape (4, 3, 3) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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.
|
| hard_shrink_relu | Ran ran; our contract draft was wrong, not the code |
donggong1/memae-anomaly-detection/models/memory_module.py code served (permissive licence) · get_code("9a26454b2ff613bb") 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 Tensor, ndim 2, dtype family float, shape (2, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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.
|
| str2bool | Ran ran, violated the contract we drafted |
donggong1/memae-anomaly-detection/options/testing_options.py code served (permissive licence) · get_code("f017532fc389cbfe") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned bool, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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.
|
| tensor2numpy | Ran ran on a synthesized input |
donggong1/memae-anomaly-detection/utils/utils.py code served (permissive licence) · get_code("20c6252c6b02cdfd") 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 ndarray, ndim 2, dtype family float, shape (2, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape 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.
|
| discrete_cmap | Not yet run unverified (harvested, no recorded run) |
YeongHyeon/MemAE/source/tf_process.py code served (permissive licence) · get_code("d6efb7ecae19cdd8") How it ranno invocation recorded. |
Of 9 samples lifted from this paper's linked repositories, 9 carry a function identity and 0 do not. Of the 9 distinct functions with an identity, 4 are also present in other papers whose code we hold (3 with at least one paper dated earlier, 1 the same month, 2 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 |
|---|---|---|---|
| str2bool | 82 other papers 9 dated earlier, 4 the same month, 69 later |
1510.03055 (2015-10) A Diversity-Promoting Objective Function for Neural Conversation Models |
1703.06490 (2017-03) Generating Multi-label Discrete Patient Records using Generative Adversarial Networks 1710.10467 (2017-10) Generalized End-to-End Loss for Speaker Verification and 79 more not named here |
| dat2canvas | 3 other papers 3 dated earlier |
1703.05921 (2017-03) Unsupervised Anomaly Detection with Generative Adversarial Networks to Guide Marker Discovery |
1805.06725 (2018-05) GANomaly: Semi-Supervised Anomaly Detection via Adversarial Training 1901.08954 (2019-01) Skip-GANomaly: Skip Connected and Adversarially Trained Encoder-Decoder Anomaly Detection |
| gray2rgb | 3 other papers 3 dated earlier |
1703.05921 (2017-03) Unsupervised Anomaly Detection with Generative Adversarial Networks to Guide Marker Discovery |
1805.06725 (2018-05) GANomaly: Semi-Supervised Anomaly Detection via Adversarial Training 1901.08954 (2019-01) Skip-GANomaly: Skip Connected and Adversarially Trained Encoder-Decoder Anomaly Detection |
| hard_shrink_relu | 2 other papers 2 later |
136730727 (2022 (year only)) Self-Supervised Sparse Representation for Video Anomaly Detection |
2307.00755 (2023-07) Graph-level Anomaly Detection via Hierarchical Memory 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.
Deep autoencoder has been extensively used for anomaly detection. Training on the normal data, the autoencoder is expected to produce higher reconstruction error for the abnormal inputs than the normal ones, which is adopted as a criterion for identifying anomalies. However, this assumption does not always hold in practice. It has been observed that sometimes the autoencoder "generalizes" so well that it can also reconstruct anomalies well, leading to the miss detection of anomalies. To mitigate this drawback for autoencoder based anomaly detector, we propose to augment the autoencoder with a memory module and develop an improved autoencoder called memory-augmented autoencoder, i.e. MemAE. Given an input, MemAE firstly obtains the encoding from the encoder and then uses it as a query to retrieve the most relevant memory items for reconstruction. At the training stage, the memory contents are updated and are encouraged to represent the prototypical elements of the normal data. At the test stage, the learned memory will be fixed, and the reconstruction is obtained from a few selected memory records of the normal data. The reconstruction will thus tend to be close to a normal sample. Thus the reconstructed errors on anomalies will be strengthened for anomaly detection. MemAE is free of assumptions on the data type and thus general to be applied to different tasks. Experiments on various datasets prove the excellent generalization and high effectiveness of the proposed MemAE.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("1904.02639")
get_code_for_paper("1904.02639")
have("1904.02639")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/1904.02639.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/1904.02639)
Connect an agent — have() is free.