5 of 5 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 3 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/1808.07535.json · badge: /api/ran/1808.07535.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 |
|---|---|---|
| xcyan/neurips18_hierchical_image_manipulation | community (classifier label) classifier basis not recorded on the link |
5 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| compute_gan_loss | Ran ran on a synthesized input |
xcyan/neurips18_hierchical_image_manipulation/models/losses.py code served (permissive licence) · get_code("e874376a7e1429d4") 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.
|
| conv3x3 | Ran ran; our contract draft was wrong, not the code |
xcyan/neurips18_hierchical_image_manipulation/models/layer_util.py code served (permissive licence) · get_code("0e722c9ff0920473") 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 Conv2d. 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.
|
| conv3x3 | Ran ran on a synthesized input |
xcyan/neurips18_hierchical_image_manipulation/models/Discriminator_NET.py code served (permissive licence) · get_code("8ab5f104f9317376") 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 Conv2d. 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.
|
| get_norm_layer | Ran ran; our contract draft was wrong, not the code |
xcyan/neurips18_hierchical_image_manipulation/models/layer_util.py code served (permissive licence) · get_code("29bb0088c8c38ae4") 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 partial. 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.
|
| lr_control | Ran ran on a synthesized input |
xcyan/neurips18_hierchical_image_manipulation/models/Discriminator_NET.py code served (permissive licence) · get_code("4d39f0d4ec405775") 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.
|
Of 5 samples lifted from this paper's linked repositories, 5 carry a function identity and 0 do not. Of the 5 distinct functions with an identity, 2 are also present in other papers whose code we hold (1 with at least one paper dated earlier, 0 the same month, 2 later) and 3 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 |
|---|---|---|---|
| get_norm_layer | 8 other papers 2 dated earlier, 6 later |
1711.11585 (2017-11) High-Resolution Image Synthesis and Semantic Manipulation with Conditional GANs |
1805.04487 (2018-05) Non-Stationary Texture Synthesis by Adversarial Expansion 2003.05863 (2020-03) Towards Photo-Realistic Virtual Try-On by Adaptively Generating$\leftrightarrow$Preserving Image Content and 5 more not named here |
| conv3x3 | 6 other papers 6 later |
1906.05856 (2019-06) Detecting Photoshopped Faces by Scripting Photoshop |
1908.06702 (2019-08) Floor-SP: Inverse CAD for Floorplans by Sequential Room-wise Shortest Path 2003.05970 (2020-03) LiDAR guided Small obstacle Segmentation and 3 more not named here |
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.
Understanding, reasoning, and manipulating semantic concepts of images have been a fundamental research problem for decades. Previous work mainly focused on direct manipulation on natural image manifold through color strokes, key-points, textures, and holes-to-fill. In this work, we present a novel hierarchical framework for semantic image manipulation. Key to our hierarchical framework is that we employ a structured semantic layout as our intermediate representation for manipulation. Initialized with coarse-level bounding boxes, our structure generator first creates pixel-wise semantic layout capturing the object shape, object-object interactions, and object-scene relations. Then our image generator fills in the pixel-level textures guided by the semantic layout. Such framework allows a user to manipulate images at object-level by adding, removing, and moving one bounding box at a time. Experimental evaluations demonstrate the advantages of the hierarchical manipulation framework over existing image generation and context hole-filing models, both qualitatively and quantitatively. Benefits of the hierarchical framework are further demonstrated in applications such as semantic object manipulation, interactive image editing, and data-driven image manipulation.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("1808.07535")
get_code_for_paper("1808.07535")
have("1808.07535")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/1808.07535.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/1808.07535)
Connect an agent — have() is free.