fix bug when re-establish tracks and privide consistent result with matlab toolbox #127
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Considering match before last frameid when re-establish tracks will lead to unpredicted match and neglected id tranfer.
From result on private dataset and result, HId 148 trasfer bettween 23 and 27, but not counted timely.
Before bug fix:
events.loc[event["HId"]==148]
events.loc[event["0Id"]==23]
events.loc[event["0Id"]==27]
After bug fix:
events.loc[event["HId"]==148]
iou_det_SDP.zip
When testing the iou_det_SDP.zip on MOT16_train, average MOTA is 62.9%(pymotmetrics) with 63.1%(mot challendge matlab toolbox)
By the way, ML MT definition is slight different with matlab toolbox, but it's unimportant:
pymotmetrics: ML >= 0.8; partially_tracked 0.2 <= <0.8
matlab: ML > 0.8; partially_tracked 0.2 <= <=0.8
If change the ML MT definition in metrics.py as well, result will be:
The commit is tested in master branch, but mot.py is same in the branch.