Papers › RLE: A Unified Perspective of Data Augmentation for Cross-Spectral Re-identification

RLE: A Unified Perspective of Data Augmentation for Cross-Spectral Re-identification

2 Nov 2024arXiv:2411.01225archive 2025-07-28

Lei Tan, Yukang Zhang, Keke Han, Pingyang Dai, Yan Zhang, Yongjian Wu, Rongrong Ji

This paper makes a step towards modeling the modality discrepancy in the cross-spectral re-identification task. Based on the Lambertain model, we observe that the non-linear modality discrepancy mainly comes from diverse linear transformations acting on the surface of different materials. From this view, we unify all data augmentation strategies for cross-spectral re-identification by mimicking such local linear transformations and categorizing them into moderate transformation and radical transformation. By extending the observation, we propose a Random Linear Enhancement (RLE) strategy which includes Moderate Random Linear Enhancement (MRLE) and Radical Random Linear Enhancement (RRLE) to push the boundaries of both types of transformation. Moderate Random Linear Enhancement is designed to provide diverse image transformations that satisfy the original linear correlations under constrained conditions, whereas Radical Random Linear Enhancement seeks to generate local linear transformations directly without relying on external information. The experimental results not only demonstrate the superiority and effectiveness of RLE but also confirm its great potential as a general-purpose data augmentation for cross-spectral re-identification. The code is available at https://github.com/stone96123/RLE.

PaperPDFCodeCode 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.

