Papers › Auto-Exposure Fusion for Single-Image Shadow Removal

Auto-Exposure Fusion for Single-Image Shadow Removal

1 Mar 2021CVPR 2021 1arXiv:2103.01255archive 2025-07-28

Lan Fu, Changqing Zhou, Qing Guo, Felix Juefei-Xu, Hongkai Yu, Wei Feng, Yang Liu, Song Wang

Shadow removal is still a challenging task due to its inherent background-dependent and spatial-variant properties, leading to unknown and diverse shadow patterns. Even powerful state-of-the-art deep neural networks could hardly recover traceless shadow-removed background. This paper proposes a new solution for this task by formulating it as an exposure fusion problem to address the challenges. Intuitively, we can first estimate multiple over-exposure images w.r.t. the input image to let the shadow regions in these images have the same color with shadow-free areas in the input image. Then, we fuse the original input with the over-exposure images to generate the final shadow-free counterpart. Nevertheless, the spatial-variant property of the shadow requires the fusion to be sufficiently `smart', that is, it should automatically select proper over-exposure pixels from different images to make the final output natural. To address this challenge, we propose the shadow-aware FusionNet that takes the shadow image as input to generate fusion weight maps across all the over-exposure images. Moreover, we propose the boundary-aware RefineNet to eliminate the remaining shadow trace further. We conduct extensive experiments on the ISTD, ISTD+, and SRD datasets to validate our method's effectiveness and show better performance in shadow regions and comparable performance in non-shadow regions over the state-of-the-art methods. We release the model and code in https://github.com/tsingqguo/exposure-fusion-shadow-removal.

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

The archive's official repository (tsingqguo/exposure-fusion-shadow-removal) was not harvested; the 7 samples below come from 1 community repository.

Syntology 7 code samples harvested from 1 repository linked to this paper: 3 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

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

tsingqguo/exposure-fusion-shadow-removal officialmentioned in papermentioned on GitHubpytorchSyntology: not harvested report
CV-Reimplementation/AEFNet-Reimplementation pytorchSyntology: 7 samples, 3 ran (1 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

7 samples harvested: 3 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 1 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; the contract check could not run
2ran
4unverified

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 CV-Reimplementation/AEFNet-Reimplementation. “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”. For 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “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.

CV-Reimplementation/AEFNet-Reimplementation community (archive-listed) 7 samples, 3 ran (1 instrument-failed) · 4 unverified
GradientLoss models/Fusion_model.py ran · metamorphic tier: deterministic no licence file found · pointer only · 973bfc25e8f16d63 · report fixture: returned GradientLoss · level recorded 2026-09-22
L_TV models/Fusion_model.py ran fingerprinted no licence file found · pointer only · 1573d916ee849cff · report fixture: signature x:Tensor/4/float · returned Tensor · level recorded 2026-09-24
tensor2im in 30 papers models/Fusion_model.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant no licence file found · pointer only · c45b6700be1cc109 · report fixture: returned ndarray · level recorded 2026-09-22
BaseModel in 92 papers models/Fusion_model.py unverified no licence file found · pointer only · 6b8739e8fabd686e · report
DistangleModel models/Fusion_model.py unverified no licence file found · pointer only · fa0b81ea417ad17d · report
FusionModel models/Fusion_model.py unverified no licence file found · pointer only · ffad6ea71a6ce1ff · report
PoissonGradientLoss models/Fusion_model.py unverified no licence file found · pointer only · 5162d854ad287b25 · 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 FusionNet (graph method: FusionNet). 7 bricks; individually on a fixture: 3 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. The assembly has not been run end-to-end.

  1. FusionModel entry · level 0 · unverified · ffad6ea71a6ce1ff
  2. BaseModel helper · level 0 · unverified · 6b8739e8fabd686e
  3. DistangleModel helper · level 0 · unverified · fa0b81ea417ad17d
  4. GradientLoss loss · level 1 · ran · 973bfc25e8f16d63
  5. L_TV loss · level 1 · ran · 1573d916ee849cff
  6. PoissonGradientLoss loss · level 0 · unverified · 5162d854ad287b25
  7. tensor2im helper · level 1 · ran; the contract check could not run (RAISES) · c45b6700be1cc109

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

Tasks

Image Shadow RemovalShadow Removal

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Shadow Removal ISTD+ Auto (CVPR 2021) (512x512) LPIPS 0.189 #6 of 26 Archive leaderboard report
Shadow Removal ISTD+ Auto (CVPR 2021) (512x512) PSNR 28.07 #6 of 26 Archive leaderboard report
Shadow Removal ISTD+ Auto (CVPR 2021) (512x512) RMSE 2.99 #6 of 26 Archive leaderboard report
Shadow Removal ISTD+ Auto (CVPR 2021) (512x512) SSIM 0.853 #6 of 26 Archive leaderboard report
Shadow Removal ISTD+ Auto (CVPR 2021) (256x256) LPIPS 0.365 #21 of 26 Archive leaderboard report
Shadow Removal ISTD+ Auto (CVPR 2021) (256x256) PSNR 26.1 #21 of 26 Archive leaderboard report
Shadow Removal ISTD+ Auto (CVPR 2021) (256x256) RMSE 3.53 #21 of 26 Archive leaderboard report
Shadow Removal ISTD+ Auto (CVPR 2021) (256x256) SSIM 0.718 #21 of 26 Archive leaderboard report
Shadow Removal SRD Auto (CVPR 2021) (512x512) LPIPS 0.247 #19 of 25 Archive leaderboard report
Shadow Removal SRD Auto (CVPR 2021) (512x512) PSNR 24.32 #19 of 25 Archive leaderboard report
Shadow Removal SRD Auto (CVPR 2021) (512x512) RMSE 4.71 #19 of 25 Archive leaderboard report
Shadow Removal SRD Auto (CVPR 2021) (512x512) SSIM 0.8 #19 of 25 Archive leaderboard report
Shadow Removal SRD Auto (CVPR 2021) (256x256) LPIPS 0.37 #22 of 25 Archive leaderboard report
Shadow Removal SRD Auto (CVPR 2021) (256x256) PSNR 23.2 #22 of 25 Archive leaderboard report
Shadow Removal SRD Auto (CVPR 2021) (256x256) RMSE 5.37 #22 of 25 Archive leaderboard report
Shadow Removal SRD Auto (CVPR 2021) (256x256) SSIM 0.694 #22 of 25 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

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