Papers › See More Details: Efficient Image Super-Resolution by Experts Mining

See More Details: Efficient Image Super-Resolution by Experts Mining

5 Feb 2024arXiv:2402.03412archive 2025-07-28

Eduard Zamfir, Zongwei Wu, Nancy Mehta, Yulun Zhang, Radu Timofte

Reconstructing high-resolution (HR) images from low-resolution (LR) inputs poses a significant challenge in image super-resolution (SR). While recent approaches have demonstrated the efficacy of intricate operations customized for various objectives, the straightforward stacking of these disparate operations can result in a substantial computational burden, hampering their practical utility. In response, we introduce SeemoRe, an efficient SR model employing expert mining. Our approach strategically incorporates experts at different levels, adopting a collaborative methodology. At the macro scale, our experts address rank-wise and spatial-wise informative features, providing a holistic understanding. Subsequently, the model delves into the subtleties of rank choice by leveraging a mixture of low-rank experts. By tapping into experts specialized in distinct key factors crucial for accurate SR, our model excels in uncovering intricate intra-feature details. This collaborative approach is reminiscent of the concept of "see more", allowing our model to achieve an optimal performance with minimal computational costs in efficient settings. The source will be publicly made available at https://github.com/eduardzamfir/seemoredetails

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 19 code samples harvested from 2 repositories linked to this paper: 15 ran (of which 13 constructed an object rather than computing a result; 14 with no instrument failure: 0 honoured, 0 violated, 14 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 10 samples from 1 repository, 7 ran (7 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 9 samples from 1 repository, 8 ran (7 with no instrument failure; 1 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

eduardzamfir/seemoredetails officialmentioned in papermentioned on GitHubpytorchSyntology: 10 samples, 7 ran (0 instrument-failed) · 3 unverified report
zhoushen1/MEASNet mentioned on GitHubpytorchSyntology: 9 samples, 8 ran (1 instrument-failed) · 1 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

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

1ran; the contract check could not run
14ran
4unverified

Licence: 9 of the 19 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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 8 samples 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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

eduardzamfir/seemoredetails official repository 10 samples, 7 ran (0 instrument-failed) · 3 unverified
Expert in 7 papers basicsr/archs/seemore_arch.py ran fingerprinted Apache-2.0 (permissive) · 8e705ad33db3ece0 · report fixture: returned Expert · level recorded 2026-09-22
GatedFFN basicsr/archs/seemore_arch.py ran fingerprinted Apache-2.0 (permissive) · 66c26e9c9b1d539f · report fixture: returned GatedFFN · level recorded 2026-09-22
MoEBlock basicsr/archs/seemore_arch.py ran Apache-2.0 (permissive) · 4f3e4c93dfd5cb1a · report fixture: returned MoEBlock · level recorded 2026-09-22
MoELayer in 5 papers basicsr/archs/seemore_arch.py ran Apache-2.0 (permissive) · d161ce9a080bff74 · report fixture: returned MoELayer · level recorded 2026-09-22
Router in 11 papers basicsr/archs/seemore_arch.py ran fingerprinted Apache-2.0 (permissive) · f825feff5cc9f504 · report fixture: returned Router · level recorded 2026-09-22
SME basicsr/archs/seemore_arch.py ran fingerprinted Apache-2.0 (permissive) · 37b23826145deabe · report fixture: returned SME · level recorded 2026-09-22
StripedConvFormer basicsr/archs/seemore_arch.py ran fingerprinted Apache-2.0 (permissive) · 513ee53b4c559a5a · report fixture: returned StripedConvFormer · level recorded 2026-09-22
RME basicsr/archs/seemore_arch.py unverified Apache-2.0 (permissive) · fb65e199251d159e · report
ResGroup basicsr/archs/seemore_arch.py unverified Apache-2.0 (permissive) · 69415565c8c15832 · report
SeemoRe basicsr/archs/seemore_arch.py unverified Apache-2.0 (permissive) · ddb8a8108be5a5c7 · report
zhoushen1/MEASNet community (archive-listed) 9 samples, 8 ran (1 instrument-failed) · 1 unverified
EL MEASNet/net/FD_MEE.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · 1d1bc8a1a6d7eecd · report fixture: returned EL · level recorded 2026-09-22
FD MEASNet/net/FD_MEE.py ran no licence file found · pointer only · b890f94263e3455b · report fixture: signature x:Tensor/4/float · returned tuple · level recorded 2026-09-24
Layer in 20 papers MEASNet/net/FD_MEE.py ran · metamorphic tier: deterministic no licence file found · pointer only · 9146fec2223e3a45 · report fixture: returned Layer · level recorded 2026-09-22
MEE MEASNet/net/FD_MEE.py ran · metamorphic tier: deterministic no licence file found · pointer only · 26e700a2cf13763b · report fixture: returned MEE · level recorded 2026-09-22
MESE MEASNet/net/FD_MEE.py ran · metamorphic tier: deterministic no licence file found · pointer only · 17e909eea51c6bed · report fixture: returned MESE · level recorded 2026-09-22
StripedConv2d MEASNet/net/FD_MEE.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · 1b9acd1b10cbbbff · report fixture: returned StripedConv2d · level recorded 2026-09-22
WET MEASNet/net/FD_MEE.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · 4d9c76578a8d3647 · report fixture: returned WET · level recorded 2026-09-22
channel_shuffle in 35 papers
census: 3 implementations from 7 papers, 2 distinct outputs on one shared input
MEASNet/net/FD_MEE.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 80663608dbd5eff8 · report fixture: signature x:Tensor/4/float, groups:int/0/int · returned Tensor · level recorded 2026-09-22
FD_MEE MEASNet/net/FD_MEE.py unverified no licence file found · pointer only · 3cb1c1cb77fa48b8 · 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. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.

2 assemblies on this paper: 2 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).

2 sibling assemblies for SeemoRe (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for SeemoRe (graph method: SeemoRe). 10 bricks; individually on a fixture: 9 ran (of which 7 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) · 1 unverified. The assembly has not been run end-to-end.

one of 2 siblings

  1. FD_MEE entry · level 0 · unverified · 3cb1c1cb77fa48b8
  2. FD helper · level 1 · ran · b890f94263e3455b
  3. MEE helper · level 1 · ran · 26e700a2cf13763b
  4. LayerNorm helper · level 1 · ran · f7cde5f401e45872
  5. MESE helper · level 1 · ran · 17e909eea51c6bed
  6. EL helper · level 1 · ran · 1d1bc8a1a6d7eecd
  7. Layer helper · level 1 · ran · 9146fec2223e3a45
  8. StripedConv2d helper · level 1 · ran · 1b9acd1b10cbbbff
  9. WET helper · level 1 · ran · 4d9c76578a8d3647
  10. channel_shuffle helper · level 1 · ran; the contract check could not run (RAISES) · 80663608dbd5eff8

harvested Assembly for SeemoRe (graph method: SeemoRe). 14 bricks; individually on a fixture: 11 ran (of which 10 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 1 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.

one of 2 siblings

  1. SeemoRe entry · level 0 · unverified · ddb8a8108be5a5c7
  2. LayerNorm model · level 1 · ran · 2f8121a6bb6bf49c
  3. ResGroup model · level 0 · unverified · 69415565c8c15832
  4. RME model · level 0 · unverified · fb65e199251d159e
  5. SME model · level 1 · ran · 37b23826145deabe
  6. GatedFFN model · level 1 · ran · 66c26e9c9b1d539f
  7. MoEBlock model · level 1 · ran · 4f3e4c93dfd5cb1a
  8. StripedConvFormer model · level 1 · ran · 513ee53b4c559a5a
  9. Expert model · level 1 · ran · 8e705ad33db3ece0
  10. MoELayer model · level 1 · ran · d161ce9a080bff74
  11. Router model · level 1 · ran · f825feff5cc9f504
  12. StripedConv2d model · level 1 · ran · 1b9acd1b10cbbbff
  13. channel_shuffle helper · level 1 · ran; the contract check could not run (RAISES) · 80663608dbd5eff8
  14. Registry helper · level 1 · ran · 2cd4dd2a6360b684

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="2402.03412") 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

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