Papers › JRMOT: A Real-Time 3D Multi-Object Tracker and a New Large-Scale Dataset

JRMOT: A Real-Time 3D Multi-Object Tracker and a New Large-Scale Dataset

19 Feb 2020arXiv:2002.08397archive 2025-07-28

Abhijeet Shenoi, Mihir Patel, JunYoung Gwak, Patrick Goebel, Amir Sadeghian, Hamid Rezatofighi, Roberto Martín-Martín, Silvio Savarese

Robots navigating autonomously need to perceive and track the motion of objects and other agents in its surroundings. This information enables planning and executing robust and safe trajectories. To facilitate these processes, the motion should be perceived in 3D Cartesian space. However, most recent multi-object tracking (MOT) research has focused on tracking people and moving objects in 2D RGB video sequences. In this work we present JRMOT, a novel 3D MOT system that integrates information from RGB images and 3D point clouds to achieve real-time, state-of-the-art tracking performance. Our system is built with recent neural networks for re-identification, 2D and 3D detection and track description, combined into a joint probabilistic data-association framework within a multi-modal recursive Kalman architecture. As part of our work, we release the JRDB dataset, a novel large scale 2D+3D dataset and benchmark, annotated with over 2 million boxes and 3500 time consistent 2D+3D trajectories across 54 indoor and outdoor scenes. JRDB contains over 60 minutes of data including 360 degree cylindrical RGB video and 3D pointclouds in social settings that we use to develop, train and evaluate JRMOT. The presented 3D MOT system demonstrates state-of-the-art performance against competing methods on the popular 2D tracking KITTI benchmark and serves as first 3D tracking solution for our benchmark. Real-robot tests on our social robot JackRabbot indicate that the system is capable of tracking multiple pedestrians fast and reliably. We provide the ROS code of our tracker at https://sites.google.com/view/jrmot.

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

By repository: official repository: 16 samples from 1 repository, 15 ran (14 with no instrument failure; 1 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 15 samples that ran has no recorded date.

StanfordVL/JRMOT_ROS officialpytorchMITSyntology: 16 samples, 15 ran (1 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

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

Licence: 1 of the 16 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, 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 StanfordVL/JRMOT_ROS. “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.

StanfordVL/JRMOT_ROS official repository 16 samples, 15 ran (1 instrument-failed) · 1 unverified
conv3x3 in 1,376 papers src/aligned_reid_model.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
find_area src/distances.py ran MIT (permissive) · 03de75aaa3b406e0 · report fixture: signature vertices:list/1/list · returned float · level recorded 2026-09-25
get_unmatched src/JPDA_matching.py ran MIT (permissive) · f3c57153547a2d6d · report fixture: signature all_idx:list/1/int, matches:list/1/dict, i:int/0/int, marginalization:ndarray/2/int · returned list · level recorded 2026-09-25
iou_matrix src/distances.py ran fingerprinted MIT (permissive) · d3e27588bb89e7f2 · report fixture: signature objs:ndarray/2/float, hyps:ndarray/2/float, max_iou:float/0/float · returned ndarray · level recorded 2026-09-25
load_pickle in 115 papers src/aligned_reid_utils.py ran MIT (permissive) · 3bd76346246df44c · report fixture: signature path:str/0/str · returned dict · level recorded 2026-09-25
norm2squared_matrix in 5 papers src/distances.py ran fingerprinted MIT (permissive) · 84e275a207526fa2 · report fixture: signature objs:ndarray/2/float, hyps:ndarray/2/float, max_d2:float/0/float · returned ndarray · level recorded 2026-09-25
remove_fc src/aligned_reid_model.py ran MIT (permissive) · 91c9512a42be21c4 · report fixture: signature state_dict:dict/0/? · returned dict · level recorded 2026-09-25
resnet18 in 432 papers src/aligned_reid_model.py ran MIT (permissive) · 2c1c8a02c1ba4103 · report fixture: signature pretrained:bool/0/bool · returned ResNet · level recorded 2026-09-25
rotx in 15 papers src/calibration.py ran · honoured contract fingerprinted MIT (permissive) · 8843d80ab666c4e9 · report fixture: signature t:float/0/float · returned ndarray · level recorded 2026-09-24
roty in 19 papers src/calibration.py ran · honoured contract fingerprinted MIT (permissive) · ae86074e10e1dfd7 · report fixture: signature t:float/0/float · returned ndarray · level recorded 2026-09-24
rotz in 12 papers src/calibration.py ran fingerprinted MIT (permissive) · 082920adf6e29c94 · report fixture: signature t:float/0/float · returned ndarray · level recorded 2026-09-25
squared_mahalanobis_distance src/EKF.py ran MIT (permissive) · 2eea9d292de00db2 · report fixture: signature mean:ndarray/1/float, covariance:ndarray/2/float, measurements:ndarray/2/float · returned ndarray · level recorded 2026-09-25
swap in 9 papers src/double_measurement_kf.py ran MIT (permissive) · d99bf42088f3299d · report fixture: signature detections_3d:list/1/ndarray, iou:ndarray/2/float, idx:int/0/int, swap_prob:float/0/float · returned ndarray · level recorded 2026-09-25
time_str in 5 papers src/aligned_reid_utils.py ran fingerprinted MIT (permissive) · da7227beeb4bcf4f · report fixture: signature fmt:str/0/str · returned str · level recorded 2026-09-25
to_scalar in 6 papers src/aligned_reid_utils.py ran MIT (permissive) · fba558bcab745072 · report fixture: signature vt:Tensor/1/float · returned float32 · level recorded 2026-09-25
non_max_suppression in 12 papers src/deep_sort_utils.py unverified MIT (permissive) · e8fe9fcc53566f61 · report

Tasks

Autonomous NavigationMotion PlanningMulti-Object TrackingMultiple Object TrackingObject Tracking

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Multiple Object Tracking KITTI Test (Online Methods) JRMOT HOTA 69.61 #18 of 34 Archive leaderboard report
Multiple Object Tracking KITTI Test (Online Methods) JRMOT MOTA 85.70 #18 of 34 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