Methods › Computer Vision › Image Models › EfficientNet

EfficientNet

195 papers tagged archive 2025-07-28

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

EfficientNet is a convolutional neural network architecture and scaling method that uniformly scales all dimensions of depth/width/resolution using a compound coefficient. Unlike conventional practice that arbitrary scales these factors, the EfficientNet scaling method uniformly scales network width, depth, and resolution with a set of fixed scaling coefficients. For example, if we want to use 2ᴺ times more computational resources, then we can simply increase the network depth by αᴺ, width by βᴺ, and image size by γᴺ, where α, β, γ are constant coefficients determined by a small grid search on the original small model. EfficientNet uses a compound coefficient ϕ to uniformly scales network width, depth, and resolution in a principled way.

The compound scaling method is justified by the intuition that if the input image is bigger, then the network needs more layers to increase the receptive field and more channels to capture more fine-grained patterns on the bigger image.

The base EfficientNet-B0 network is based on the inverted bottleneck residual blocks of MobileNetV2, in addition to squeeze-and-excitation blocks.

EfficientNets also transfer well and achieve state-of-the-art accuracy on CIFAR-100 (91.7%), Flowers (98.8%), and 3 other transfer learning datasets, with an order of magnitude fewer parameters.

Source: EfficientNet: Rethinking Model Scaling for Convolutional...See Code · lukemelas/EfficientNet-PyTorch

In Syntology harvested code stored, below machine verification (unverified_code; harvested), served level V1; retrieve with get_harvested_code_for_paper(arxiv_id='1905.11946'). Repositories: 145 listed of 145 in the graph, strongest link: official. The lookup matched a paper by its title, arXiv:1905.11946, not a method entry. The archive credits no paper with an arXiv id for this method, so whether this answer (about arXiv:1905.11946) is about this method is not checked.

Origin paper of this answer, arXiv:1905.11946 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 198 ran (of which 73 constructed an object rather than computing a result; 157 with no instrument failure: 26 honoured, 2 violated, 129 with no contract checked; 41 where Syntology's instrument failed) · 104 unverified (of 302 harvested samples) · 113 pointer-only (licence). The instrument figure counts failures of Syntology's instrument, not of the code. Ran means executed on a synthesized input, not that the code is correct.

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.

What each level means, quoted from Syntology's server card: V0 “imports”; V1 “executes against a synthesized fixture and returns a value of the recorded type”; 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.” The card adds: “No rung on this ladder compares the served code against the authors' implementation, so treat every level as evidence about runnability and internal agreement, not about matching the paper's results.” A level quoted in two parts is one definition the card writes as two clauses joined by a double hyphen, each clause quoted on its own (how these levels are quoted).

Papers archive 2025-07-28

archive papers tagged: 195 · with a code link: 101 · where Syntology ran a sample: 20 (15 with a run with no instrument failure, 5 where every run was a failure of Syntology's instrument) Syntology

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

Page 1 of 2: papers 1 to 100 of 195, 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 224 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
Image Classification42
Transfer Learning32
image-classification28
General Classification20
Object Detection17
Semantic Segmentation17
Data Augmentation16
Classification15
Deep Learning13
Neural Architecture Search12
Diagnostic10
object-detection10
Segmentation9
Decoder6
Self-Supervised Learning6
Specificity6
model6
Anomaly Detection5
Instance Segmentation5
Multi-Task Learning5

Usage over time archive 2025-07-28

Papers per year tagged with EfficientNet: 2019 to 2025, peak 62 62 0 2019: 14 papers 2019 2020: 57 papers 2020 2021: 30 papers 2021 2022: 8 papers 2022 2023: 4 papers 2023 2024: 62 papers 2024 2025: 20 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (195 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

Image Models

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