Papers › PRVQL: Progressive Knowledge-guided Refinement for Robust Egocentric Visual Query Localization

PRVQL: Progressive Knowledge-guided Refinement for Robust Egocentric Visual Query Localization

11 Feb 2025arXiv:2502.07707archive 2025-07-28

Bing Fan, Yunhe Feng, Yapeng Tian, Yuewei Lin, Yan Huang, Heng Fan

Egocentric visual query localization (EgoVQL) focuses on localizing the target of interest in space and time from first-person videos, given a visual query. Despite recent progressive, existing methods often struggle to handle severe object appearance changes and cluttering background in the video due to lacking sufficient target cues, leading to degradation. Addressing this, we introduce PRVQL, a novel Progressive knowledge-guided Refinement framework for EgoVQL. The core is to continuously exploit target-relevant knowledge directly from videos and utilize it as guidance to refine both query and video features for improving target localization. Our PRVQL contains multiple processing stages. The target knowledge from one stage, comprising appearance and spatial knowledge extracted via two specially designed knowledge learning modules, are utilized as guidance to refine the query and videos features for the next stage, which are used to generate more accurate knowledge for further feature refinement. With such a progressive process, target knowledge in PRVQL can be gradually improved, which, in turn, leads to better refined query and video features for localization in the final stage. Compared to previous methods, our PRVQL, besides the given object cues, enjoys additional crucial target information from a video as guidance to refine features, and hence enhances EgoVQL in complicated scenes. In our experiments on challenging Ego4D, PRVQL achieves state-of-the-art result and largely surpasses other methods, showing its efficacy. Our code, model and results will be released at https://github.com/fb-reps/PRVQL.

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 13 code samples harvested from 1 repository linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 2 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 2 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, 11 ran (11 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 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.

fb-reps/prvql officialmentioned in paperpytorchMITSyntology: 13 samples, 11 ran (0 instrument-failed) · 2 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: 11 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 2 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 2 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.

2ran · honoured contract
9ran
2unverified

Licence: 1 of the 13 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, 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 fb-reps/prvql. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

fb-reps/prvql official repository 13 samples, 11 ran (0 instrument-failed) · 2 unverified
extract_sub_modules_state_dict model/corr_clip_spatial_transformer2_anchor_2heads_hnm.py ran MIT (permissive) · e58720b43049fef2 · report fixture: signature checkpoint:dict/0/?, prefix:str/0/str · returned dict · level recorded 2026-09-24
format_predictions inference_results.py ran MIT (permissive) · fe7c2f09c012c022 · report fixture: signature annotations:dict/0/?, predicted_rts:dict/0/? · returned dict · level recorded 2026-09-24
gelu in 308 papers
census: 43 implementations from 74 papers, 6 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
bert_model/bert_module.py ran · honoured contract fingerprinted MIT (permissive) · 69e3a274f98c15af · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22
gelu_new in 55 papers
census: 3 implementations from 7 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32
bert_model/bert_module.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only · 77601724cad03f95 · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22
get_bbox_from_data dataset/base_dataset.py ran MIT (permissive) · 070d7eed4f22f51d · report fixture: signature data:dict/0/? · returned list · level recorded 2026-09-24
get_losses in 8 papers utils/loss_utils.py ran MIT (permissive) · 0e96da7c96574812 · report fixture: signature config:Config/0/?, preds:dict/0/?, gts:dict/0/? · returned dict · level recorded 2026-09-24
get_losses_head utils/loss_utils.py ran MIT (permissive) · 71ace89be308adbc · report fixture: signature config:Config/0/?, refine_prob:Tensor/2/float, gts:dict/0/?, preds_top:dict/0/? · returned tuple · level recorded 2026-09-24
positionalencoding1d in 8 papers utils/model_utils.py ran fingerprinted MIT (permissive) · bed1828c9c920325 · report fixture: signature d_model:int/0/int, length:int/0/int · returned Tensor · level recorded 2026-09-24
positionalencoding3d utils/model_utils.py ran MIT (permissive) · 5b821635ccbae36a · report fixture: signature d_model:int/0/int, height:int/0/int, width:int/0/int, depth:int/0/int, type:str/0/str · returned Tensor · level recorded 2026-09-24
replicate_sample_for_hnm dataset/dataset_utils.py ran MIT (permissive) · 379a559fff316790 · report fixture: signature gts:dict/0/? · returned dict · level recorded 2026-09-25
sample_frames_balance dataset/base_dataset.py ran MIT (permissive) · 68900fa3cd5db048 · report fixture: signature num_frames:int/0/int, query_frame:int/0/int, frame_interval:int/0/int, sample:dict/0/?, sampling:str/0/str · returned list · level recorded 2026-09-24
positionalencoding2d in 17 papers utils/model_utils.py unverified MIT (permissive) · b2e8731183a22bb6 · report
process_data in 61 papers dataset/dataset_utils.py unverified MIT (permissive) · af0e3990e7f9effe · report

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