Syntology holds a reference implementation of RLE, generated from the paper text (not the authors' code), at level 2 on Syntology's ladder: V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)” (quoted from Syntology's server card). No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='RLE') (how to connect); the free check have('2411.01225') needs no token.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 19 code samples harvested from 1 repository linked to this paper: 13 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 1 violated, 4 with no contract checked; 6 where Syntology's instrument failed) · 6 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 19 samples from 1 repository, 13 ran (7 with no instrument failure; 6 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.

stone96123/rle officialmentioned in papermentioned on GitHubpytorchSyntology: 19 samples, 13 ran (6 instrument-failed) · 6 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

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

2ran · honoured contract
1ran · violated contract
5ran · our draft was wrong
1ran; the contract check could not run
4ran
6unverified

Licence: 19 of the 19 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 stone96123/rle. “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.

stone96123/rle official repository 19 samples, 13 ran (6 instrument-failed) · 6 unverified
GenCamIdx utils.py ran no licence file found · pointer only · 3228fe6a69a0a639 · report fixture: signature gall_img:list/1/str, gall_label:ndarray/1/int, mode:str/0/str · returned list · level recorded 2026-09-25
GenIdx utils.py ran; the contract check could not run (RAISES) no licence file found · pointer only · fd5eb0b6841b0935 · report fixture: signature train_color_label:ndarray/1/int, train_thermal_label:ndarray/1/int · returned tuple · level recorded 2026-09-25
beta_mix_factor random_erasing.py ran · honoured contract no licence file found · pointer only · 2a3d22347a374d3d · report fixture: signature num:int/0/int, factor:float/0/float · returned list · level recorded 2026-09-25
conv3x3 in 1,376 papers resnet.py ran · our draft was wrong no licence file found · pointer only · 48468b2c75aae583 · report fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int, dilation:int/0/int · returned Conv2d · level recorded 2026-09-24
eval_llcm eval_metrics.py ran fingerprinted no licence file found · pointer only · 555da7d9fcddc3f2 · report fixture: signature distmat:ndarray/2/float, q_pids:ndarray/1/int, g_pids:ndarray/1/int, q_camids:ndarray/1/int, g_camids:ndarray/1/int, max_rank:int/0/int · returned tuple · level recorded 2026-09-25
eval_regdb eval_metrics.py ran no licence file found · pointer only · d6f9cf9bb3f7b3fd · report fixture: signature distmat:ndarray/2/float, q_pids:ndarray/1/int, g_pids:ndarray/1/int, max_rank:int/0/int · returned tuple · level recorded 2026-09-25
load_data in 700 papers data_loader.py ran · our draft was wrong no licence file found · pointer only · 9cc6aa0e084e2b4e · report fixture: signature input_data_path:str/0/str · returned tuple · 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
loss.py ran · our draft was wrong fingerprinted no licence file found · pointer only · e3b2a83f52101f2d · report fixture: signature x:Tensor/2/float, axis:int/0/int · returned Tensor · level recorded 2026-09-22
pdist_torch loss.py ran · honoured contract fingerprinted no licence file found · pointer only · 17467d76227ea501 · report fixture: signature emb1:Tensor/2/float, emb2:Tensor/2/float · returned Tensor · level recorded 2026-09-22
process_query_llcm data_manager.py ran no licence file found · pointer only · 4881f0854b34e006 · report fixture: signature data_path:str/0/str, mode:int/0/int, relabel:bool/0/bool · returned tuple · level recorded 2026-09-25
remove_fc resnet.py ran · our draft was wrong no licence file found · pointer only · c5961f4478deab2b · report fixture: signature state_dict:dict/0/? · returned dict · level recorded 2026-09-22
resnet18 in 432 papers resnet.py ran · our draft was wrong no licence file found · pointer only · b755f02af6a9f947 · report fixture: signature pretrained:bool/0/bool · returned ResNet · level recorded 2026-09-25
softmax_weights loss.py ran · violated contract fingerprinted no licence file found · pointer only · 9b6e48a65ef5717f · report fixture: signature dist:Tensor/2/float, mask:Tensor/2/float · returned Tensor · level recorded 2026-09-22
embed_net model.py unverified no licence file found · pointer only · 03a2fe154212e5c9 · report
eval_sysu eval_metrics.py unverified no licence file found · pointer only · bfc70e469e1be59d · report
middle_module model.py unverified no licence file found · pointer only · 62cc52570c2a35ef · report
process_gallery_sysu data_manager.py unverified no licence file found · pointer only · 64cb77f4750867c9 · report
process_query_sysu data_manager.py unverified no licence file found · pointer only · e5f1dc88ea13689c · report
read_imgs pre_process_sysu.py unverified no licence file found · pointer only · e983eec0a09d59cf · 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. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. 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. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model". Where an assembly's phrase has no constructed figure, a brick that ran is not among the harvested samples this build reads, and whether a brick's run only constructed an object is read from that brick's harvested sample, so the figure was not counted; it does not say there were none.

2 assemblies on this paper: 1 harvested, 1 generated.

generated Assembly for RLE (graph method: RLE), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 1 ran (1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. Ran end-to-end against an independent peer (level 2).

label matches by construction: the code was generated for this method (not judged by a model)

  1. apply_linear_enhancement_mask entry · level 2 · ran · 460b2a813e0466ffcc6c5fac2bcefb3db9d72d29debcb00b61065d10311bb173

harvested Assembly for RLE (graph method: RLE). 12 bricks; individually on a fixture: 5 ran (of which 3 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 7 unverified. The assembly has not been run end-to-end.

  1. embed_net entry · level 0 · unverified · 03a2fe154212e5c9
  2. Normalize helper · level 1 · ran · 7f16d1363f322454
  3. base_resnet helper · level 0 · unverified · 808abc324b799b4f
  4. middle_module model · level 0 · unverified · 62cc52570c2a35ef
  5. thermal_module model · level 0 · unverified · 05cc6196c717f836
  6. visible_module model · level 0 · unverified · 1c67d33e697b6c55
  7. weights_init_classifier helper · level 0 · unverified · acca42c3caaebbf2
  8. weights_init_kaiming helper · level 0 · unverified · d110187b453d6759
  9. resnet50 helper · level 1 · ran · our draft was wrong · cbefb8091a472844
  10. Bottleneck helper · level 1 · ran · 1ac2e5df7496b629
  11. ResNet helper · level 1 · ran · be06126c93d1a123
  12. remove_fc helper · level 1 · ran · our draft was wrong · c5961f4478deab2b

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

Tasks

Data Augmentation

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