Papers › Hierarchical Integration Diffusion Model for Realistic Image Deblurring

Hierarchical Integration Diffusion Model for Realistic Image Deblurring

22 May 2023NeurIPS 2023 11arXiv:2305.12966archive 2025-07-28

Zheng Chen, Yulun Zhang, Ding Liu, Bin Xia, Jinjin Gu, Linghe Kong, Xin Yuan

Diffusion models (DMs) have recently been introduced in image deblurring and exhibited promising performance, particularly in terms of details reconstruction. However, the diffusion model requires a large number of inference iterations to recover the clean image from pure Gaussian noise, which consumes massive computational resources. Moreover, the distribution synthesized by the diffusion model is often misaligned with the target results, leading to restrictions in distortion-based metrics. To address the above issues, we propose the Hierarchical Integration Diffusion Model (HI-Diff), for realistic image deblurring. Specifically, we perform the DM in a highly compacted latent space to generate the prior feature for the deblurring process. The deblurring process is implemented by a regression-based method to obtain better distortion accuracy. Meanwhile, the highly compact latent space ensures the efficiency of the DM. Furthermore, we design the hierarchical integration module to fuse the prior into the regression-based model from multiple scales, enabling better generalization in complex blurry scenarios. Comprehensive experiments on synthetic and real-world blur datasets demonstrate that our HI-Diff outperforms state-of-the-art methods. Code and trained models are available at https://github.com/zhengchen1999/HI-Diff.

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

By repository: official repository: 13 samples from 1 repository, 11 ran (6 with no instrument failure; 5 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. 3 of the 11 samples that ran have no recorded date.

zhengchen1999/hi-diff officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 13 samples, 11 ran (5 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

13 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 2 violated, 4 with no contract checked; 5 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.

2ran · violated contract
2ran · our draft was wrong
3ran; the contract check could not run
4ran
2unverified

Licence: 5 of the 13 samples are pointer only, meaning Syntology does not serve that copy's text. For 5 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 zhengchen1999/hi-diff. “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.

zhengchen1999/hi-diff official repository 13 samples, 11 ran (5 instrument-failed) · 2 unverified
augment in 36 papers hi_diff/utils/transforms.py ran Apache-2.0 (permissive) · 7f124cd33fb750ee · report fixture: signature imgs:list/1/ndarray, hflip:bool/0/bool, rotation:bool/0/bool, flows:list/1/ndarray, return_status:bool/0/bool · returned tuple · level recorded 2026-09-25
compute_psnr in 30 papers evaluate_realblur.py ran Apache-2.0 (permissive) here; the stored copy is pointer only · 91fa50e293bf2fde · report fixture: signature image_true:ndarray/2/float, image_test:ndarray/2/float, image_mask:ndarray/2/float, data_range:float/0/float · returned float64 · level recorded 2026-09-24
default in 430 papers hi_diff/utils/beta_schedule.py ran · violated contract Apache-2.0 (permissive) · fbf9ec7be545688e · report fixture: signature val:NoneType/0/?, d:str/0/str · returned str · level recorded 2026-09-22
dict2str in 30 papers hi_diff/utils/options.py ran · our draft was wrong Apache-2.0 (permissive) · 769e9c110eeb4a0d · report fixture: signature opt:dict/0/?, indent_level:int/0/int · returned str · level recorded 2026-09-24
exists in 528 papers
census: 5 implementations from 103 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 1, kind int, dtype int64
hi_diff/utils/beta_schedule.py ran · violated contract Apache-2.0 (permissive) · 608e364a9d2376a3 · report fixture: signature x:Tensor/1/int · returned bool · level recorded, date not recorded
get_position_from_periods in 59 papers hi_diff/utils/lr_scheduler.py ran; the contract check could not run (RAISES) fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · cd569444547de84f · report fixture: signature iteration:int/0/int, cumulative_period:list/1/int · returned int · level recorded 2026-09-24
make_beta_schedule in 48 papers hi_diff/utils/beta_schedule.py ran Apache-2.0 (permissive) · 78feb2965623416b · report fixture: signature schedule:str/0/str, n_timestep:int/0/int, linear_start:float/0/float, linear_end:float/0/float, cosine_s:float/0/float · returned ndarray · level recorded 2026-09-24
mod_crop hi_diff/utils/transforms.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 223d0788b0725dfb · report fixture: signature img:ndarray/3/int, scale:int/0/int · returned ndarray · level recorded 2026-09-25
paired_random_crop hi_diff/utils/transforms.py ran Apache-2.0 (permissive) · 64cd160c586b1bef · report fixture: signature img_gts:Tensor/4/float, img_lqs:Tensor/4/float, gt_patch_size:int/0/int, scale:int/0/int, gt_path:NoneType/0/? · returned tuple · level recorded 2026-09-25
to_3d in 66 papers
census: 3 implementations from 20 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 4, kind float, dtype float32
hi_diff/archs/Transformer_arch.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 82a15cc1e46f7e4d · report fixture: signature x:Tensor/4/float · returned Tensor · level recorded, date not recorded
to_4d in 69 papers hi_diff/archs/Transformer_arch.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant Apache-2.0 (permissive) here; the stored copy is pointer only · b20f2a5df739a59e · report fixture: signature x:Tensor/3/float, h:int/0/int, w:int/0/int · returned Tensor · level recorded, date not recorded
compute_ssim in 15 papers evaluate_realblur.py unverified Apache-2.0 (permissive) · 64c776bb050ba1e2 · report
image_align in 8 papers evaluate_realblur.py unverified Apache-2.0 (permissive) here; the stored copy is pointer only · 5aad1c1e328fd4ec · report

Tasks

DeblurringImage Deblurringmodelregression

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Diffusion

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