Papers › Hybrid Fourier Score Distillation for Efficient One Image to 3D Object Generation

Hybrid Fourier Score Distillation for Efficient One Image to 3D Object Generation

31 May 2024arXiv:2405.20669archive 2025-07-28

Shuzhou Yang, Yu Wang, Haijie Li, Jiarui Meng, Yanmin Wu, Xiandong Meng, Jian Zhang

Single image-to-3D generation is pivotal for crafting controllable 3D assets. Given its under-constrained nature, we attempt to leverage 3D geometric priors from a novel view diffusion model and 2D appearance priors from an image generation model to guide the optimization process. We note that there is a disparity between the generation priors of these two diffusion models, leading to their different appearance outputs. Specifically, image generation models tend to deliver more detailed visuals, whereas novel view models produce consistent yet over-smooth results across different views. Directly combining them leads to suboptimal effects due to their appearance conflicts. Hence, we propose a 2D-3D hybrid Fourier Score Distillation objective function, hy-FSD. It optimizes 3D Gaussians using 3D priors in spatial domain to ensure geometric consistency, while exploiting 2D priors in the frequency domain through Fourier transform for better visual quality. hy-FSD can be integrated into existing 3D generation methods and produce significant performance gains. With this technique, we further develop an image-to-3D generation pipeline to create high-quality 3D objects within one minute, named Fourier123. Extensive experiments demonstrate that Fourier123 excels in efficient generation with rapid convergence speed and visually-friendly generation results.

PaperPDFCodeCode 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 10 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: 4 honoured, 0 violated, 4 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 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: 10 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.

Ysz2022/Fourier123 officialmentioned on GitHubpytorchMITSyntology: 10 samples, 10 ran (2 instrument-failed) · 0 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

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

4ran · honoured contract
1ran · our draft was wrong
1ran; the contract check could not run
4ran

Licence: 2 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 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 Ysz2022/Fourier123. “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.

Ysz2022/Fourier123 official repository 10 samples, 10 ran (2 instrument-failed) · 0 unverified
dot in 68 papers cam_utils.py ran · honoured contract fingerprinted MIT (permissive) · e35aafbf0069edb6 · report fixture: signature x:Tensor/2/float, y:Tensor/2/float · returned Tensor · level recorded 2026-09-25
get_expon_lr_func in 14 papers gs_renderer.py ran MIT (permissive) · 6d2c15014d993b0e · report fixture: signature lr_init:float/0/float, lr_final:float/0/float, lr_delay_steps:int/0/int, lr_delay_mult:float/0/float, max_steps:int/0/int · returned function · level recorded 2026-09-24
grid_distortion core/utils.py ran fingerprinted MIT (permissive) here; the stored copy is pointer only · 807e057029e98578 · report fixture: signature images:Tensor/4/float, strength:float/0/float · returned Tensor · level recorded 2026-09-24
inverse_sigmoid in 80 papers
census: 9 implementations from 14 papers, 5 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 2, kind float, dtype float32
gs_renderer.py ran · honoured contract fingerprinted MIT (permissive) · b488da571728b636 · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22
length in 22 papers cam_utils.py ran · honoured contract fingerprinted MIT (permissive) · 43cdc168f88caf9b · report fixture: signature x:Tensor/2/float, eps:float/0/float · returned Tensor · level recorded 2026-09-25
safe_normalize in 19 papers cam_utils.py ran · honoured contract fingerprinted MIT (permissive) · 8a8484ccf552d87f · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-25
scatter_add_nd grid_put.py ran MIT (permissive) · f677a14137b6170d · report fixture: signature input:Tensor/4/float, indices:Tensor/2/int, values:Tensor/2/float · returned Tensor · level recorded 2026-09-24
scatter_add_nd_with_count grid_put.py ran MIT (permissive) · 0a4a0c5951d1f0bf · report fixture: signature input:Tensor/3/float, count:Tensor/3/float, indices:Tensor/2/int, values:Tensor/2/float, weights:Tensor/2/float · returned tuple · level recorded 2026-09-24
stride_from_shape grid_put.py ran · our draft was wrong MIT (permissive) · be46ebcf4f59432b · report fixture: signature shape:tuple/1/int · returned list · level recorded 2026-09-24
strip_lowerdiag in 9 papers gs_renderer.py ran; the contract check could not run (RAISES) MIT (permissive) here; the stored copy is pointer only · cd789cab1b072db4 · report fixture: returned Tensor · level recorded 2026-09-22

Tasks

3D GenerationImage GenerationImage to 3D

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

DiffusionSPEED

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