Papers › GRAF: Generative Radiance Fields for 3D-Aware Image Synthesis

GRAF: Generative Radiance Fields for 3D-Aware Image Synthesis

5 Jul 2020NeurIPS 2020 12arXiv:2007.02442archive 2025-07-28

Katja Schwarz, Yiyi Liao, Michael Niemeyer, Andreas Geiger

While 2D generative adversarial networks have enabled high-resolution image synthesis, they largely lack an understanding of the 3D world and the image formation process. Thus, they do not provide precise control over camera viewpoint or object pose. To address this problem, several recent approaches leverage intermediate voxel-based representations in combination with differentiable rendering. However, existing methods either produce low image resolution or fall short in disentangling camera and scene properties, e.g., the object identity may vary with the viewpoint. In this paper, we propose a generative model for radiance fields which have recently proven successful for novel view synthesis of a single scene. In contrast to voxel-based representations, radiance fields are not confined to a coarse discretization of the 3D space, yet allow for disentangling camera and scene properties while degrading gracefully in the presence of reconstruction ambiguity. By introducing a multi-scale patch-based discriminator, we demonstrate synthesis of high-resolution images while training our model from unposed 2D images alone. We systematically analyze our approach on several challenging synthetic and real-world datasets. Our experiments reveal that radiance fields are a powerful representation for generative image synthesis, leading to 3D consistent models that render with high fidelity.

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 12 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 1 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 12 samples from 1 repository, 10 ran (8 with no instrument failure; 2 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-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

autonomousvision/graf officialmentioned in paperpytorchMITSyntology: 12 samples, 10 ran (2 instrument-failed) · 2 unverified 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

12 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 1 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 2 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.

1ran · honoured contract
1ran · violated contract
2ran; the contract check could not run
6ran
2unverified

Licence: 1 of the 12 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, 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 autonomousvision/graf. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

autonomousvision/graf official repository 12 samples, 10 ran (2 instrument-failed) · 2 unverified
color_depth_map graf/utils.py ran MIT (permissive) · 71ec2a9308fa61f3 · report fixture: signature depths:ndarray/2/float, scale:NoneType/0/? · returned ndarray · level recorded 2026-09-25
count_trainable_parameters in 21 papers graf/utils.py ran MIT (permissive) · 7de1ceff1fdc469d · report fixture: signature model:callable/0/? · returned int64 · level recorded 2026-09-25
get_nsamples graf/utils.py ran MIT (permissive) · 4cbceee1eebaf6d4 · report fixture: signature data_loader:list/1/Tensor, N:int/0/int · returned Tensor · level recorded 2026-09-25
load_blender_data in 7 papers submodules/nerf_pytorch/load_blender.py ran MIT (permissive) · 83ed66ae61279dbc · report fixture: signature basedir:str/0/str, half_res:bool/0/bool, testskip:int/0/int · returned tuple · level recorded 2026-09-25
load_dv_data submodules/nerf_pytorch/load_deepvoxels.py ran MIT (permissive) · e69746042397f344 · report fixture: signature scene:str/0/str, basedir:str/0/str, testskip:int/0/int · returned tuple · level recorded 2026-09-25
normalize in 638 papers
census: 70 implementations from 82 papers, 51 distinct outputs across 11 buckets, one shared input per bucket this sample: bucket 3 of 11, arg 1: rank 1, kind float, dtype float64
submodules/nerf_pytorch/load_llff.py ran · violated contract fingerprinted MIT (permissive) · 1d6f8390d799f055 · report fixture: signature x:ndarray/1/float · returned ndarray · level recorded 2026-09-22
pose_spherical in 17 papers submodules/nerf_pytorch/load_blender.py ran · honoured contract MIT (permissive) here; the stored copy is pointer only · 8313c1fb69b28c8e · report fixture: signature theta:float/0/float, phi:float/0/float, radius:float/0/float · returned Tensor · level recorded 2026-09-24
ptstocam in 11 papers submodules/nerf_pytorch/load_llff.py ran; the contract check could not run (RAISES) MIT (permissive) · 36f5de7a0aae4a9b · report fixture: signature pts:ndarray/2/float, c2w:ndarray/2/float · returned ndarray · level recorded 2026-09-25
update_config in 54 papers graf/config.py ran MIT (permissive) · 559fa10dfa807ea5 · report fixture: signature config:dict/0/?, unknown:list/1/str · returned dict · level recorded 2026-09-25
viewmatrix in 18 papers submodules/nerf_pytorch/load_llff.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) · aa52acee18f54d38 · report fixture: signature z:ndarray/1/float, up:ndarray/1/float, pos:ndarray/1/float · returned ndarray · level recorded 2026-09-22
get_data in 223 papers graf/config.py unverified MIT (permissive) · 856b87aabeff2342 · report
get_render_poses graf/config.py unverified MIT (permissive) · 677c56fac6ae59a2 · report

Tasks

3D-Aware Image SynthesisImage GenerationNovel View SynthesisScene Generation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Scene Generation AVD GRAF FID 62.59 #2 of 3 Archive leaderboard report
Scene Generation AVD GRAF SwAV-FID 6.95 #2 of 3 Archive leaderboard report
Scene Generation Replica GRAF FID 65.37 #2 of 3 Archive leaderboard report
Scene Generation Replica GRAF SwAV-FID 5.76 #2 of 3 Archive leaderboard report
Scene Generation VizDoom GRAF FID 47.50 #2 of 3 Archive leaderboard report
Scene Generation VizDoom GRAF SwAV-FID 5.44 #2 of 3 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