3 of 3 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 0 have no contract verdict; 3 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/2007.07843.json · badge: /api/ran/2007.07843.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 |
|---|---|---|
| yiweilu3/Few-shot-Scene-adaptive-Anomaly-Detection | canonical (classifier label) classifier basis: census |
3 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| createEpochData | Ran ran; our contract draft was wrong, not the code |
yiweilu3/Few-shot-Scene-adaptive-Anomaly-Detection/utils.py code served (permissive licence) · get_code("82124ed781e43e8b") 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 4, 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.
|
| double_conv | Ran ran; our contract draft was wrong, not the code |
yiweilu3/Few-shot-Scene-adaptive-Anomaly-Detection/rGAN.py pointer only (licence: MIT); the stored copy get_code serves, from EvgenyDyshlyuk/Oil_Seep_Detection, is pointer only (licence: NONE) · get_code("3e9ea4498e4b8a8d") 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 EvgenyDyshlyuk/Oil_Seep_Detection, 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. |
| generate_k_shot_frames | Ran ran; our contract draft was wrong, not the code |
yiweilu3/Few-shot-Scene-adaptive-Anomaly-Detection/utils.py code served (permissive licence) · get_code("9d88c63e86f77b0b") 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.
|
Of 3 samples lifted from this paper's linked repositories, 3 carry a function identity and 0 do not. Of the 3 distinct functions with an identity, 3 are also present in other papers whose code we hold (1 with at least one paper dated earlier, 0 the same month, 3 later) and 0 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 |
|---|---|---|---|
| double_conv | 4 other papers 2 dated earlier, 2 later |
1505.04597 (2015-05) U-Net: Convolutional Networks for Biomedical Image Segmentation |
1912.05074 (2019-12) UNet++: Redesigning Skip Connections to Exploit Multiscale Features in Image Segmentation 2404.06737 (2024-04) Disguised Copyright Infringement of Latent Diffusion Models and 1 more not named here |
| createEpochData | 1 other paper 1 later |
2404.06737 (2024-04) Disguised Copyright Infringement of Latent Diffusion Models |
|
| generate_k_shot_frames | 1 other paper 1 later |
2404.06737 (2024-04) Disguised Copyright Infringement of Latent Diffusion Models |
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.
We address the problem of anomaly detection in videos. The goal is to identify unusual behaviours automatically by learning exclusively from normal videos. Most existing approaches are usually data-hungry and have limited generalization abilities. They usually need to be trained on a large number of videos from a target scene to achieve good results in that scene. In this paper, we propose a novel few-shot scene-adaptive anomaly detection problem to address the limitations of previous approaches. Our goal is to learn to detect anomalies in a previously unseen scene with only a few frames. A reliable solution for this new problem will have huge potential in real-world applications since it is expensive to collect a massive amount of data for each target scene. We propose a meta-learning based approach for solving this new problem; extensive experimental results demonstrate the effectiveness of our proposed method.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2007.07843")
get_code_for_paper("2007.07843")
have("2007.07843")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2007.07843.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2007.07843)
Connect an agent — have() is free.