Methods › General › Miscellaneous Components › PixelShuffle

PixelShuffle

45 papers tagged archive 2025-07-28

Introduced by Wenzhe Shi et al. in Real-Time Single Image and Video Super-Resolution Using an Efficient Sub-Pixel Convolutional Neural Network

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

PixelShuffle is an operation used in super-resolution models to implement efficient sub-pixel convolutions with a stride of 1/r. Specifically it rearranges elements in a tensor of shape (*, C ×r², H, W) to a tensor of shape (*, C, H ×r, W ×r).

Image Source: Remote Sensing Single-Image Resolution Improvement Using A Deep Gradient-Aware Network with Image-Specific Enhancement

PaperSourceSee Code · pytorch/pytorch

In Syntology name not resolved (unknown_name). The lookup matched no method, paper or venue by this name; that asserts nothing about whether code exists.

Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.

Papers archive 2025-07-28

archive papers tagged: 45 · with a code link: 25 · where Syntology ran a sample: 5 (5 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (5 of 45 tagged: 5 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)

Page 1 of 1: papers 1 to 45 of 45, newest first by the archive's date (ties by slug), in archive order.

Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.

Tasks archive 2025-07-28

20 shown of 57 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Super-Resolution40
Image Super-Resolution21
Generative Adversarial Network11
Video Super-Resolution10
SSIM9
Video Enhancement3
Decoder2
Denoising2
GPU2
Optical Flow Estimation2
Quantization2
Semantic Segmentation2
Video Restoration2
Video deraining2
Analog Video Restoration1
Brain Tumor Segmentation1
CPU1
Colorization1
Data Compression1
Deblurring1

Usage over time archive 2025-07-28

Papers per year tagged with PixelShuffle: 2016 to 2025, peak 10 10 0 2016: 1 paper 2016 2017: 0 papers 2017 2018: 6 papers 2018 2019: 5 papers 2019 2020: 10 papers 2020 2021: 5 papers 2021 2022: 7 papers 2022 2023: 4 papers 2023 2024: 6 papers 2024 2025: 1 paper 2025
Papers per year the archive tags with this method, by the paper's archive date (45 dated). Bars are counts, not a trend claim.

Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).

Categories archive 2025-07-28

Miscellaneous Components

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