Papers › Towards Content-based Pixel Retrieval in Revisited Oxford and Paris

Towards Content-based Pixel Retrieval in Revisited Oxford and Paris

11 Sep 2023ICCV 2023 1arXiv:2309.05438archive 2025-07-28

Guoyuan An, Woo Jae Kim, Saelyne Yang, Rong Li, Yuchi Huo, Sung-Eui Yoon

This paper introduces the first two pixel retrieval benchmarks. Pixel retrieval is segmented instance retrieval. Like semantic segmentation extends classification to the pixel level, pixel retrieval is an extension of image retrieval and offers information about which pixels are related to the query object. In addition to retrieving images for the given query, it helps users quickly identify the query object in true positive images and exclude false positive images by denoting the correlated pixels. Our user study results show pixel-level annotation can significantly improve the user experience. Compared with semantic and instance segmentation, pixel retrieval requires a fine-grained recognition capability for variable-granularity targets. To this end, we propose pixel retrieval benchmarks named PROxford and PRParis, which are based on the widely used image retrieval datasets, ROxford and RParis. Three professional annotators label 5,942 images with two rounds of double-checking and refinement. Furthermore, we conduct extensive experiments and analysis on the SOTA methods in image search, image matching, detection, segmentation, and dense matching using our pixel retrieval benchmarks. Results show that the pixel retrieval task is challenging to these approaches and distinctive from existing problems, suggesting that further research can advance the content-based pixel-retrieval and thus user search experience. The datasets can be downloaded from this link (https://github.com/anguoyuan/Pixel_retrieval-Segmented_instance_retrieval).

PaperPDFConference PDFCodeCode Syntology ran

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 13 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 13 samples from 1 repository, 9 ran (9 with no instrument failure; 0 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

anguoyuan/pixel_retrieval-segmented_instance_retrieval officialmentioned in paperMITSyntology: 13 samples, 9 ran (0 instrument-failed) · 4 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

13 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures 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.

9ran
4unverified

Licence: 0 of the 13 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 anguoyuan/pixel_retrieval-segmented_instance_retrieval. “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.

anguoyuan/pixel_retrieval-segmented_instance_retrieval official repository 13 samples, 9 ran (0 instrument-failed) · 4 unverified
AdjustPositiveRanks evaluation_code/dataset.py ran fingerprinted MIT (permissive) · c96e035397093fbb · report fixture: signature positive_ranks:ndarray/1/int, junk_ranks:ndarray/1/int · returned ndarray · level recorded 2026-09-24
ParseEasyMediumHardGroundTruth evaluation_code/dataset.py ran MIT (permissive) · 6d4f93163998dcad · report fixture: signature ground_truth:list/1/dict · returned tuple · level recorded 2026-09-24
ReadDatasetFile evaluation_code/dataset.py ran MIT (permissive) · 62de237434a3a409 · report fixture: signature dataset_file_path:str/0/str · returned tuple · level recorded 2026-09-24
compute_ap in 13 papers evaluation_code/utils/evaluate_pixel.py ran MIT (permissive) · a07ad22c46aa3105 · report fixture: signature ranks:ndarray/1/int, nres:int/0/int · returned float64 · level recorded 2026-09-24
compute_iou in 68 papers evaluation_code/utils/iou_compute.py ran MIT (permissive) · 5c1d039685bafbdd · report fixture: signature test_points:list/1/list, gt_points:list/1/list, image:ndarray/3/int, type:str/0/str · returned tuple · level recorded 2026-09-24
compute_iou in 68 papers evaluation_code/utils/iou_compute_delg.py ran MIT (permissive) · 1a23c5e4a34671bf · report fixture: signature test_points:list/1/list, gt_points:list/1/list, image:ndarray/3/int, type:str/0/str · returned tuple · level recorded 2026-09-24
extract_bounding_box evaluation_code/utils/iou_compute.py ran MIT (permissive) · 66337892cc8301d2 · report fixture: signature image:ndarray/3/int, points:list/1/list · returned tuple · level recorded 2026-09-24
extract_segmentation evaluation_code/utils/iou_compute.py ran MIT (permissive) · bfea0e96f2e300a0 · report fixture: signature image:ndarray/3/int, points:list/1/list · returned tuple · level recorded 2026-09-24
wrong_items evaluation_code/utils/evaluate.py ran MIT (permissive) · 9131b0a6c9b5809e · report fixture: signature l:list/1/int, q:int/0/int, roxford:dict/0/? · returned tuple · level recorded 2026-09-24
compute_map evaluation_code/utils/evaluate_pixel.py unverified MIT (permissive) · e09f485327418d4c · report
compute_map evaluation_code/utils/evaluate_pixel.py unverified MIT (permissive) · 1380b78f9d584f36 · report
compute_map evaluation_code/utils/evaluate.py unverified MIT (permissive) · 9456f5818ed5a150 · report
name_list evaluation_code/utils/path_manage.py unverified MIT (permissive) · 15282d96802de39c · report

Tasks

Image RetrievalInstance SegmentationRetrievalSegmentationSemantic Segmentation

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