Methods › Computer Vision › Pooling Operations › Corner Pooling

Corner Pooling

12 papers tagged archive 2025-07-28

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

Corner Pooling is a pooling technique for object detection that seeks to better localize corners by encoding explicit prior knowledge. Suppose we want to determine if a pixel at location (i, j) is a top-left corner. Let fₜ and fₗ be the feature maps that are the inputs to the top-left corner pooling layer, and let f_(tᵢⱼ) and f_(lᵢⱼ) be the vectors at location (i, j) in fₜ and fₗ respectively. With H ×W feature maps, the corner pooling layer first max-pools all feature vectors between (i, j) and (i, H) in fₜ to a feature vector tᵢⱼ , and max-pools all feature vectors between (i, j) and (W, j) in fₗ to a feature vector lᵢⱼ. Finally, it adds tᵢⱼ and lᵢⱼ together.

Source: CornerNet: Detecting Objects as Paired KeypointsSee Code · princeton-vl/CornerNet

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.

Near matches the lookup lists, each a different name: GMM Pooling; QKV Pooling; Style Pooling; adaptive pooling; LLaVA-SP-Pooling; new pooling method; Classifier Pooling; multi-track pooling.

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: 12 · with a code link: 8 · 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 12 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 12 of 12, 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

19 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 Detection8
object-detection8
Object7
Keypoint Estimation2
Region Proposal2
Chart Understanding1
Decoder1
Deep Learning1
Instance Segmentation1
Management1
Metric Learning1
Position1
Real-Time Object Detection1
Semantic Segmentation1
Table Detection1
Table Recognition1
Triplet1
Visual Tracking1
Vocal Bursts Intensity Prediction1

Usage over time archive 2025-07-28

Papers per year tagged with Corner Pooling: 2018 to 2023, peak 3 3 0 2018: 1 paper 2018 2019: 3 papers 2019 2020: 3 papers 2020 2021: 2 papers 2021 2022: 1 paper 2022 2023: 2 papers 2023
Papers per year the archive tags with this method, by the paper's archive date (12 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

Pooling Operations

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