Methods › Computer Vision › One-Stage Object Detection Models › CenterNet

CenterNet

47 papers tagged archive 2025-07-28

Introduced by Kaiwen Duan et al. in CenterNet: Keypoint Triplets for Object Detection

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

CenterNet is a one-stage object detector that detects each object as a triplet, rather than a pair, of keypoints. It utilizes two customized modules named cascade corner pooling and center pooling, which play the roles of enriching information collected by both top-left and bottom-right corners and providing more recognizable information at the central regions, respectively. The intuition is that, if a predicted bounding box has a high IoU with the ground-truth box, then the probability that the center keypoint in its central region is predicted as the same class is high, and vice versa. Thus, during inference, after a proposal is generated as a pair of corner keypoints, we determine if the proposal is indeed an object by checking if there is a center keypoint of the same class falling within its central region.

PaperSourceSee Code · Duankaiwen/CenterNet

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

Origin paper of this answer, arXiv:1904.08189 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 9 unverified (of 11 harvested samples) · 4 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: 47 · with a code link: 16 · where Syntology ran a sample: 3 (2 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 (3 of 47 tagged: 2 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 47 of 47, 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 70 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 Detection31
object-detection29
Object18
Pose Estimation5
Keypoint Detection3
Representation Learning3
Semantic Segmentation3
Transfer Learning3
Clothes Landmark Detection2
Decoder2
Depth Estimation2
Domain Adaptation2
Instance Segmentation2
Keypoint Estimation2
Object Detection In Aerial Images2
Object Tracking2
Super-Resolution2
Triplet2
Unsupervised Domain Adaptation2
2D Human Pose Estimation1

Usage over time archive 2025-07-28

Papers per year tagged with CenterNet: 2019 to 2025, peak 10 10 0 2019: 5 papers 2019 2020: 8 papers 2020 2021: 10 papers 2021 2022: 8 papers 2022 2023: 6 papers 2023 2024: 9 papers 2024 2025: 1 paper 2025
Papers per year the archive tags with this method, by the paper's archive date (47 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

One-Stage Object Detection ModelsObject Detection 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