Papers › End-to-end Alternating Optimization for Real-World Blind Super Resolution
End-to-end Alternating Optimization for Real-World Blind Super Resolution
Zhengxiong Luo, Yan Huang, Shang Li, Liang Wang, Tieniu Tan
Blind Super-Resolution (SR) usually involves two sub-problems: 1) estimating the degradation of the given low-resolution (LR) image; 2) super-resolving the LR image to its high-resolution (HR) counterpart. Both problems are ill-posed due to the information loss in the degrading process. Most previous methods try to solve the two problems independently, but often fall into a dilemma: a good super-resolved HR result requires an accurate degradation estimation, which however, is difficult to be obtained without the help of original HR information. To address this issue, instead of considering these two problems independently, we adopt an alternating optimization algorithm, which can estimate the degradation and restore the SR image in a single model. Specifically, we design two convolutional neural modules, namely Restorer and Estimator. Restorer restores the SR image based on the estimated degradation, and Estimator estimates the degradation with the help of the restored SR image. We alternate these two modules repeatedly and unfold this process to form an end-to-end trainable network. In this way, both Restorer and Estimator could get benefited from the intermediate results of each other, and make each sub-problem easier. Moreover, Restorer and Estimator are optimized in an end-to-end manner, thus they could get more tolerant of the estimation deviations of each other and cooperate better to achieve more robust and accurate final results. Extensive experiments on both synthetic datasets and real-world images show that the proposed method can largely outperform state-of-the-art methods and produce more visually favorable results. The codes are rleased at https://github.com/greatlog/RealDAN.git.
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):
get_harvested_code_for_paper(arxiv_id="2308.08816")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2308.08816", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2308.08816")
Code
Syntology 15 code samples harvested from 1 repository linked to this paper: 11 ran (of which 8 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 2 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 15 samples from 1 repository, 11 ran (9 with no instrument failure; 2 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.
No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:
- greatlog/DAN, community (archive-listed): harvested for another paper, listed under the repository
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.
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.
A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.
Code Syntology ran Syntology
15 samples harvested: 11 ran (of which 8 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 2 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 last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 15 of the 15 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 greatlog/realdan. “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: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.
597407e0ef5f0ffc · report
fixture: returned Estimator_L · level recorded 2026-09-22 93cd657d05d345f1 · report
fixture: returned Estimator_S · level recorded 2026-09-22 2c669d003de5c991 · report
fixture: returned RRDB · level recorded 2026-09-22 1ff491126ca5cfab · report
fixture: returned Registry · level recorded 2026-09-22 322463443631e7b2 · report
fixture: returned ResBlockv2 · level recorded 2026-09-22 651e9332d7582b2d · report
fixture: returned ResidualBlockNoBN · level recorded 2026-09-22 b66a5402faceaed0 · report
fixture: returned ResidualDenseBlock_5C · level recorded 2026-09-22 07ebce59f59416a0 · report
fixture: returned Upsampler · level recorded 2026-09-22 ffe305c88adc595a · report
fixture: signature feat:Tensor/4/float, flow:Tensor/4/float, mode:str/0/str, padding_mode:str/0/str · returned Tensor · level recorded 2026-09-24 f49ae20c66e878e6 · report
fixture: signature activation:str/0/str, activation_params:dict/0/?, num_channels:int/0/int · returned PReLU · level recorded 2026-09-22 e95863a41a94133f · report
fixture: signature basic_block:callable/0/?, num_basic_block:int/0/int, in_channels:int/0/int, out_channels:int/0/int · returned Sequential · level recorded 2026-09-25 a9fcc5b5cc2154db · report
10b54053c54fe1e1 · report
4e53ff141fdde271 · report
fc2bdd408f663b78 · 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 End-to-end Alternating Optimization (graph method: End-to-end Alternating Optimization). 13 bricks; individually on a fixture: 9 ran (of which 8 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. The assembly has not been run end-to-end.
- DAN entry · level 0 · unverified ·
a9fcc5b5cc2154db - Estimator_L model · level 1 · ran ·
597407e0ef5f0ffc - Estimator_S model · level 1 · ran ·
93cd657d05d345f1 - Restorer model · level 0 · unverified ·
10b54053c54fe1e1 - Upsampler helper · level 1 · ran ·
07ebce59f59416a0 - ResBlockv2 helper · level 1 · ran ·
322463443631e7b2 - RRDB model · level 1 · ran ·
2c669d003de5c991 - ResidualBlockNoBN helper · level 1 · ran ·
651e9332d7582b2d - get_activation helper · level 1 · ran · our draft was wrong ·
f49ae20c66e878e6 - get_attention helper · level 0 · unverified ·
fc2bdd408f663b78 - ResidualDenseBlock_5C model · level 1 · ran ·
b66a5402faceaed0 - default_init_weights helper · level 0 · unverified ·
4e53ff141fdde271 - Registry helper · level 1 · ran ·
1ff491126ca5cfab
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="2308.08816") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
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