Papers › Specifying Object Attributes and Relations in Interactive Scene Generation

Specifying Object Attributes and Relations in Interactive Scene Generation

11 Sep 2019ICCV 2019 10arXiv:1909.05379archive 2025-07-28

Oron Ashual, Lior Wolf

We introduce a method for the generation of images from an input scene graph. The method separates between a layout embedding and an appearance embedding. The dual embedding leads to generated images that better match the scene graph, have higher visual quality, and support more complex scene graphs. In addition, the embedding scheme supports multiple and diverse output images per scene graph, which can be further controlled by the user. We demonstrate two modes of per-object control: (i) importing elements from other images, and (ii) navigation in the object space, by selecting an appearance archetype. Our code is publicly available at https://www.github.com/ashual/scene_generation

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 16 code samples harvested from 1 repository linked to this paper: 15 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 0 honoured, 0 violated, 12 with no contract checked; 3 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 16 samples from 1 repository, 15 ran (12 with no instrument failure; 3 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-25 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

ashual/scene_generation officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 16 samples, 15 ran (3 instrument-failed) · 1 unverified report
Touyuki/Cover_generation mentioned on GitHubpytorchSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

16 samples harvested: 15 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 0 honoured, 0 violated, 12 with no contract checked; 3 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · our draft was wrong
1ran; the contract check could not run
12ran
1unverified

Licence: 3 of the 16 samples are pointer only, meaning Syntology does not serve that copy's text. For 3 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from ashual/scene_generation. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

ashual/scene_generation official repository 16 samples, 15 ran (3 instrument-failed) · 1 unverified
bce_loss in 22 papers scene_generation/losses.py ran fingerprinted Apache-2.0 (permissive) · ae92b5ed5c527664 · report fixture: signature input:Tensor/1/float, target:Tensor/1/float · returned Tensor · level recorded 2026-09-25
build_cnn in 7 papers scene_generation/layers.py ran Apache-2.0 (permissive) · bc8cbd075263a084 · report fixture: signature arch:list/1/str, normalization:str/0/str, activation:str/0/str, padding:str/0/str, pooling:str/0/str, init:str/0/str · returned tuple · level recorded 2026-09-25
crop_bbox scene_generation/bilinear.py ran · our draft was wrong Apache-2.0 (permissive) here; the stored copy is pointer only · c53b4e16e12f033f · report fixture: signature feats:Tensor/4/float, bbox:Tensor/2/float, HH:int/0/int, WW:int/0/int, backend:str/0/str · returned Tensor · level recorded 2026-09-26
crop_bbox_batch scene_generation/bilinear.py ran; the contract check could not run (RAISES) Apache-2.0 (permissive) here; the stored copy is pointer only · 2fa113c634c92368 · report fixture: signature feats:Tensor/4/float, bbox:Tensor/2/float, bbox_to_feats:Tensor/1/int, HH:int/0/int, WW:int/0/int · returned Tensor · level recorded 2026-09-26
crop_bbox_batch_cudnn scene_generation/bilinear.py ran · our draft was wrong Apache-2.0 (permissive) here; the stored copy is pointer only · 08e9481d0c0ca383 · report fixture: signature feats:Tensor/4/float, bbox:Tensor/2/float, bbox_to_feats:Tensor/1/int, HH:int/0/int, WW:int/0/int · returned Tensor · level recorded 2026-09-26
float_tuple scene_generation/utils.py ran Apache-2.0 (permissive) · 5e3086197586c014 · report fixture: signature s:str/0/str · returned tuple · level recorded 2026-09-25
gan_g_loss scene_generation/losses.py ran fingerprinted Apache-2.0 (permissive) · 712a7831efa220b1 · report fixture: signature scores_fake:Tensor/1/float · returned Tensor · level recorded 2026-09-25
get_activation in 218 papers scene_generation/layers.py ran Apache-2.0 (permissive) · fa5f35b7c26dbe12 · report fixture: signature name:str/0/str · returned LeakyReLU · level recorded 2026-09-25
get_gan_losses scene_generation/losses.py ran Apache-2.0 (permissive) · b8a0bea29f303010 · report fixture: signature gan_type:str/0/str · returned tuple · level recorded 2026-09-25
get_normalization_2d scene_generation/layers.py ran Apache-2.0 (permissive) · 481b0a0e44bbea29 · report fixture: signature channels:int/0/int, normalization:str/0/str · returned BatchNorm2d · level recorded 2026-09-25
int_tuple in 6 papers scene_generation/utils.py ran Apache-2.0 (permissive) · c7a0b110ef7c5e03 · report fixture: signature s:str/0/str · returned tuple · level recorded 2026-09-25
intersection in 24 papers scene_generation/metrics.py ran fingerprinted Apache-2.0 (permissive) · 6d89e132179f2fbd · report fixture: signature bbox_pred:Tensor/2/float, bbox_gt:Tensor/2/float · returned Tensor · level recorded 2026-09-25
jaccard in 33 papers scene_generation/metrics.py ran fingerprinted Apache-2.0 (permissive) · 6c551c38bca87602 · report fixture: signature bbox_pred:Tensor/2/float, bbox_gt:Tensor/2/float · returned tuple · level recorded 2026-09-25
masks_to_layout scene_generation/layout.py ran Apache-2.0 (permissive) · 16e2481c885af916 · report fixture: signature vecs:Tensor/2/float, boxes:Tensor/2/float, masks:Tensor/3/float, obj_to_img:Tensor/1/int, H:int/0/int, W:int/0/int, pooling:str/0/str, test_mode:bool/0/bool · returned Tensor · level recorded 2026-09-25
str_tuple scene_generation/utils.py ran fingerprinted Apache-2.0 (permissive) · ec5493a698745a69 · report fixture: signature s:str/0/str · returned tuple · level recorded 2026-09-25
boxes_to_layout scene_generation/layout.py unverified Apache-2.0 (permissive) · b9013d4eb8886059 · report

Tasks

Layout-to-Image GenerationObjectScene Generation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Layout-to-Image Generation COCO-Stuff 128x128 SOARISG FID 59.5 #5 of 5 Archive leaderboard report
Layout-to-Image Generation COCO-Stuff 128x128 SOARISG Inception Score 12.5 #5 of 5 Archive leaderboard report
Layout-to-Image Generation COCO-Stuff 128x128 SOARISG SceneFID 33.46 #5 of 5 Archive leaderboard report
Layout-to-Image Generation COCO-Stuff 64x64 SOARISG FID 48.7 #4 of 5 Archive leaderboard report
Layout-to-Image Generation COCO-Stuff 64x64 SOARISG Inception Score 10.3 #4 of 5 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections