Papers › Composed Image Retrieval with Text Feedback via Multi-grained Uncertainty Regularization

Composed Image Retrieval with Text Feedback via Multi-grained Uncertainty Regularization

14 Nov 2022arXiv:2211.07394archive 2025-07-28

Yiyang Chen, Zhedong Zheng, Wei Ji, Leigang Qu, Tat-Seng Chua

We investigate composed image retrieval with text feedback. Users gradually look for the target of interest by moving from coarse to fine-grained feedback. However, existing methods merely focus on the latter, i.e., fine-grained search, by harnessing positive and negative pairs during training. This pair-based paradigm only considers the one-to-one distance between a pair of specific points, which is not aligned with the one-to-many coarse-grained retrieval process and compromises the recall rate. In an attempt to fill this gap, we introduce a unified learning approach to simultaneously modeling the coarse- and fine-grained retrieval by considering the multi-grained uncertainty. The key idea underpinning the proposed method is to integrate fine- and coarse-grained retrieval as matching data points with small and large fluctuations, respectively. Specifically, our method contains two modules: uncertainty modeling and uncertainty regularization. (1) The uncertainty modeling simulates the multi-grained queries by introducing identically distributed fluctuations in the feature space. (2) Based on the uncertainty modeling, we further introduce uncertainty regularization to adapt the matching objective according to the fluctuation range. Compared with existing methods, the proposed strategy explicitly prevents the model from pushing away potential candidates in the early stage, and thus improves the recall rate. On the three public datasets, i.e., FashionIQ, Fashion200k, and Shoes, the proposed method has achieved +4.03%, +3.38%, and +2.40% Recall@50 accuracy over a strong baseline, respectively.

PaperPDFCodeCode 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 10 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 10 samples from 1 repository, 10 ran (7 with no instrument failure; 3 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 between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

Monoxide-Chen/uncertainty_retrieval officialmentioned in papermentioned on GitHubpytorchMITSyntology: 10 samples, 10 ran (3 instrument-failed) · 0 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

10 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
3ran · our draft was wrong
6ran

Licence: 6 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. For 6 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from Monoxide-Chen/uncertainty_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.

Monoxide-Chen/uncertainty_retrieval official repository 10 samples, 10 ran (3 instrument-failed) · 0 unverified
calculate_mean_std in 7 papers models/utils.py ran fingerprinted MIT (permissive) here; the stored copy is pointer only · 77dc755eec4b339c · report fixture: signature x:Tensor/4/float · returned tuple · level recorded 2026-09-24
create_experiment_export_folder set_up.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 7657330ca2d9594a · report fixture: signature experiment_dir:str/0/str, experiment_description:str/0/str · returned str · level recorded 2026-09-25
create_lr_schedulers optimizers.py ran MIT (permissive) · 6cad2a4ad3a87d25 · report fixture: signature optimizers:dict/0/?, config:dict/0/? · returned dict · level recorded 2026-09-25
create_optimizers optimizers.py ran MIT (permissive) · fffafb2f1a4e975d · report fixture: signature models:dict/0/?, config:dict/0/? · returned dict · level recorded 2026-09-25
create_read_func language/utils.py ran MIT (permissive) · 6e93e17cdd292238 · report fixture: signature vocab_path:str/0/str · returned function · level recorded 2026-09-25
create_write_func language/utils.py ran MIT (permissive) · aac3a343da033f5d · report fixture: signature vocab_path:str/0/str · returned function · level recorded 2026-09-25
equal_lr in 11 papers models/utils.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 82c40579a3041ca0 · report fixture: signature module:callable/0/?, name:str/0/str · returned Linear · level recorded 2026-09-22
fix_random_seed_as set_up.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only · 15df572f14aa3ffb · report fixture: signature random_seed:int/0/int · returned int · level recorded 2026-09-25
get_name_of_experiment_path set_up.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 465d0cb5ececdb3e · report fixture: signature experiment_dir:str/0/str, experiment_description:str/0/str · returned str · level recorded 2026-09-25
reshape_text_features_to_concat models/utils.py ran MIT (permissive) here; the stored copy is pointer only · 68994a7ec705cdf0 · report fixture: signature text_features:Tensor/2/float, image_features_shapes:tuple/1/int · returned Tensor · level recorded 2026-09-24

Tasks

Composed Image Retrieval (CoIR)Image RetrievalImage Retrieval with Multi-Modal QueryRetrieval

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Image Retrieval Fashion IQ MUR (4*ResNet50) (Recall@10+Recall@50)/2 50.61 #13 of 22 Archive leaderboard report
Image Retrieval Fashion IQ MUR (Recall@10+Recall@50)/2 47.28 #15 of 22 Archive leaderboard report
Image Retrieval with Multi-Modal Query Fashion200k Multi-grained Uncertainty Regularization(MUR) Recall@1 21.8 #3 of 8 Archive leaderboard report
Image Retrieval with Multi-Modal Query Fashion200k Multi-grained Uncertainty Regularization(MUR) Recall@10 52.1 #3 of 8 Archive leaderboard report
Image Retrieval with Multi-Modal Query Fashion200k Multi-grained Uncertainty Regularization(MUR) Recall@50 70.2 #3 of 8 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.

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