Papers › Removing Diffraction Image Artifacts in Under-Display Camera via Dynamic Skip...

Removing Diffraction Image Artifacts in Under-Display Camera via Dynamic Skip Connection Network

19 Apr 2021CVPR 2021 1arXiv:2104.09556archive 2025-07-28

Ruicheng Feng, Chongyi Li, Huaijin Chen, Shuai Li, Chen Change Loy, Jinwei Gu

Recent development of Under-Display Camera (UDC) systems provides a true bezel-less and notch-free viewing experience on smartphones (and TV, laptops, tablets), while allowing images to be captured from the selfie camera embedded underneath. In a typical UDC system, the microstructure of the semi-transparent organic light-emitting diode (OLED) pixel array attenuates and diffracts the incident light on the camera, resulting in significant image quality degradation. Oftentimes, noise, flare, haze, and blur can be observed in UDC images. In this work, we aim to analyze and tackle the aforementioned degradation problems. We define a physics-based image formation model to better understand the degradation. In addition, we utilize one of the world's first commodity UDC smartphone prototypes to measure the real-world Point Spread Function (PSF) of the UDC system, and provide a model-based data synthesis pipeline to generate realistically degraded images. We specially design a new domain knowledge-enabled Dynamic Skip Connection Network (DISCNet) to restore the UDC images. We demonstrate the effectiveness of our method through extensive experiments on both synthetic and real UDC data. Our physics-based image formation model and proposed DISCNet can provide foundations for further exploration in UDC image restoration, and even for general diffraction artifact removal in a broader sense.

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

By repository: official repository: 11 samples from 1 repository, 7 ran (2 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

jnjaby/DISCNet officialmentioned on GitHubpytorchSyntology: 11 samples, 7 ran (5 instrument-failed) · 4 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

11 samples harvested: 7 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 0 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 4 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 · honoured contract
5ran · our draft was wrong
1ran
4unverified

Licence: 11 of the 11 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 jnjaby/DISCNet. “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.

jnjaby/DISCNet official repository 11 samples, 7 ran (5 instrument-failed) · 4 unverified
ResBlock in 127 papers
census: 6 implementations from 5 papers, 6 distinct outputs across 2 buckets, one shared input per bucket
basicsr/models/archs/discnet_arch.py ran · metamorphic tier: deterministic no licence file found · pointer only · 6b2f8c2ebe2461b0 · report fixture: returned ResBlock · level recorded 2026-09-22
act in 30 papers basicsr/models/archs/discnet_arch.py ran · our draft was wrong no licence file found · pointer only · 15d829a065897df0 · report fixture: signature act_type:str/0/str, inplace:bool/0/bool, neg_slope:float/0/float, n_prelu:int/0/int · returned ReLU · level recorded 2026-09-22
conv_block in 95 papers basicsr/models/archs/discnet_arch.py ran · our draft was wrong no licence file found · pointer only · 2088da310e2c1c79 · report fixture: signature in_nc:int/0/int, out_nc:int/0/int, kernel_size:int/0/int, stride:int/0/int, dilation:int/0/int, groups:int/0/int, bias:bool/0/bool, pad_type:str/0/str, norm_type:str/0/str, act_type:str/0/str, mode:str/0/str · returned Sequential · level recorded 2026-09-22
get_valid_padding basicsr/models/archs/discnet_arch.py ran · honoured contract fingerprinted no licence file found · pointer only · 1f28a2e923debcdb · report fixture: signature kernel_size:int/0/int, dilation:int/0/int · returned int · level recorded 2026-09-22
norm in 120 papers
census: 23 implementations from 26 papers, 15 distinct outputs across 6 buckets, one shared input per bucket
basicsr/models/archs/discnet_arch.py ran · our draft was wrong no licence file found · pointer only · b6a238bb90c0069b · report fixture: signature norm_type:str/0/str, nc:int/0/int · returned BatchNorm2d · level recorded 2026-09-22
pad in 85 papers basicsr/models/archs/discnet_arch.py ran · our draft was wrong no licence file found · pointer only · 4a56ce1917d87f9b · report fixture: signature pad_type:str/0/str, padding:int/0/int · returned ReflectionPad2d · level recorded 2026-09-22
upconv in 11 papers basicsr/models/archs/discnet_arch.py ran · our draft was wrong no licence file found · pointer only · a4ee0af247731bd3 · report fixture: signature in_nc:int/0/int, out_nc:int/0/int, upscale_factor:int/0/int, kernel_size:int/0/int, stride:int/0/int, bias:bool/0/bool, pad_type:str/0/str, norm_type:NoneType/0/?, act_type:str/0/str · returned Sequential · level recorded 2026-09-22
DISCNet basicsr/models/archs/discnet_arch.py unverified no licence file found · pointer only · fa8b013b61e4496e · report
default_init_weights basicsr/models/archs/discnet_arch.py unverified no licence file found · pointer only · e62081511dcd3fe1 · report
kernel2d_conv basicsr/models/archs/discnet_arch.py unverified no licence file found · pointer only · 33ece21f42f7e520 · report
sequential in 6 papers basicsr/models/archs/discnet_arch.py unverified no licence file found · pointer only · e4f6817e59050117 · 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 Dynamic Skip Connection Network (graph method: Dynamic Skip Connection Network). 11 bricks; individually on a fixture: 7 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 0 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 4 unverified. The assembly has not been run end-to-end.

  1. DISCNet entry · level 0 · unverified · fa8b013b61e4496e
  2. ResBlock model · level 1 · ran · 6b2f8c2ebe2461b0
  3. conv_block helper · level 1 · ran · our draft was wrong · 2088da310e2c1c79
  4. kernel2d_conv helper · level 0 · unverified · 33ece21f42f7e520
  5. upconv helper · level 1 · ran · our draft was wrong · a4ee0af247731bd3
  6. act helper · level 1 · ran · our draft was wrong · 15d829a065897df0
  7. default_init_weights helper · level 0 · unverified · e62081511dcd3fe1
  8. get_valid_padding helper · level 1 · ran · honoured contract · 1f28a2e923debcdb
  9. norm helper · level 1 · ran · our draft was wrong · b6a238bb90c0069b
  10. pad helper · level 1 · ran · our draft was wrong · 4a56ce1917d87f9b
  11. sequential helper · level 0 · unverified · e4f6817e59050117

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="2104.09556") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Image Restoration

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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