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

YOLOv3

258 papers tagged archive 2025-07-28

Introduced by Joseph Redmon et al. in YOLOv3: An Incremental Improvement

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

YOLOv3 is a real-time, single-stage object detection model that builds on YOLOv2 with several improvements. Improvements include the use of a new backbone network, Darknet-53 that utilises residual connections, or in the words of the author, "those newfangled residual network stuff", as well as some improvements to the bounding box prediction step, and use of three different scales from which to extract features (similar to an FPN).

PaperSourceSee Code · pjreddie/darknet

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

Origin paper of this answer, arXiv:1804.02767 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 94 ran (of which 0 constructed an object rather than computing a result; 82 with no instrument failure: 7 honoured, 2 violated, 73 with no contract checked; 12 where Syntology's instrument failed) · 30 unverified (of 124 harvested samples) · 24 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: 258 · with a code link: 98 · where Syntology ran a sample: 13 (11 with a run with no instrument failure, 2 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (13 of 258 tagged: 11 with a run with no instrument failure, 2 where every run was a failure of Syntology's instrument)

Page 1 of 3: papers 1 to 100 of 258, 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 191 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 Detection151
object-detection141
Object77
Autonomous Driving20
Real-Time Object Detection18
Data Augmentation14
Deep Learning14
Semantic Segmentation13
GPU12
Transfer Learning10
Classification9
Image Classification9
image-classification9
Pedestrian Detection8
Segmentation8
Instance Segmentation7
2D Object Detection6
Autonomous Vehicles6
Defect Detection6
General Classification6

Usage over time archive 2025-07-28

Papers per year tagged with YOLOv3: 2016 to 2025, peak 59 59 0 2016: 1 paper 2016 2017: 0 papers 2017 2018: 3 papers 2018 2019: 23 papers 2019 2020: 52 papers 2020 2021: 54 papers 2021 2022: 59 papers 2022 2023: 35 papers 2023 2024: 22 papers 2024 2025: 9 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (258 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