Papers › Reconciling Stochastic and Deterministic Strategies for Zero-shot Image Restoration...

Reconciling Stochastic and Deterministic Strategies for Zero-shot Image Restoration using Diffusion Model in Dual

3 Mar 2025CVPR 2025 1arXiv:2503.01288archive 2025-07-28

Chong Wang, Lanqing Guo, Zixuan Fu, Siyuan Yang, Hao Cheng, Alex C. Kot, Bihan Wen

Plug-and-play (PnP) methods offer an iterative strategy for solving image restoration (IR) problems in a zero-shot manner, using a learned discriminative denoiser as the implicit prior. More recently, a sampling-based variant of this approach, which utilizes a pre-trained generative diffusion model, has gained great popularity for solving IR problems through stochastic sampling. The IR results using PnP with a pre-trained diffusion model demonstrate distinct advantages compared to those using discriminative denoisers, i.e. improved perceptual quality while sacrificing the data fidelity. The unsatisfactory results are due to the lack of integration of these strategies in the IR tasks. In this work, we propose a novel zero-shot IR scheme, dubbed Reconciling Diffusion Model in Dual (RDMD), which leverages only a single pre-trained diffusion model to construct two complementary regularizers. Specifically, the diffusion model in RDMD will iteratively perform deterministic denoising and stochastic sampling, aiming to achieve high-fidelity image restoration with appealing perceptual quality. RDMD also allows users to customize the distortion-perception tradeoff with a single hyperparameter, enhancing the adaptability of the restoration process in different practical scenarios. Extensive experiments on several IR tasks demonstrate that our proposed method could achieve superior results compared to existing approaches on both the FFHQ and ImageNet datasets.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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

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

chongwang1024/rdmd officialmentioned in paperpytorchSyntology: 7 samples, 1 ran (0 instrument-failed) · 6 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

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

1ran
6unverified

Licence: 7 of the 7 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from chongwang1024/rdmd. “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.

chongwang1024/rdmd official repository 7 samples, 1 ran (0 instrument-failed) · 6 unverified
QKVAttention in 25 papers guided_diffusion/unet_traj.py ran no licence file found · pointer only · 73cd1ec9fdcb41a8 · report fixture: signature qkv:Tensor/3/float · returned Tensor · level recorded 2026-09-24
AttentionBlock in 69 papers guided_diffusion/unet_traj.py unverified no licence file found · pointer only · 3107ad901b8a997d · report
AttentionBlock_Crossframe guided_diffusion/unet_traj.py unverified no licence file found · pointer only · 3b3056259c2105b9 · report
TimestepEmbedSequential in 28 papers guided_diffusion/unet_traj.py unverified no licence file found · pointer only · 8b58481b16d2016f · report
UNetModel in 23 papers guided_diffusion/unet_traj.py unverified no licence file found · pointer only · 954b783eddbd4118 · report
my_QKVAttentionLegacy guided_diffusion/unet_traj.py unverified no licence file found · pointer only · 7759e76e64ca3b8a · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Reconciling Diffusion Model in Dual (RDMD) (graph method: Reconciling Diffusion Model in Dual (RDMD)). 23 bricks; individually on a fixture: 10 ran (of which 5 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 4 where Syntology's instrument failed) · 13 unverified. The assembly has not been run end-to-end.

  1. UNetModel entry · level 0 · unverified · 954b783eddbd4118
  2. AttentionBlock model · level 0 · unverified · 3107ad901b8a997d
  3. AttentionBlock_Crossframe model · level 0 · unverified · 3b3056259c2105b9
  4. Downsample helper · level 1 · ran · 8c5676227adb2492
  5. ResBlock model · level 0 · unverified · be904e793da7ac54
  6. TimestepEmbedSequential model · level 0 · unverified · 8b58481b16d2016f
  7. Upsample helper · level 1 · ran · 6998a3677700ee6c
  8. conv_nd helper · level 0 · unverified · fe4eb545bbb728e0
  9. convert_module_to_f16 helper · level 0 · unverified · ac07425399caf784
  10. convert_module_to_f32 helper · level 0 · unverified · b283a8ab305dc007
  11. linear helper · level 1 · ran · our draft was wrong · 0e30585f04efffbe
  12. normalization helper · level 1 · ran · our draft was wrong · 5b31715a9b105926
  13. timestep_embedding helper · level 1 · ran · our draft was wrong · b0aa348a2f95ef0f
  14. zero_module helper · level 1 · ran · our draft was wrong · 129b804760b3115f
  15. QKVAttention model · level 1 · ran · 73cd1ec9fdcb41a8
  16. QKVAttentionLegacy helper · level 1 · ran · c21412aa89ed28a7
  17. checkpoint helper · level 0 · unverified · fb150e1f7e53041e
  18. my_QKVAttentionLegacy helper · level 0 · unverified · 7759e76e64ca3b8a
  19. avg_pool_nd helper · level 0 · unverified · ecd0fc28815b65ae
  20. TimestepBlock helper · level 0 · unverified · 40fb9bc947892adc
  21. GroupNorm32 helper · level 1 · ran · 426c2385fa431d9a
  22. count_flops_attn helper · level 0 · unverified · 0c49097ae6ff37ef
  23. CheckpointFunction helper · level 1 · ran · 27faeacc0d8cf344

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2503.01288") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

DenoisingImage Restoration

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

DiffusionPnP

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