Papers › SRFlow: Learning the Super-Resolution Space with Normalizing Flow

SRFlow: Learning the Super-Resolution Space with Normalizing Flow

25 Jun 2020ECCV 2020 8arXiv:2006.14200archive 2025-07-28

Andreas Lugmayr, Martin Danelljan, Luc van Gool, Radu Timofte

Super-resolution is an ill-posed problem, since it allows for multiple predictions for a given low-resolution image. This fundamental fact is largely ignored by state-of-the-art deep learning based approaches. These methods instead train a deterministic mapping using combinations of reconstruction and adversarial losses. In this work, we therefore propose SRFlow: a normalizing flow based super-resolution method capable of learning the conditional distribution of the output given the low-resolution input. Our model is trained in a principled manner using a single loss, namely the negative log-likelihood. SRFlow therefore directly accounts for the ill-posed nature of the problem, and learns to predict diverse photo-realistic high-resolution images. Moreover, we utilize the strong image posterior learned by SRFlow to design flexible image manipulation techniques, capable of enhancing super-resolved images by, e.g., transferring content from other images. We perform extensive experiments on faces, as well as on super-resolution in general. SRFlow outperforms state-of-the-art GAN-based approaches in terms of both PSNR and perceptual quality metrics, while allowing for diversity through the exploration of the space of super-resolved solutions.

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

No sample from the archive's official repository (andreas128/SRFlow) is linked to this paper; the 3 samples below come from 1 community repository. Syntology harvested code from andreas128/SRFlow for another paper.

andreas128/SRFlow: Syntology's graph links these samples to Deep Generative Model based Rate-Distortion for Image Downscaling Assessment (arXiv:2403.15139; that paper's own run record: 13 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 2 honoured, 3 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 7 unverified); nothing checks that they implement this paper's method.

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

By repository: community (archive-listed): 3 samples from 1 repository, 2 ran (0 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 4 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

andreas128/SRFlow officialmentioned in paperpytorchNOASSERTIONSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Deep Generative Model based Rate-Distortion for Image Downscaling Assessment (arXiv:2403.15139; that paper's own run record: 13 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 2 honoured, 3 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 7 unverified); nothing checks that they implement this paper's method. report
Zhangyanbo/iResNetLab mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Glow: Generative Flow with Invertible 1x1 Convolutions (arXiv:1807.03039; that paper's own run record: 85 ran (of which 47 constructed an object rather than computing a result; 73 with no instrument failure: 3 honoured, 0 violated, 70 with no contract checked; 12 where Syntology's instrument failed) · 44 unverified); nothing checks that they implement this paper's method. report
andreas128/NTIRE21_Learning_SR_Space mentioned on GitHubpytorchSyntology: not harvested report
friedmanroy/hi-generation mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to HIGlow: Conditional Normalizing Flows for High-Fidelity HI Map Modeling (arXiv:2211.12724; that paper's own run record: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
liyuantsao/BFSR mentioned on GitHubpytorchSyntology: 3 samples, 2 ran (2 instrument-failed) · 1 unverified report
liyuantsao/flowsr-lp mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Local Implicit Normalizing Flow for Arbitrary-Scale Image Super-Resolution (arXiv:2303.05156; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified); nothing checks that they implement this paper's method. report
seungho-snu/fxsr mentioned on GitHubpytorchSyntology: not harvested report
2023-MindSpore-1/ms-code-222 mindsporeSyntology: not harvested 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.

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

3 samples harvested: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure 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.

2ran · our draft was wrong
1unverified

Licence: 3 of the 3 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 liyuantsao/BFSR. “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.

liyuantsao/BFSR community (archive-listed) 3 samples, 2 ran (2 instrument-failed) · 1 unverified
dict2str in 30 papers SRFlow-LP/code/options/options.py ran · our draft was wrong no licence file found · pointer only · 40c52ad98161c17b · report fixture: signature opt:dict/0/?, indent_l:int/0/int · returned str · level recorded 2026-09-22
dict_to_nonedict in 22 papers SRFlow-LP/code/options/options.py ran · our draft was wrong no licence file found · pointer only · ada7273eee7081c7 · report fixture: signature opt:dict/0/? · returned NoneDict · level recorded 2026-09-22
parse in 85 papers SRFlow-LP/code/options/options.py unverified no licence file found · pointer only · 7738c4d667301cd0 · report

Tasks

DiversityImage ManipulationImage Super-ResolutionSuper-Resolution

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Image Super-Resolution DIV2K val - 4x upscaling SRFlow LPIPS 0.12 #8 of 21 Archive leaderboard report
Image Super-Resolution DIV2K val - 4x upscaling SRFlow LRPSNR 49.96 #8 of 21 Archive leaderboard report
Image Super-Resolution DIV2K val - 4x upscaling SRFlow NIQE 3.57 #8 of 21 Archive leaderboard report
Image Super-Resolution DIV2K val - 4x upscaling SRFlow PSNR 27.09 #8 of 21 Archive leaderboard report
Image Super-Resolution DIV2K val - 4x upscaling SRFlow SSIM 0.76 #8 of 21 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