Papers › CORA: Adapting CLIP for Open-Vocabulary Detection with Region Prompting and Anchor Pre-Matching

CORA: Adapting CLIP for Open-Vocabulary Detection with Region Prompting and Anchor Pre-Matching

23 Mar 2023CVPR 2023 1arXiv:2303.13076archive 2025-07-28

Xiaoshi Wu, Feng Zhu, Rui Zhao, Hongsheng Li

Open-vocabulary detection (OVD) is an object detection task aiming at detecting objects from novel categories beyond the base categories on which the detector is trained. Recent OVD methods rely on large-scale visual-language pre-trained models, such as CLIP, for recognizing novel objects. We identify the two core obstacles that need to be tackled when incorporating these models into detector training: (1) the distribution mismatch that happens when applying a VL-model trained on whole images to region recognition tasks; (2) the difficulty of localizing objects of unseen classes. To overcome these obstacles, we propose CORA, a DETR-style framework that adapts CLIP for Open-vocabulary detection by Region prompting and Anchor pre-matching. Region prompting mitigates the whole-to-region distribution gap by prompting the region features of the CLIP-based region classifier. Anchor pre-matching helps learning generalizable object localization by a class-aware matching mechanism. We evaluate CORA on the COCO OVD benchmark, where we achieve 41.7 AP50 on novel classes, which outperforms the previous SOTA by 2.4 AP50 even without resorting to extra training data. When extra training data is available, we train CORA^+ on both ground-truth base-category annotations and additional pseudo bounding box labels computed by CORA. CORA^+ achieves 43.1 AP50 on the COCO OVD benchmark and 28.1 box APr on the LVIS OVD benchmark.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

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

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 3 code samples harvested from 1 repository linked to this paper: 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) · 1 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: official repository: 3 samples from 1 repository, 2 ran (0 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

tgxs002/cora officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 3 samples, 2 ran (2 instrument-failed) · 1 unverified 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

3 samples harvested: 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) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
1ran; the contract check could not run
1unverified

Licence: 0 of the 3 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 tgxs002/cora. “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. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (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 are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. 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 six 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; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. 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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

tgxs002/cora official repository 3 samples, 2 ran (2 instrument-failed) · 1 unverified
gen_sineembed_for_position in 29 papers models/fast_detr.py ran; the contract check could not run (RAISES) fingerprinted Apache-2.0 (permissive) · 1455637eb5d8b21d · report fixture: signature pos_tensor:Tensor/3/float · returned Tensor · level recorded 2026-09-22
nested_tensor_from_tensor_list in 60 papers models/fast_detr.py ran · our draft was wrong Apache-2.0 (permissive) · 6c586ce97f1675d6 · report fixture: signature tensor_list:list/1/Tensor · returned NestedTensor · level recorded 2026-09-22
FastDETR models/fast_detr.py unverified Apache-2.0 (permissive) · 465f0a217286c663 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for CORA (graph method: CORA). 12 bricks; individually on a fixture: 10 ran (of which 2 constructed an object rather than computing a result; 5 with no instrument failure: 3 honoured, 0 violated, 2 with no contract checked; 5 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

  1. FastDETR entry · level 0 · unverified · 465f0a217286c663
  2. MLP helper · level 1 · ran · 1630454d42cd8f1e
  3. NestedTensor helper · level 1 · ran · b636bcda4557023e
  4. _get_clones helper · level 1 · ran · our draft was wrong · a8f1bbeb369e1829
  5. box_cxcywh_to_xyxy helper · level 1 · ran · honoured contract · e0a06ded5d4f6c3c
  6. box_iou helper · level 1 · ran · honoured contract · ce749f837424dd8c
  7. gen_sineembed_for_position helper · level 1 · ran; the contract check could not run (RAISES) · 1455637eb5d8b21d
  8. generalized_box_iou helper · level 1 · ran; the contract check could not run · dc8fb9b6fb48ac37
  9. inverse_sigmoid helper · level 1 · ran · our draft was wrong · 83c03ceb1307c6c4
  10. nested_tensor_from_tensor_list helper · level 1 · ran · our draft was wrong · 6c586ce97f1675d6
  11. _max_by_axis helper · level 1 · ran · honoured contract · ef393284ce3c9ea1
  12. _onnx_nested_tensor_from_tensor_list helper · level 0 · unverified · 0ff86335d5b895ad

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2303.13076") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Described Object DetectionObject DetectionObject LocalizationOpen Vocabulary Object Detectionobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Described Object Detection Description Detection Dataset CORA-R50 Intra-scenario ABS mAP 5.0 #8 of 8 Archive leaderboard report
Described Object Detection Description Detection Dataset CORA-R50 Intra-scenario FULL mAP 6.2 #8 of 8 Archive leaderboard report
Described Object Detection Description Detection Dataset CORA-R50 Intra-scenario PRES mAP 6.7 #8 of 8 Archive leaderboard report
Open Vocabulary Object Detection MSCOCO CORA+ AP 0.5 43.1 #8 of 32 Archive leaderboard report
Open Vocabulary Object Detection MSCOCO CORA AP 0.5 41.7 #11 of 32 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

BASECLIP

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