Browse State-of-the-Art › Real-Time Object Detection

Real-Time Object Detection

134 papers with code · 8 benchmarks · 9 datasets archive 2025-07-28

Computer Vision

Real-Time Object Detection is a computer vision task that involves identifying and locating objects of interest in real-time video sequences with fast inference while maintaining a base level of accuracy.

This is typically solved using algorithms that combine object detection and tracking techniques to accurately detect and track objects in real-time. They use a combination of feature extraction, object proposal generation, and classification to detect and localize objects of interest.

( Image credit: CenterNet )

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

8 leaderboard tables shown for this task, 8 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
COCO (Common Objects in Context) (82 rows) DEIM-D-FINE-X+ DEIM: DETR with Improved Matching for Fast Convergence code Syntology official (archive's flag): 9 ran · 9 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 1 honoured, 0 violated, 4 with no contract checked; 4 where Syntology's instrument failed) · 4 unverified Compare
Argoverse-HD (Full-Stack, Val) (4 rows) RL-Based Dynamic-Online Policy — — — Compare
PASCAL VOC 2007 (4 rows) YOLO You Only Look Once: Unified, Real-Time Object Detection code Syntology 89 ran (of which 27 constructed an object rather than computing a result; 58 with no instrument failure: 4 honoured, 4 violated, 50 with no contract checked; 31 where Syntology's instrument failed) · 59 unverified Compare
Argoverse-HD (Detection-Only, Test) (3 rows) YOLOX YOLOX: Exceeding YOLO Series in 2021 code Syntology community repositories only · 16 ran (of which 0 constructed an object rather than computing a result; 14 with no instrument failure: 0 honoured, 0 violated, 14 with no contract checked; 2 where Syntology's instrument failed) · 7 unverified Compare
Argoverse-HD (Full-Stack, Test) (3 rows) YOLOX YOLOX: Exceeding YOLO Series in 2021 code Syntology community repositories only · 16 ran (of which 0 constructed an object rather than computing a result; 14 with no instrument failure: 0 honoured, 0 violated, 14 with no contract checked; 2 where Syntology's instrument failed) · 7 unverified Compare
Argoverse-HD (Detection-Only, Val) (2 rows) YOLOX YOLOX: Exceeding YOLO Series in 2021 code Syntology community repositories only · 16 ran (of which 0 constructed an object rather than computing a result; 14 with no instrument failure: 0 honoured, 0 violated, 14 with no contract checked; 2 where Syntology's instrument failed) · 7 unverified Compare
COCO (1 row) Mask R-CNN X-152-32x8d Mask R-CNN code Syntology 101 ran (of which 3 constructed an object rather than computing a result; 77 with no instrument failure: 2 honoured, 1 violated, 74 with no contract checked; 24 where Syntology's instrument failed) · 39 unverified Compare
PASCAL VOC 2007 (15+5) (1 row) Faster R-CNN Faster R-CNN: Towards Real-Time Object Detection with Region... code Syntology community repositories only · 79 ran (of which 9 constructed an object rather than computing a result; 47 with no instrument failure: 18 honoured, 5 violated, 24 with no contract checked; 32 where Syntology's instrument failed) · 45 unverified Compare

Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “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. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is 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. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

9 datasets whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

No subtask under this task in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 259 · with a code link: 134 · where Syntology ran a sample: 45 (43 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 (45 of 259 tagged: 43 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 259, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “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 figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. 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); hover it for the repositories the samples that ran came from. The first sentence of the abstract is shown for the first 30 papers; every abstract is on its paper's page.

Syntology lines on 41 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

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