Papers › CA-Jaccard: Camera-aware Jaccard Distance for Person Re-identification

CA-Jaccard: Camera-aware Jaccard Distance for Person Re-identification

17 Nov 2023CVPR 2024 1arXiv:2311.10605archive 2025-07-28

Yiyu Chen, Zheyi Fan, Zhaoru Chen, Yixuan Zhu

Person re-identification (re-ID) is a challenging task that aims to learn discriminative features for person retrieval. In person re-ID, Jaccard distance is a widely used distance metric, especially in re-ranking and clustering scenarios. However, we discover that camera variation has a significant negative impact on the reliability of Jaccard distance. In particular, Jaccard distance calculates the distance based on the overlap of relevant neighbors. Due to camera variation, intra-camera samples dominate the relevant neighbors, which reduces the reliability of the neighbors by introducing intra-camera negative samples and excluding inter-camera positive samples. To overcome this problem, we propose a novel camera-aware Jaccard (CA-Jaccard) distance that leverages camera information to enhance the reliability of Jaccard distance. Specifically, we design camera-aware k-reciprocal nearest neighbors (CKRNNs) to find k-reciprocal nearest neighbors on the intra-camera and inter-camera ranking lists, which improves the reliability of relevant neighbors and guarantees the contribution of inter-camera samples in the overlap. Moreover, we propose a camera-aware local query expansion (CLQE) to mine reliable samples in relevant neighbors by exploiting camera variation as a strong constraint and assign these samples higher weights in overlap, further improving the reliability. Our CA-Jaccard distance is simple yet effective and can serve as a general distance metric for person re-ID methods with high reliability and low computational cost. Extensive experiments demonstrate the effectiveness of our method.

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

By repository: official repository: 10 samples from 1 repository, 6 ran (4 with no instrument failure; 2 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-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 6 samples that ran has no recorded date.

chen960/ca-jaccard officialmentioned in papermentioned on GitHubpytorchMITSyntology: 10 samples, 6 ran (2 instrument-failed) · 4 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

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

Licence: 2 of the 10 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 chen960/ca-jaccard. “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.

chen960/ca-jaccard official repository 10 samples, 6 ran (2 instrument-failed) · 4 unverified
cm in 9 papers caj/models/cm.py ran · our draft was wrong MIT (permissive) · 10ba7332fd4a54eb · report fixture: signature inputs:Tensor/2/float, indexes:Tensor/1/int, features:Tensor/2/float, momentum:float/0/float · returned Tensor · level recorded 2026-09-24
conv3x3 in 1,376 papers caj/models/resnet_ibn_a.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · fac5364e2f53c6db · report fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int · returned Conv2d · level recorded, date not recorded
pairwise_distance in 55 papers
census: 6 implementations from 7 papers, 5 distinct outputs across 3 buckets, one shared input per bucket
caj/evaluators.py ran MIT (permissive) · b6d5887f94b1db25 · report fixture: signature features:dict/0/?, query:NoneType/0/?, gallery:NoneType/0/? · returned Tensor · level recorded 2026-09-25
process_dir caj/datasets/dukemtmcreid.py ran fingerprinted MIT (permissive) · 7e822f939fbe184f · report fixture: signature dir_path:str/0/str, relabel:bool/0/bool · returned list · level recorded 2026-09-24
resnet101_ibn_a in 8 papers caj/models/resnet_ibn_a.py ran MIT (permissive) · c7f5d45660e6ec13 · report fixture: signature pretrained:bool/0/bool · returned ResNet · level recorded 2026-09-24
resnet50_ibn_a in 10 papers caj/models/resnet_ibn_a.py ran MIT (permissive) · 93cbdbc352d644d9 · report fixture: signature pretrained:bool/0/bool · returned ResNet · level recorded 2026-09-24
build_pooling_layer in 6 papers caj/models/pooling.py unverified MIT (permissive) · 5c5d2f6f3c01ba6c · report
extract_cnn_feature in 14 papers caj/evaluators.py unverified MIT (permissive) · fbb5efeed7ebfd09 · report
extract_features in 73 papers caj/evaluators.py unverified MIT (permissive) here; the stored copy is pointer only · 962810c012a60817 · report
label_generator_kmeans in 8 papers caj/models/kmeans.py unverified MIT (permissive) · 4560dc753fea5981 · report

Tasks

Person Re-IdentificationPerson RetrievalRe-RankingUnsupervised Person Re-IdentificationUnsupervised Vehicle Re-IdentificationVehicle Re-Identification

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Person Re-Identification MSMT17 CA-Jaccard Rank-1 86.2 #11 of 43 Archive leaderboard report
Person Re-Identification MSMT17 CA-Jaccard Rank-5 90.5 #11 of 43 Archive leaderboard report
Person Re-Identification MSMT17 CA-Jaccard mAP 74.1 #11 of 43 Archive leaderboard report
Person Re-Identification Market-1501 CA-Jaccard Rank-1 96.2 #19 of 135 Archive leaderboard report
Person Re-Identification Market-1501 CA-Jaccard Rank-5 98.1 #19 of 135 Archive leaderboard report
Person Re-Identification Market-1501 CA-Jaccard mAP 94.5 #19 of 135 Archive leaderboard report
Unsupervised Person Re-Identification MSMT17 CA-Jaccard Rank-1 75.1 #5 of 12 Archive leaderboard report
Unsupervised Person Re-Identification MSMT17 CA-Jaccard Rank-10 87.3 #5 of 12 Archive leaderboard report
Unsupervised Person Re-Identification MSMT17 CA-Jaccard Rank-5 84.3 #5 of 12 Archive leaderboard report
Unsupervised Person Re-Identification MSMT17 CA-Jaccard mAP 44.3 #5 of 12 Archive leaderboard report
Unsupervised Person Re-Identification Market-1501 CA-Jaccard MAP 86.1 #7 of 23 Archive leaderboard report
Unsupervised Person Re-Identification Market-1501 CA-Jaccard Rank-1 94.4 #7 of 23 Archive leaderboard report
Unsupervised Person Re-Identification Market-1501 CA-Jaccard Rank-10 98.7 #7 of 23 Archive leaderboard report
Unsupervised Person Re-Identification Market-1501 CA-Jaccard Rank-5 97.9 #7 of 23 Archive leaderboard report
Vehicle Re-Identification VeRi-776 CA-Jaccard Rank-1 97.6 #10 of 17 Archive leaderboard report
Vehicle Re-Identification VeRi-776 CA-Jaccard Rank-5 98.3 #10 of 17 Archive leaderboard report
Vehicle Re-Identification VeRi-776 CA-Jaccard mAP 81.4 #10 of 17 Archive leaderboard report

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