Papers › How to Evaluate the Generalization of Detection? A Benchmark for Comprehensive...

How to Evaluate the Generalization of Detection? A Benchmark for Comprehensive Open-Vocabulary Detection

25 Aug 2023arXiv:2308.13177archive 2025-07-28

Yiyang Yao, Peng Liu, Tiancheng Zhao, Qianqian Zhang, Jiajia Liao, Chunxin Fang, Kyusong Lee, Qing Wang

Object detection (OD) in computer vision has made significant progress in recent years, transitioning from closed-set labels to open-vocabulary detection (OVD) based on large-scale vision-language pre-training (VLP). However, current evaluation methods and datasets are limited to testing generalization over object types and referral expressions, which do not provide a systematic, fine-grained, and accurate benchmark of OVD models' abilities. In this paper, we propose a new benchmark named OVDEval, which includes 9 sub-tasks and introduces evaluations on commonsense knowledge, attribute understanding, position understanding, object relation comprehension, and more. The dataset is meticulously created to provide hard negatives that challenge models' true understanding of visual and linguistic input. Additionally, we identify a problem with the popular Average Precision (AP) metric when benchmarking models on these fine-grained label datasets and propose a new metric called Non-Maximum Suppression Average Precision (NMS-AP) to address this issue. Extensive experimental results show that existing top OVD models all fail on the new tasks except for simple object types, demonstrating the value of the proposed dataset in pinpointing the weakness of current OVD models and guiding future research. Furthermore, the proposed NMS-AP metric is verified by experiments to provide a much more truthful evaluation of OVD models, whereas traditional AP metrics yield deceptive results. Data is available at \url{https://github.com/om-ai-lab/OVDEval}

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology: its repositories, every harvested function with whether it ran, its licence and the call to fetch it.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2308.13177")

Code

Syntology Ran 10 of 10 code samples harvested from 2 repositories linked to this paper; 0 have no recorded run. Of those that ran: 2 ran · our draft was wrong; 1 ran · fixture could not drive it; 7 ran with no contract checked.

By repository: official repository: 2 samples from 1 repository, 2 ran; community (archive-listed): 8 samples from 1 repository, 8 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

om-ai-lab/ovdeval officialmentioned in papermentioned on GitHubpytorchApache-2.0 report
om-ai-lab/OmAgent mentioned on GitHubApache-2.0 report
om-ai-lab/OmDet mentioned on GitHubpytorchApache-2.0 report
om-ai-lab/ZoomEye mentioned on GitHubpytorch report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

10 samples harvested; 10 ran; 0 honoured the contract we drafted; 0 have no recorded run. Read from Syntology's graph 2026-09-25; that is when this build read the record, not when the samples ran.

2ran · our draft was wrong
1ran · fixture could not drive it
7ran

Licence: 0 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; each sample names its own and says which. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

calculate_iou om-ai-lab/ovdeval/eval_glip.py official repository ran Apache-2.0 (permissive) · f37e6f7d03c74102 · report
nms_threaded om-ai-lab/ovdeval/eval_glip.py official repository ran Apache-2.0 (permissive) · bdd48ffb812ebe9b · report
apply_deltas om-ai-lab/OmDet/omdet/modeling/common.py community (archive-listed) ran Apache-2.0 (permissive) · 3e006b27eb5131f9 · report
conv3x3 om-ai-lab/OmDet/omdet/modeling/backbone/dlafpn.py community (archive-listed) ran · our draft was wrong Apache-2.0 (permissive) · dd1114865f06f0fd · report
get_fpn_config om-ai-lab/OmDet/omdet/modeling/backbone/bifpn.py community (archive-listed) ran fingerprinted Apache-2.0 (permissive) · 7e97d239afcab15e · report
get_model_url om-ai-lab/OmDet/omdet/modeling/backbone/dlafpn.py community (archive-listed) ran fingerprinted Apache-2.0 (permissive) · 738b4871dc26c54f · report
get_output_shape om-ai-lab/OmDet/omdet/inference/base_engine.py community (archive-listed) ran Apache-2.0 (permissive) · 9c966a0badf6f168 · report
swish om-ai-lab/OmDet/omdet/modeling/backbone/bifpn.py community (archive-listed) ran fingerprinted Apache-2.0 (permissive) · 717e4d22b6d103e6 · report
window_partition om-ai-lab/OmDet/omdet/modeling/backbone/swint.py community (archive-listed) ran · fixture could not drive it fingerprinted Apache-2.0 (permissive) · f9fd6241d935f07b · report
window_reverse om-ai-lab/OmDet/omdet/modeling/backbone/swint.py community (archive-listed) ran · our draft was wrong Apache-2.0 (permissive) · fb32094c6dbece71 · report

Tasks

Object Detection

Datasets

Introduced by this paper, per the archive.

OVDEval

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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