Instructions

Please login or register to submit your results.

Submission Policy

We strongly encourage all participants to use only the sequences from the training set for finding parameters and report results on the provided detections to enable a meaningful comparison of tracking methods.

Tracking results will be evaluated automatically and made visible only to you. You will be able to make them public at any time.

Important: The evaluation server is not to be used for training. To discourage this, you will have to wait 72 hours (3 days) before you can re-submit your results. If you want to present results of your method with various settings (e.g. different features, inference method, etc.), please use the training set for this purpose and submit only one result to the test server!

File Format

Please submit your results as a single .zip file. The results for each sequence must be stored in a separate .txt file in the archive's root folder. The file name must be exactly like the sequence name (case sensitive).

The file format should be the same as the ground truth file, which is a CSV text-file containing one object instance per line. Each line must contain 10 values:

<frame>, <id>, <bb_left>, <bb_top>, <bb_width>, <bb_height>, <conf>, <x>, <y>, <z>

The conf value contains the detection confidence in the det.txt files. For the ground truth and results, it acts as a flag whether the entry is to be considered. A value of 0 means that this particular instance is ignored in the evaluation, while any other value can be used to mark it as active. The world coordinates x,y,z are ignored for the 2D challenge and can be filled with -1. Similarly, the bounding boxes are ignored for the 3D challenge. However, each line is still required to contain 10 values.

All frame numbers, target IDs and bounding boxes are 1-based. Here is an example:

Tracking with bounding boxes

(2D MOT 2015, MOT16, PETS2017, MOT17)

  1, 3, 794.27, 247.59, 71.245, 174.88, -1, -1, -1, -1
  1, 6, 1648.1, 119.61, 66.504, 163.24, -1, -1, -1, -1
  1, 8, 875.49, 399.98, 95.303, 233.93, -1, -1, -1, -1
  ...
  

Tracking in world coordinates

(3D MOT)

  1, 3, -1, -1, -1, -1, -1, 123.32, 2342.3, 0
  1, 4, -1, -1, -1, -1, -1, 153.12, 2478.2, 0
  2, 3, -1, -1, -1, -1, -1, 125.23, 2213.7, 0
  ...
  

Detection with bounding boxes

(MOT17Det)

  1, -1, 794.27, 247.59, 71.245, 174.88, 4.56
  1, -1, 1648.1, 119.61, 66.504, 163.24, 0.32
  1, -1, 875.49, 399.98, 95.303, 233.93, -1.34
  ...
  

Tracking in multiple cameras

(MultiCam)

Please refer to the dataset's official website for the file format.

Archive Structure

The content of the .zip archive should contain

2D MOT 2015

./TUD-Crossing.txt 
./PETS09-S2L2.txt
./ETH-Jelmoli.txt
./ETH-Linthescher.txt
./ETH-Crossing.txt
./AVG-TownCentre.txt
./ADL-Rundle-1.txt
./ADL-Rundle-3.txt
./KITTI-16.txt
./KITTI-19.txt
./Venice-1.txt

3D MOT 2015

./PETS09-S2L2.txt 
./AVG-TownCentre.txt

MOT16

./MOT16-01.txt 
./MOT16-03.txt
./MOT16-06.txt
./MOT16-07.txt
./MOT16-08.txt
./MOT16-12.txt
./MOT16-14.txt

MultiCam

./duke.txt 

PETS2017

./ARENA-A1-15_06_ENV_RGB_3.txt 
./ARENA-A1-15_06_TRK_RGB_2.txt
./ARENA-W1-11_03_ENV_RGB_3.txt
./ARENA-W1-11_03_TRK_RGB_1.txt
./IPATCH-Sc2a_Tk1_TST_Th2.txt
./IPATCH-Sc2a_Tk1_UoR_RGB_11.txt
./IPATCH-Sc3_Tk2_TST_Th2.txt
./IPATCH-Sc3_Tk2_UoR_RGB_14.txt

MOT17Det

./MOT16-01.txt 
./MOT16-03.txt
./MOT16-06.txt
./MOT16-07.txt
./MOT16-08.txt
./MOT16-12.txt
./MOT16-14.txt

MOT17

./MOT16-01-DPM.txt 
./MOT16-03-DPM.txt
./MOT16-06-DPM.txt
./MOT16-07-DPM.txt
./MOT16-08-DPM.txt
./MOT16-12-DPM.txt
./MOT16-14-DPM.txt
./MOT16-01-FRCNN.txt
./MOT16-03-FRCNN.txt
./MOT16-06-FRCNN.txt
./MOT16-07-FRCNN.txt
./MOT16-08-FRCNN.txt
./MOT16-12-FRCNN.txt
./MOT16-14-FRCNN.txt
./MOT16-01-SDP.txt
./MOT16-03-SDP.txt
./MOT16-06-SDP.txt
./MOT16-07-SDP.txt
./MOT16-08-SDP.txt
./MOT16-12-SDP.txt
./MOT16-14-SDP.txt