Methods › Computer Vision › Light-weight neural networks › GhostNet

GhostNet

22 papers tagged archive 2025-07-28

Introduced by Kai Han et al. in GhostNet: More Features from Cheap Operations

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

A GhostNet is a type of convolutional neural network that is built using Ghost modules, which aim to generate more features by using fewer parameters (allowing for greater efficiency).

GhostNet mainly consists of a stack of Ghost bottlenecks with the Ghost modules as the building block. The first layer is a standard convolutional layer with 16 filters, then a series of Ghost bottlenecks with gradually increased channels follow. These Ghost bottlenecks are grouped into different stages according to the sizes of their input feature maps. All the Ghost bottlenecks are applied with stride=1 except that the last one in each stage is with stride=2. At last a global average pooling and a convolutional layer are utilized to transform the feature maps to a 1280-dimensional feature vector for final classification. The squeeze and excite (SE) module is also applied to the residual layer in some ghost bottlenecks.

In contrast to MobileNetV3, GhostNet does not use hard-swish nonlinearity function due to its large latency.

PaperSourceSee Code · osmr/imgclsmob

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

Origin paper of this answer, arXiv:1911.11907 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 19 ran (of which 0 constructed an object rather than computing a result; 16 with no instrument failure: 3 honoured, 0 violated, 13 with no contract checked; 3 where Syntology's instrument failed) · 4 unverified (of 23 harvested samples) · 5 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: 22 · with a code link: 15 · where Syntology ran a sample: 5 (4 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument) Syntology

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

Page 1 of 1: papers 1 to 22 of 22, 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 40 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 Classification8
image-classification5
Object Detection3
GPU2
Segmentation2
Semantic Segmentation2
object-detection2
Acoustic Scene Classification1
Action Recognition1
CPU1
Data Augmentation1
Defect Detection1
Denoising1
Depth Estimation1
EEG1
Emotion Recognition1
Human Detection1
Image Segmentation1
Image Super-Resolution1
Instance Segmentation1

Usage over time archive 2025-07-28

Papers per year tagged with GhostNet: 2019 to 2024, peak 7 7 0 2019: 1 paper 2019 2020: 4 papers 2020 2021: 5 papers 2021 2022: 7 papers 2022 2023: 1 paper 2023 2024: 4 papers 2024
Papers per year the archive tags with this method, by the paper's archive date (22 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

Light-weight neural networksConvolutional Neural Networks

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