You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some investigation, I found the main issue is the difference in the loading approach used by TrackEval and py-motmetric. For instance, I tried using the data.zip from here for MOT20-01 and got a different number of detections and ground-truths. Also, the ID for py-motmetrics should be started from 1, which is not an issue for TrackEval. Matching the loading logic might solve the problem, but it requires some time to bridge the gap.
I remember achieving identical results on MOTA and IDF1 in a comparison I did like a year ago. And yes, both in the gt and my predicted mot results the ID starts from 1
I have 2 sequences which I generated motchallenge compliant results for. First lines in my
(frame, id, l, t, w, h, conf, class)
dataset format:When running
trackeval
I get:Using
motmetics
by the code snippet suggested by @Justin900429 here I get:AssA seems to match, but not DetA nor HOTA. What am I missing?
The text was updated successfully, but these errors were encountered: