Methods › Computer Vision › Feature Extractors › FPN

Feature Pyramid Network

FPN

583 papers tagged archive 2025-07-28

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

A Feature Pyramid Network, or FPN, is a feature extractor that takes a single-scale image of an arbitrary size as input, and outputs proportionally sized feature maps at multiple levels, in a fully convolutional fashion. This process is independent of the backbone convolutional architectures. It therefore acts as a generic solution for building feature pyramids inside deep convolutional networks to be used in tasks like object detection.

The construction of the pyramid involves a bottom-up pathway and a top-down pathway.

The bottom-up pathway is the feedforward computation of the backbone ConvNet, which computes a feature hierarchy consisting of feature maps at several scales with a scaling step of 2. For the feature pyramid, one pyramid level is defined for each stage. The output of the last layer of each stage is used as a reference set of feature maps. For ResNets we use the feature activations output by each stage’s last residual block.

The top-down pathway hallucinates higher resolution features by upsampling spatially coarser, but semantically stronger, feature maps from higher pyramid levels. These features are then enhanced with features from the bottom-up pathway via lateral connections. Each lateral connection merges feature maps of the same spatial size from the bottom-up pathway and the top-down pathway. The bottom-up feature map is of lower-level semantics, but its activations are more accurately localized as it was subsampled fewer times.

Source: Feature Pyramid Networks for Object DetectionSee Code · facebookresearch/Detectron

In Syntology name not resolved (unknown_name). Other entries in Syntology's graph carry this name; the lookup's note below says what that means for this name.

From the lookup's note on this name: Nothing resolved to this name, but 2 entries in Syntology's graph carry it; the most cited is “Feature Pyramid Network (FPN)”, a method in the paper “Feature Pyramid Networks for Object Detection” (arXiv:1612.03144, 28,056 citations). The lookup reads this as a miss of its own name matching, not a gap in coverage: the graph holds the name under a spelling the lookup did not reach. For arXiv:1612.03144: its page on this site · ask the lookup about it.

Near matches the lookup lists, each a different name: E-FPN; A2-FPN; A3-FPN; AD-FPN; Retro-FPN; Dual-stream FPN (DS-FPN); Feature Pyramid Network (FPN); Feature Pyramid Network (FPN).

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: 583 · with a code link: 300 · where Syntology ran a sample: 68 (58 with a run with no instrument failure, 10 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (68 of 583 tagged: 58 with a run with no instrument failure, 10 where every run was a failure of Syntology's instrument)

Page 1 of 6: papers 1 to 100 of 583, 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 351 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
Object Detection342
object-detection311
Object192
Semantic Segmentation96
Instance Segmentation62
Segmentation60
Image Classification43
image-classification27
Data Augmentation25
GPU25
Classification23
Decoder23
Knowledge Distillation23
Autonomous Driving22
General Classification22
Real-Time Object Detection21
Text Classification19
Deep Learning18
Pedestrian Detection18
text-classification18

Usage over time archive 2025-07-28

Papers per year tagged with FPN: 2016 to 2025, peak 109 109 0 2016: 1 paper 2016 2017: 5 papers 2017 2018: 20 papers 2018 2019: 82 papers 2019 2020: 102 papers 2020 2021: 109 papers 2021 2022: 99 papers 2022 2023: 80 papers 2023 2024: 64 papers 2024 2025: 21 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (583 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

Feature Extractors

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