Papers › The Devil is in the Spurious Correlation: Boosting Moment Retrieval via Temporal...

The Devil is in the Spurious Correlation: Boosting Moment Retrieval via Temporal Dynamic Learning

13 Jan 2025arXiv:2501.07305archive 2025-07-28

Xinyang Zhou, Fanyue Wei, Lixin Duan, Wen Li

Given a textual query along with a corresponding video, the objective of moment retrieval aims to localize the moments relevant to the query within the video. While commendable results have been demonstrated by existing transformer-based approaches, predicting the accurate temporal span of the target moment is currently still a major challenge. In this paper, we reveal that a crucial reason stems from the spurious correlation between the text queries and the moment context. Namely, the model may associate the textual query with the background frames rather than the target moment. To address this issue, we propose a temporal dynamic learning approach for moment retrieval, where two strategies are designed to mitigate the spurious correlation. First, we introduce a novel video synthesis approach to construct a dynamic context for the relevant moment. With separate yet similar videos mixed up, the synthesis approach empowers our model to attend to the target moment of the corresponding query under various dynamic contexts. Second, we enhance the representation by learning temporal dynamics. Besides the visual representation, text queries are aligned with temporal dynamic representations, which enables our model to establish a non-spurious correlation between the query-related moment and context. With the aforementioned proposed method, the spurious correlation issue in moment retrieval can be largely alleviated. Our method establishes a new state-of-the-art performance on two popular benchmarks of moment retrieval, i.e., QVHighlights and Charades-STA. In addition, the detailed ablation analyses demonstrate the effectiveness of the proposed strategies. Our code will be publicly available.

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

By repository: found in paper text by Syntology: 11 samples from 1 repository, 8 ran (4 with no instrument failure; 4 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.

xyangzhou/TD-DETR found in paper text by SyntologyMITSyntology: 11 samples, 8 ran (4 instrument-failed) · 3 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

11 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 1 violated, 2 with no contract checked; 4 where Syntology's instrument failed) · 3 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
1ran · violated contract
4ran · our draft was wrong
2ran
3unverified

Licence: 8 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. For 8 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 xyangzhou/TD-DETR. “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.

xyangzhou/TD-DETR found in paper text by Syntology 11 samples, 8 ran (4 instrument-failed) · 3 unverified
build_position_encoding in 42 papers td_detr/position_encoding.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · d6ca656c20df137a · report fixture: signature args:ArgsConfig/0/? · returned tuple · level recorded 2026-09-24
count_parameters in 278 papers utils/model_utils.py ran · honoured contract MIT (permissive) here; the stored copy is pointer only · edb929dece68582e · report fixture: signature model:callable/0/?, verbose:bool/0/bool · returned tuple · level recorded 2026-09-25
gen_sineembed_for_position in 29 papers td_detr/transformer.py ran fingerprinted MIT (permissive) · ef58ba4fdac7256e · report fixture: signature pos_tensor:Tensor/3/float · returned Tensor · level recorded 2026-09-24
inverse_sigmoid in 80 papers
census: 9 implementations from 14 papers, 5 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 2, kind float, dtype float32
td_detr/model.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 6897880b6ce14c94 · report fixture: signature x:Tensor/2/float, eps:float/0/float · returned Tensor · level recorded 2026-09-22
prepare_batch_inputs in 11 papers td_detr/start_end_dataset.py ran MIT (permissive) · ba9fbbf6b2237b8d · report fixture: signature batched_model_inputs:dict/0/?, device:str/0/str, non_blocking:bool/0/bool · returned tuple · level recorded 2026-09-24
span_cxw_to_xx in 10 papers td_detr/span_utils.py ran · violated contract fingerprinted MIT (permissive) here; the stored copy is pointer only · b7639c2e8b83837b · report fixture: signature cxw_spans:Tensor/2/float · returned Tensor · level recorded 2026-09-22
span_xx_to_cxw in 10 papers td_detr/span_utils.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 7114f025044af9b4 · report fixture: signature xx_spans:Tensor/2/float · returned Tensor · level recorded 2026-09-25
temporal_iou in 10 papers td_detr/span_utils.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · e4ae5582a2533cdb · report fixture: signature spans1:Tensor/2/float, spans2:Tensor/2/float · returned tuple · level recorded 2026-09-25
accuracy in 872 papers
census: 8 implementations from 7 papers, 7 distinct outputs across 6 buckets, one shared input per bucket
td_detr/misc.py unverified MIT (permissive) here; the stored copy is pointer only · 081c8abd57d082fd · report
build_transformer in 62 papers td_detr/transformer.py unverified MIT (permissive) · 595b7178ce4c0616 · report
multi_head_attention_forward in 73 papers td_detr/attention.py unverified MIT (permissive) here; the stored copy is pointer only · a82091666b9db8cf · report

Tasks

Moment RetrievalRetrieval

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