Hi Alex,
This might come a bit late, but hopefully it will still be useful to some.
There are plenty of ways to analyze the behavior of the tracker at each step. My first recommendation would be to modify this line of code to output the analysis information structure:
[tracks, ~, alltracks, info] = tracker(highScoreDetections, reader.CurrentTime, iouCost);
This fourth output contains a lot of useful information regarding the decisions that the tracker made during this step. See this page for details on the list.
In particular it will list which tracks were just initialized by their trackID. You can find those new tracks in the 3rd output 'alltracks' and query their State property to find their initial value (which by construction is simply the bounding box measurement of the initializing detection, and null velocities). The 'Assignment' field informs you which detection was used to correct each track. Note that the correction value is already available to you by querying the State property of the track output.
The predicted location of the track is calculated internally by the tracker. You have a few ways to access this information.
- prior to running the above line of code, query the predicted locations of all existing tracks in tracker using predictTracksToTime:
allpredictedTracks = predictTracksToTime(tracker, 'all', reader.CurrentTime);
% inspect the State property here
[tracks, ~, alltracks, info] = tracker(highScoreDetections, reader.CurrentTime, iouCost);
- In this particular example, the previous step is also done as part of the IOU cost calculation, therefore you can also output the predicted track states by modifying that function, or put a breakpoint in the similarityIoU function in the helperSORTCost.m function file.
Hope that helps
