Papers › Efficient Long-Range Attention Network for Image Super-resolution

Efficient Long-Range Attention Network for Image Super-resolution

13 Mar 2022arXiv:2203.06697archive 2025-07-28

Xindong Zhang, Hui Zeng, Shi Guo, Lei Zhang

Recently, transformer-based methods have demonstrated impressive results in various vision tasks, including image super-resolution (SR), by exploiting the self-attention (SA) for feature extraction. However, the computation of SA in most existing transformer based models is very expensive, while some employed operations may be redundant for the SR task. This limits the range of SA computation and consequently the SR performance. In this work, we propose an efficient long-range attention network (ELAN) for image SR. Specifically, we first employ shift convolution (shift-conv) to effectively extract the image local structural information while maintaining the same level of complexity as 1x1 convolution, then propose a group-wise multi-scale self-attention (GMSA) module, which calculates SA on non-overlapped groups of features using different window sizes to exploit the long-range image dependency. A highly efficient long-range attention block (ELAB) is then built by simply cascading two shift-conv with a GMSA module, which is further accelerated by using a shared attention mechanism. Without bells and whistles, our ELAN follows a fairly simple design by sequentially cascading the ELABs. Extensive experiments demonstrate that ELAN obtains even better results against the transformer-based SR models but with significantly less complexity. The source code can be found at https://github.com/xindongzhang/ELAN.

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.

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

Code

Syntology 8 code samples harvested from 1 repository linked to this paper: 6 ran (of which 6 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified; every one of the 6 samples that ran constructed an object rather than computing a result. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 8 samples from 1 repository, 6 ran (6 with no instrument failure; 0 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

xindongzhang/elan officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 8 samples, 6 ran (0 instrument-failed) · 2 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

8 samples harvested: 6 ran (of which 6 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified; every one of the 6 samples that ran constructed an object rather than computing a result. “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.

6ran
2unverified

Licence: 0 of the 8 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 xindongzhang/elan. “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.

xindongzhang/elan official repository 8 samples, 6 ran (0 instrument-failed) · 2 unverified
GMSA models/elan_network.py ran Apache-2.0 (permissive) · dfe23f9c73fba360 · report fixture: returned GMSA · level recorded 2026-09-22
LFE models/elan_network.py ran Apache-2.0 (permissive) · e2f3cf4b805acd22 · report fixture: returned LFE · level recorded 2026-09-22
MeanShift in 7 papers models/elan_network.py ran fingerprinted Apache-2.0 (permissive) · d490b61d417da427 · report fixture: returned MeanShift · level recorded 2026-09-22
ShiftConv2d models/elan_network.py ran Apache-2.0 (permissive) · e096da98ed9b4c9b · report fixture: returned ShiftConv2d · level recorded 2026-09-22
ShiftConv2d0 models/elan_network.py ran Apache-2.0 (permissive) · 66d05bc6340179bf · report fixture: returned ShiftConv2d0 · level recorded 2026-09-22
ShiftConv2d1 models/elan_network.py ran Apache-2.0 (permissive) · 41750d8ae4ed5bb6 · report fixture: returned ShiftConv2d1 · level recorded 2026-09-22
ELAB models/elan_network.py unverified Apache-2.0 (permissive) · 0d8891855a2a0b6b · report
ELAN models/elan_network.py unverified Apache-2.0 (permissive) · 50a985088fff2f68 · 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 Efficient Long-Range Attention Network (ELAN) (graph method: Efficient Long-Range Attention Network (ELAN)). 8 bricks; individually on a fixture: 6 ran (of which 6 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified; every one of the 6 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

  1. ELAN entry · level 0 · unverified · 50a985088fff2f68
  2. ELAB model · level 0 · unverified · 0d8891855a2a0b6b
  3. MeanShift helper · level 1 · ran · d490b61d417da427
  4. GMSA model · level 1 · ran · dfe23f9c73fba360
  5. LFE model · level 1 · ran · e2f3cf4b805acd22
  6. ShiftConv2d model · level 1 · ran · e096da98ed9b4c9b
  7. ShiftConv2d0 helper · level 1 · ran · 66d05bc6340179bf
  8. ShiftConv2d1 helper · level 1 · ran · 41750d8ae4ed5bb6

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

Tasks

Image Super-ResolutionSuper-Resolution

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Image Super-Resolution Manga109 - 4x upscaling ELAN PSNR 31.68 #18 of 50 Archive leaderboard report
Image Super-Resolution Manga109 - 4x upscaling ELAN SSIM 0.9226 #18 of 50 Archive leaderboard report
Image Super-Resolution Set14 - 4x upscaling ELAN PSNR 28.96 #33 of 104 Archive leaderboard report
Image Super-Resolution Set14 - 4x upscaling ELAN SSIM 0.7914 #33 of 104 Archive leaderboard report
Image Super-Resolution Set14 - 4x upscaling ELAN-light PSNR 28.78 #52 of 104 Archive leaderboard report
Image Super-Resolution Set14 - 4x upscaling ELAN-light SSIM 0.7858 #52 of 104 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.

Methods

Convolution

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