Papers › DP-NeRF: Deblurred Neural Radiance Field with Physical Scene Priors

DP-NeRF: Deblurred Neural Radiance Field with Physical Scene Priors

22 Nov 2022CVPR 2023 1arXiv:2211.12046archive 2025-07-28

Dogyoon Lee, Minhyeok Lee, Chajin Shin, Sangyoun Lee

Neural Radiance Field (NeRF) has exhibited outstanding three-dimensional (3D) reconstruction quality via the novel view synthesis from multi-view images and paired calibrated camera parameters. However, previous NeRF-based systems have been demonstrated under strictly controlled settings, with little attention paid to less ideal scenarios, including with the presence of noise such as exposure, illumination changes, and blur. In particular, though blur frequently occurs in real situations, NeRF that can handle blurred images has received little attention. The few studies that have investigated NeRF for blurred images have not considered geometric and appearance consistency in 3D space, which is one of the most important factors in 3D reconstruction. This leads to inconsistency and the degradation of the perceptual quality of the constructed scene. Hence, this paper proposes a DP-NeRF, a novel clean NeRF framework for blurred images, which is constrained with two physical priors. These priors are derived from the actual blurring process during image acquisition by the camera. DP-NeRF proposes rigid blurring kernel to impose 3D consistency utilizing the physical priors and adaptive weight proposal to refine the color composition error in consideration of the relationship between depth and blur. We present extensive experimental results for synthetic and real scenes with two types of blur: camera motion blur and defocus blur. The results demonstrate that DP-NeRF successfully improves the perceptual quality of the constructed NeRF ensuring 3D geometric and appearance consistency. We further demonstrate the effectiveness of our model with comprehensive ablation analysis.

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

dogyoonlee/dp-nerf officialmentioned in papermentioned on GitHubpytorchMITSyntology: 12 samples, 11 ran (4 instrument-failed) · 1 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: 11 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 2 violated, 5 with no contract checked; 4 where Syntology's instrument failed) · 1 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
2ran; the contract check could not run
5ran
1unverified

Licence: 0 of the 12 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 dogyoonlee/dp-nerf. “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.

dogyoonlee/dp-nerf official repository 12 samples, 11 ran (4 instrument-failed) · 1 unverified
compute_img_metric in 7 papers utils/metrics.py ran · our draft was wrong MIT (permissive) · 7ef64e41224b81bf · report fixture: signature im1t:Tensor/4/float, im2t:Tensor/4/float, metric:str/0/str, margin:int/0/int, mask:NoneType/0/? · returned float64 · level recorded 2026-09-25
compute_time run_dpnerf.py ran · violated contract fingerprinted MIT (permissive) · 4d61a4e68d52da3b · report fixture: signature dt:int/0/int · returned tuple · level recorded, date not recorded
get_embedder in 88 papers utils/run_dpnerf_helpers.py ran MIT (permissive) · c99caa4af7646b2e · report fixture: signature multires:int/0/int, i:int/0/int, input_dim:int/0/int · returned tuple · level recorded 2026-09-25
get_rays in 39 papers utils/run_dpnerf_helpers.py ran MIT (permissive) · c48b2dd212e8a456 · report fixture: signature H:int/0/int, W:int/0/int, K:Tensor/2/float, c2w:Tensor/2/float · returned tuple · level recorded 2026-09-25
get_rays_np in 13 papers utils/run_dpnerf_helpers.py ran MIT (permissive) · 899e6539904686a9 · report fixture: signature H:int/0/int, W:int/0/int, K:ndarray/2/float, c2w:ndarray/2/float · returned tuple · level recorded 2026-09-24
l2 in 38 papers
census: 5 implementations from 7 papers, 4 distinct outputs across 3 buckets, one shared input per bucket
lpips/lpips.py ran fingerprinted MIT (permissive) · cebd4a767f96722b · report fixture: signature p0:ndarray/2/float, p1:ndarray/2/float, range:float/0/float · returned float32 · 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
data_utils/load_llff.py ran · violated contract fingerprinted MIT (permissive) · 1d6f8390d799f055 · report fixture: signature x:ndarray/1/float · returned ndarray · level recorded 2026-09-22
normalize_tensor in 47 papers
census: 3 implementations from 5 papers, 2 distinct outputs across 2 buckets, one shared input per bucket
lpips/lpips.py ran · our draft was wrong fingerprinted MIT (permissive) · 61221a9686133a8c · report fixture: signature in_feat:Tensor/2/float, eps:float/0/float · returned Tensor · level recorded 2026-09-25
psnr in 88 papers
census: 9 implementations from 11 papers, 6 distinct outputs across 4 buckets, one shared input per bucket
lpips/lpips.py ran fingerprinted MIT (permissive) · e844cf206c6621e3 · report fixture: signature p0:ndarray/2/float, p1:ndarray/2/float, peak:float/0/float · returned float32 · level recorded 2026-09-25
ptstocam in 11 papers data_utils/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
viewmatrix in 18 papers data_utils/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
exponential_scale_fine_loss_weight run_dpnerf.py unverified MIT (permissive) · 91c1988cd56d32a6 · report

Tasks

3D ReconstructionNeRFNovel View Synthesis

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