Methods › Computer Vision › Object Detection Models › RepPoints
RepPoints
Introduced by Ze Yang et al. in RepPoints: Point Set Representation for Object Detection
archive 2025-07-28 Description, source and code snippet are the archive's method entry.
RepPoints is a representation for object detection that consists of a set of points which indicate the spatial extent of an object and semantically significant local areas. This representation is learned via weak localization supervision from rectangular ground-truth boxes and implicit recognition feedback. Based on the richer RepPoints representation, the authors develop an anchor-free object detector that yields improved performance compared to using bounding boxes.
In Syntology harvested code stored, below machine verification (unverified_code; harvested), served level V1; retrieve with get_harvested_code_for_paper(arxiv_id='1904.11490'). Repositories: 6 listed of 6 in the graph, strongest link: official. The lookup matched a paper by its title, arXiv:1904.11490, not a method entry. This answer is about arXiv:1904.11490, the paper the archive credits with this method.
Origin paper of this answer, arXiv:1904.11490 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 3 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 0 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified (of 3 harvested samples) · 3 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: 11 · with a code link: 6 · where Syntology ran a sample: 3 (3 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (3 of 11 tagged: 3 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Page 1 of 1: papers 1 to 11 of 11, 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.
-
Dual Scale-aware Adaptive Masked Knowledge Distillation for Object Detection 13 Jan 2025 · 0 repositories · arXiv:2501.07101
-
CNN based Cuneiform Sign Detection Learned from Annotated 3D Renderings and Mapped Photographs with Illumination Augmentation 22 Aug 2023 · 0 repositories · arXiv:2308.11277
-
AMD: Adaptive Masked Distillation for Object Detection 31 Jan 2023 · 0 repositories · arXiv:2301.13538
-
Sample hardness based gradient loss for long-tailed cervical cell detection 7 Aug 2022 · 0 repositories · arXiv:2208.03779
-
Point RCNN: An Angle-Free Framework for Rotated Object Detection 28 May 2022 · 0 repositories · arXiv:2205.14328
-
Focal and Global Knowledge Distillation for Detectors 23 Nov 2021 · 1 repository · arXiv:2111.11837
-
Oriented RepPoints for Aerial Object Detection 24 May 2021 · 2 repositories · arXiv:2105.11111Syntology community repositories only · 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified (of 2 harvested samples)
-
RelationNet++: Bridging Visual Representations for Object Detection via Transformer Decoder 29 Oct 2020 · 4 repositories · arXiv:2010.15831Syntology official (archive's flag): 4 ran · 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified (of 5 harvested samples)
-
RepPoints V2: Verification Meets Regression for Object Detection 16 Jul 2020 · 1 repository · arXiv:2007.08508
-
Dense RepPoints: Representing Visual Objects with Dense Point Sets 24 Dec 2019 · 2 repositories · arXiv:1912.11473
-
RepPoints: Point Set Representation for Object Detection 25 Apr 2019 · 6 repositories · arXiv:1904.11490Syntology community repositories only · 3 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 0 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified (of 3 harvested samples) · 3 pointer-only (licence)
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.
Usage over time archive 2025-07-28
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
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