Papers › Deep Learning for Person Re-identification: A Survey and Outlook
Deep Learning for Person Re-identification: A Survey and Outlook
Mang Ye, Jianbing Shen, Gaojie Lin, Tao Xiang, Ling Shao, Steven C. H. Hoi
Person re-identification (Re-ID) aims at retrieving a person of interest across multiple non-overlapping cameras. With the advancement of deep neural networks and increasing demand of intelligent video surveillance, it has gained significantly increased interest in the computer vision community. By dissecting the involved components in developing a person Re-ID system, we categorize it into the closed-world and open-world settings. The widely studied closed-world setting is usually applied under various research-oriented assumptions, and has achieved inspiring success using deep learning techniques on a number of datasets. We first conduct a comprehensive overview with in-depth analysis for closed-world person Re-ID from three different perspectives, including deep feature representation learning, deep metric learning and ranking optimization. With the performance saturation under closed-world setting, the research focus for person Re-ID has recently shifted to the open-world setting, facing more challenging issues. This setting is closer to practical applications under specific scenarios. We summarize the open-world Re-ID in terms of five different aspects. By analyzing the advantages of existing methods, we design a powerful AGW baseline, achieving state-of-the-art or at least comparable performance on twelve datasets for FOUR different Re-ID tasks. Meanwhile, we introduce a new evaluation metric (mINP) for person Re-ID, indicating the cost for finding all the correct matches, which provides an additional criteria to evaluate the Re-ID system for real applications. Finally, some important yet under-investigated open issues are discussed.
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):
get_harvested_code_for_paper(arxiv_id="2001.04193")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2001.04193", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2001.04193")
Code
No sample from the archive's official repository (mangye16/ReID-Survey) is linked to this paper; the 19 samples below come from 2 community repositories, and 3 more are identical to code Syntology harvested from another paper's repository. Syntology harvested code from mangye16/ReID-Survey for another paper.
mangye16/ReID-Survey: Syntology's graph links these samples to Transformer for Object Re-Identification: A Survey (arXiv:2401.06960; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 1 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method.
Syntology 22 code samples: 19 from 2 repositories linked to this paper, 3 identical to code harvested from another paper's repository. Across all 22: 19 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 0 honoured, 1 violated, 11 with no contract checked; 7 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 7 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: community (archive-listed): 19 samples from 2 repositories, 18 ran (11 with no instrument failure; 7 where Syntology's instrument failed); 3 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
No sample is linked to this paper from 4 of its repositories that Syntology harvested for other papers:
- mangye16/ReID-Survey, official repository: harvested for another paper, listed under the repository
- MindCode-4/code-14, community (archive-listed): harvested for another paper, listed under the repository
- layumi/Person_reID_baseline_pytorch, community (archive-listed): harvested for another paper, listed under the repository
- pwc-1/Paper-9, community (archive-listed): harvested for another paper, listed under the repository
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. 2 of the 19 samples that ran have no recorded date.
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.
A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.
Code Syntology ran Syntology
22 samples harvested: 19 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 0 honoured, 1 violated, 11 with no contract checked; 7 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.
Licence: 5 of the 22 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. 3 samples are listed last, in a group without a repository. “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.
ce5528b90aee9251 · 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-24 ee2fbb15866cc877 · 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-24 ecbd84f325abbab0 · 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, use_metric_cuhk03:bool/0/bool · returned tuple · level recorded 2026-09-24 56d39004d57cb3a2 · report
fixture: signature current_step:int/0/int, warmup_steps:int/0/int, base_lr:float/0/float, init_lr:float/0/float · returned float · level recorded 2026-09-24 b9e24c3e3e0e88a7 · report
fixture: signature args:Namespace/0/?, cfg:dict/0/? · returned dict · level recorded 2026-09-22 ff75f4d130ead571 · report
fixture: signature parser:ArgumentParser/0/?, cfg:dict/0/?, helper:dict/0/?, choices:dict/0/?, cfg_path:str/0/str · returned Namespace · level recorded 2026-09-22 8486896224aa5191 · report
fixture: signature yaml_path:str/0/str · returned tuple · level recorded 2026-09-22 c69ee6acc82be011 · report
fixture: signature base_lr:float/0/float, lr_epochs:list/1/int, steps_per_epoch:int/0/int, warmup_epochs:int/0/int, max_epoch:int/0/int, gamma:float/0/float · returned ndarray · level recorded 2026-09-24 1c995b3e930c8f8e · report
fixture: signature lr:float/0/float, lr_epochs:list/1/int, steps_per_epoch:int/0/int, warmup_epochs:int/0/int, max_epoch:int/0/int, gamma:float/0/float · returned ndarray · level recorded 2026-09-24 7817df1615c1662c · report
fixture: signature path:str/0/str · returned bool · level recorded 2026-09-25 dd1114865f06f0fd · report
fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int · returned Conv2d · level recorded 2026-09-22 census: 12 implementations from 14 papers, 3 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32 modeling/layer/triplet_loss.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only ·
c83d9f7fca950b77 · report
fixture: signature x:Tensor/2/float, y:Tensor/2/float · returned Tensor · level recorded, date not recorded 93f2c0b80ea7f36e · report
fixture: signature dist_mat:Tensor/2/float, labels:Tensor/1/int, return_inds:bool/0/bool · returned tuple · level recorded 2026-09-25 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 modeling/layer/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 7d6e263caea8e963 · report
fixture: signature fpath:str/0/str · returned dict · level recorded 2026-09-24 f3a89c60b7c760a9 · report
fixture: signature last_stride:int/0/int, pretrained:bool/0/bool · returned ResNet_IBN · level recorded 2026-09-24 295f89c9a58b123e · report
fixture: signature last_stride:int/0/int, pretrained:bool/0/bool · returned ResNet_IBN · level recorded 2026-09-24 d5b4cd03446719f9 · report
fixture: signature name:str/0/str, save_dir:str/0/str, distributed_rank:int/0/int · returned Logger · level recorded 2026-09-24 4008920c34a176e9 · report
3 samples are identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
7c508037b40522af · report
fixture: signature v:str/0/str · returned bool · level recorded, date not recorded 3f91b09177ddeb33 · report
Tasks
Datasets
Introduced by this paper, per the archive.
Results from the paper archive 2025-07-28
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