SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2203.14216 · ECCV · 2022

Efficient and Degradation-Adaptive Network for Real-World Image Super-Resolution

Lei Zhang, Jie Liang, Hui Zeng

arXiv · PDF · Open in the Atlas

Code that ran

2 of 4 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 2 failures of our instrument; 2 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2203.14216.json · badge: /api/ran/2203.14216.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
csjliang/DASR canonical (classifier label)
classifier basis not recorded on the link
2 ran · 2 no recorded run
FunctionStatusWhere it lives
reduce_loss Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
csjliang/DASR/basicsr/losses/loss_util.py
code served (permissive licence) · get_code("a648a03a952822c0")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import torch.nn.functional as F

torch.manual_seed(0)

# Create a small elementwise loss tensor (batch=2, elements=4)
loss = torch.tensor([[0.5, 1.2, 0.3, 0.8], [0.9, 0.4, 1.1, 0.6]], dtype=torch.float32)

# Test with 'mean' reduction
reduction = 'mean'

ARGS = {
    'loss': loss,
    'reduction': reduction,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 0, dtype family float, shape () — shape () as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
weight_reduce_loss Ran
ran; our contract draft was wrong, not the code
csjliang/DASR/basicsr/losses/loss_util.py
code served (permissive licence) · get_code("1ba39317ea81871a")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import torch.nn.functional as F

torch.manual_seed(0)

# Create a small loss tensor (batch_size=2, num_elements=4)
loss = torch.rand(2, 4)

# Create a weight tensor with matching dimensions
# weight.dim() == loss.dim() and weight.size(1) == loss.size(1)
weight = torch.rand(2, 4)

# Test different reduction modes
reduction = 'mean'

ARGS = {
    'loss': loss,
    'weight': weight,
    'reduction': reduction
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 0, dtype family float, shape () — shape () as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
load_file_from_url Not yet run
unverified (harvested, no recorded run)
csjliang/DASR/dasr/utils.py
code served (permissive licence) · get_code("8320f6f582d4637a")
How it ran

no invocation recorded.

weighted_loss Not yet run
unverified (harvested, no recorded run)
csjliang/DASR/basicsr/losses/loss_util.py
code served (permissive licence) · get_code("cf63f8afc13f62a7")
How it ran

no invocation recorded.

Also present in other papers' code

Of 4 samples lifted from this paper's linked repositories, 4 carry a function identity and 0 do not. Of the 4 distinct functions with an identity, 4 are also present in other papers whose code we hold (1 with at least one paper dated earlier, 0 the same month, 3 later) and 0 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

FunctionAlso present inEarliest-datedOthers named
weighted_loss 44 other papers
43 later, 1 same year, order not determinable
136790177 (2022 (year only))
Frequency and Spatial Dual Guidance for Image Dehazing
2205.05996 (2022-05)
Blueprint Separable Residual Network for Efficient Image Super-Resolution
2206.02146 (2022-06)
Recurrent Video Restoration Transformer with Guided Deformable Attention
and 41 more not named here
reduce_loss 43 other papers
42 later, 1 same year, order not determinable
136790177 (2022 (year only))
Frequency and Spatial Dual Guidance for Image Dehazing
2205.05996 (2022-05)
Blueprint Separable Residual Network for Efficient Image Super-Resolution
2206.02146 (2022-06)
Recurrent Video Restoration Transformer with Guided Deformable Attention
and 40 more not named here
weight_reduce_loss 43 other papers
42 later, 1 same year, order not determinable
136790177 (2022 (year only))
Frequency and Spatial Dual Guidance for Image Dehazing
2205.05996 (2022-05)
Blueprint Separable Residual Network for Efficient Image Super-Resolution
2206.02146 (2022-06)
Recurrent Video Restoration Transformer with Guided Deformable Attention
and 40 more not named here
load_file_from_url 1 other paper
1 dated earlier
2107.10833 (2021-07)
Real-ESRGAN: Training Real-World Blind Super-Resolution with Pure Synthetic Data

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Efficient and effective real-world image super-resolution (Real-ISR) is a challenging task due to the unknown complex degradation of real-world images and the limited computation resources in practical applications. Recent research on Real-ISR has achieved significant progress by modeling the image degradation space; however, these methods largely rely on heavy backbone networks and they are inflexible to handle images of different degradation levels. In this paper, we propose an efficient and effective degradation-adaptive super-resolution (DASR) network, whose parameters are adaptively specified by estimating the degradation of each input image. Specifically, a tiny regression network is employed to predict the degradation parameters of the input image, while several convolutional experts with the same topology are jointly optimized to specify the network parameters via a non-linear mixture of experts. The joint optimization of multiple experts and the degradation-adaptive pipeline significantly extend the model capacity to handle degradations of various levels, while the inference remains efficient since only one adaptively specified network is used for superresolving the input image. Our extensive experiments demonstrate that DASR is not only much more effective than existing methods on handling real-world images with different degradation levels but also efficient for easy deployment. Codes, models and datasets are available at https://github.com/csjliang/DASR.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2203.14216")
get_code_for_paper("2203.14216")
have("2203.14216")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2203.14216.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2203.14216.svg)](https://syntology.ai/paper/2203.14216)

Connect an agent — have() is free.