Papers › OFTSR: One-Step Flow for Image Super-Resolution with Tunable Fidelity-Realism Trade-offs

OFTSR: One-Step Flow for Image Super-Resolution with Tunable Fidelity-Realism Trade-offs

12 Dec 2024arXiv:2412.09465archive 2025-07-28

Yuanzhi Zhu, Ruiqing Wang, Shilin Lu, Junnan Li, Hanshu Yan, Kai Zhang

Recent advances in diffusion and flow-based generative models have demonstrated remarkable success in image restoration tasks, achieving superior perceptual quality compared to traditional deep learning approaches. However, these methods either require numerous sampling steps to generate high-quality images, resulting in significant computational overhead, or rely on model distillation, which usually imposes a fixed fidelity-realism trade-off and thus lacks flexibility. In this paper, we introduce OFTSR, a novel flow-based framework for one-step image super-resolution that can produce outputs with tunable levels of fidelity and realism. Our approach first trains a conditional flow-based super-resolution model to serve as a teacher model. We then distill this teacher model by applying a specialized constraint. Specifically, we force the predictions from our one-step student model for same input to lie on the same sampling ODE trajectory of the teacher model. This alignment ensures that the student model's single-step predictions from initial states match the teacher's predictions from a closer intermediate state. Through extensive experiments on challenging datasets including FFHQ (256×256), DIV2K, and ImageNet (256×256), we demonstrate that OFTSR achieves state-of-the-art performance for one-step image super-resolution, while having the ability to flexibly tune the fidelity-realism trade-off. Code and pre-trained models are available at https://github.com/yuanzhi-zhu/OFTSR and https://huggingface.co/Yuanzhi/OFTSR, respectively.

PaperPDFCodeCode 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.

Syntology holds a reference implementation of OFTSR, generated from the paper text (not the authors' code), at level 3 on Syntology's ladder: V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” (quoted from Syntology's server card). No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='OFTSR') (how to connect); the free check have('2412.09465') needs no token.

For agents, on Syntology's MCP service (how to connect):

Code

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

By repository: official repository: 16 samples from 1 repository, 12 ran (6 with no instrument failure; 6 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. 2 of the 12 samples that ran have no recorded date.

yuanzhi-zhu/oftsr officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 16 samples, 12 ran (6 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

16 samples harvested: 12 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 2 honoured, 1 violated, 3 with no contract checked; 6 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.

2ran · honoured contract
1ran · violated contract
6ran · our draft was wrong
3ran
4unverified

Licence: 1 of the 16 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from yuanzhi-zhu/oftsr. “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.

yuanzhi-zhu/oftsr official repository 16 samples, 12 ran (6 instrument-failed) · 4 unverified
calc_psnr in 26 papers evaluate.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 543fa13af92ef55b · report fixture: signature batch1:Tensor/4/float, batch2:Tensor/4/float, max_pixel:float/0/float, eps:float/0/float · returned float · level recorded, date not recorded
constant in 36 papers fm/augment.py ran · our draft was wrong Apache-2.0 (permissive) here; the stored copy is pointer only · 6d32f9cf6f29b386 · report fixture: signature value:ndarray/1/float, shape:tuple/1/int, dtype:dtype/0/?, device:device/0/?, memory_format:memory_format/0/? · returned Tensor · level recorded 2026-09-24
get_optimizer in 228 papers fm/losses.py ran Apache-2.0 (permissive) · 3e026dce22169267 · report fixture: signature config:Config/0/?, params:generator/0/? · returned Adam · level recorded 2026-09-25
get_timesteps_gan distill_fm.py ran Apache-2.0 (permissive) · 4d5a0650804371ce · report fixture: signature gan_noise_level:str/0/str, bsz:int/0/int, device:str/0/str · returned Tensor · level recorded 2026-09-25
imread_uint in 6 papers fm/image_datasets.py ran · honoured contract Apache-2.0 (permissive) · 913183cf9882fc5a · report fixture: signature path:str/0/str, n_channels:int/0/int · returned ndarray · level recorded 2026-09-25
numpy_to_pil in 37 papers fid.py ran · our draft was wrong Apache-2.0 (permissive) · 19892367876e0b4f · report fixture: signature np_array:ndarray/3/int · returned Image · level recorded 2026-09-25
optimization_manager in 26 papers fm/losses.py ran · our draft was wrong Apache-2.0 (permissive) · 4c3fe3149cfaaedc · report fixture: signature config:Config/0/? · returned function · level recorded 2026-09-25
pil_to_numpy fid.py ran · violated contract Apache-2.0 (permissive) · 75981a871aba8899 · report fixture: signature pil_img:Image/0/? · returned ndarray · level recorded 2026-09-25
prepare_paired_batch train_fm.py ran · our draft was wrong Apache-2.0 (permissive) · cdaadfbb9242c2cf · report fixture: signature flow:callable/0/?, batch:Tensor/4/float, config:Config/0/?, augment_pipe:callable/0/?, mode:str/0/str · returned dict · level recorded, date not recorded
translate2d fm/augment.py ran · honoured contract Apache-2.0 (permissive) · 7b7201c90355cb09 · report fixture: signature tx:float/0/float, ty:float/0/float, device:device/0/? · returned Tensor · level recorded 2026-09-25
translate3d fm/augment.py ran Apache-2.0 (permissive) · 8137c1b6cc279011 · report fixture: signature tx:float/0/float, ty:float/0/float, tz:float/0/float, device:device/0/? · returned Tensor · level recorded 2026-09-25
zero_module in 184 papers models/nn.py ran · our draft was wrong Apache-2.0 (permissive) · 129b804760b3115f · report fixture: signature module:callable/0/? · returned SimpleModule · level recorded 2026-09-22
avg_pool_nd in 83 papers models/nn.py unverified Apache-2.0 (permissive) · ecd0fc28815b65ae · report
conv_nd in 94 papers models/nn.py unverified Apache-2.0 (permissive) · fe4eb545bbb728e0 · report
get_weightings in 6 papers fm/losses.py unverified Apache-2.0 (permissive) · b6cf0eb0ba82bf62 · report
unet_enc_forward models/unet.py unverified Apache-2.0 (permissive) · 142f5e900ff3ed99 · 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. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model". Where an assembly's phrase has no constructed figure, a brick that ran is not among the harvested samples this build reads, and whether a brick's run only constructed an object is read from that brick's harvested sample, so the figure was not counted; it does not say there were none.

1 assembly on this paper: 0 harvested, 1 generated.

generated Assembly for OFTSR (graph method: OFTSR), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 1 ran (1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. Ran end-to-end against an independent peer (level 3; 5 property tests passed on both).

label matches by construction: the code was generated for this method (not judged by a model)

  1. compute_oftsr_distillation_loss entry · level 3 · ran · honoured contract · c47a90872db32b8cf7f502bb74620fa2d63bdba01f7a54579212e1980c5a0408

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

Tasks

Image RestorationImage Super-ResolutionSuper-Resolution

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Diffusion

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