Papers › Magic Tokens: Select Diverse Tokens for Multi-modal Object Re-Identification

Magic Tokens: Select Diverse Tokens for Multi-modal Object Re-Identification

15 Mar 2024CVPR 2024 1arXiv:2403.10254archive 2025-07-28

Pingping Zhang, Yuhao Wang, Yang Liu, Zhengzheng Tu, Huchuan Lu

Single-modal object re-identification (ReID) faces great challenges in maintaining robustness within complex visual scenarios. In contrast, multi-modal object ReID utilizes complementary information from diverse modalities, showing great potentials for practical applications. However, previous methods may be easily affected by irrelevant backgrounds and usually ignore the modality gaps. To address above issues, we propose a novel learning framework named EDITOR to select diverse tokens from vision Transformers for multi-modal object ReID. We begin with a shared vision Transformer to extract tokenized features from different input modalities. Then, we introduce a Spatial-Frequency Token Selection (SFTS) module to adaptively select object-centric tokens with both spatial and frequency information. Afterwards, we employ a Hierarchical Masked Aggregation (HMA) module to facilitate feature interactions within and across modalities. Finally, to further reduce the effect of backgrounds, we propose a Background Consistency Constraint (BCC) and an Object-Centric Feature Refinement (OCFR). They are formulated as two new loss functions, which improve the feature discrimination with background suppression. As a result, our framework can generate more discriminative features for multi-modal object ReID. Extensive experiments on three multi-modal ReID benchmarks verify the effectiveness of our methods. The code is available at https://github.com/924973292/EDITOR.

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

924973292/editor officialmentioned in papermentioned on GitHubpytorchMITSyntology: 4 samples, 3 ran (3 instrument-failed) · 1 unverified report
924973292/fusionreid mentioned on GitHubpytorchSyntology: 7 samples, 6 ran (0 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

11 samples harvested: 9 ran (of which 5 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 3 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 last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran · our draft was wrong
6ran
2unverified

Licence: 9 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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”. For 1 sample that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

924973292/editor official repository 4 samples, 3 ran (3 instrument-failed) · 1 unverified
cosine_dist in 25 papers layers/triplet_loss.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 71b4e1d375d8fd78 · report fixture: signature x:Tensor/2/float, y:Tensor/2/float · returned Tensor · level recorded 2026-09-25
euclidean_dist in 69 papers
census: 12 implementations from 14 papers, 3 distinct outputs on one shared input
layers/triplet_loss.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 5315f75bf5367f0a · report fixture: signature x:Tensor/2/float, y:Tensor/2/float · returned Tensor · level recorded 2026-09-25
normalize in 638 papers
census: 70 implementations from 82 papers, 51 distinct outputs across 11 buckets, one shared input per bucket this sample: bucket 1 of 11, arg 1: rank 2, kind float, dtype float32
layers/triplet_loss.py ran · our draft was wrong fingerprinted MIT (permissive) · e3b2a83f52101f2d · report fixture: signature x:Tensor/2/float, axis:int/0/int · returned Tensor · level recorded 2026-09-22
make_loss in 17 papers layers/make_loss.py unverified MIT (permissive) · 2e6109d5214f6e2a · report
924973292/fusionreid community (archive-listed) 7 samples, 6 ran (0 instrument-failed) · 1 unverified
Attention in 344 papers
census: 13 implementations from 12 papers, 10 distinct outputs across 4 buckets, one shared input per bucket
modeling/fusion_part/fusion.py ran no licence file found · pointer only · 4f2b5c4adcb39a83 · report fixture: signature x:Tensor/3/float, get_attn:bool/0/bool · returned Tensor · level recorded 2026-09-24
Attention_mix modeling/fusion_part/fusion.py ran · metamorphic tier: deterministic no licence file found · pointer only · 4800b901068d9f8f · report fixture: returned Attention_mix · level recorded 2026-09-22
Block in 252 papers
census: 5 implementations from 5 papers, 3 distinct outputs across 2 buckets, one shared input per bucket
modeling/fusion_part/fusion.py ran · metamorphic tier: deterministic no licence file found · pointer only · cd31ba10bfe67622 · report fixture: returned Block · level recorded 2026-09-22
Block_mix modeling/fusion_part/fusion.py ran · metamorphic tier: deterministic no licence file found · pointer only · 21b633fce8142a7c · report fixture: returned Block_mix · level recorded 2026-09-22
Mutual_Fsuion_Unit modeling/fusion_part/fusion.py ran · metamorphic tier: deterministic no licence file found · pointer only · 74e30c9a44099a4e · report fixture: returned Mutual_Fsuion_Unit · level recorded 2026-09-22
Shared_Encoding_Unit modeling/fusion_part/fusion.py ran · metamorphic tier: deterministic no licence file found · pointer only · ab8e0fc65383467b · report fixture: returned Shared_Encoding_Unit · level recorded 2026-09-22
Reflection_item modeling/fusion_part/fusion.py unverified no licence file found · pointer only · 9558cd4a63752d5e · 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 Spatial-Frequency Token Selection (SFTS) (graph method: Hierarchical Masked Aggregation (HMA)). 10 bricks; individually on a fixture: 9 ran (of which 7 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

  1. Reflection_item entry · level 0 · unverified · 9558cd4a63752d5e
  2. Mutual_Fsuion_Unit model · level 1 · ran · 74e30c9a44099a4e
  3. Shared_Encoding_Unit model · level 1 · ran · ab8e0fc65383467b
  4. Block_mix model · level 1 · ran · 21b633fce8142a7c
  5. Block helper · level 1 · ran · cd31ba10bfe67622
  6. Attention_mix model · level 1 · ran · 4800b901068d9f8f
  7. DropPath helper · level 1 · ran · 691dde70dfd8362b
  8. Mlp helper · level 1 · ran · a1715055832f71fd
  9. drop_path helper · level 1 · ran; the contract check could not run · 39eace7e2822504f
  10. Attention helper · level 1 · ran · 4f2b5c4adcb39a83

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="2403.10254") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Object

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformerVision Transformer

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