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
Thank you very much for your excellent work. I tried to reproduce your results, but found that MOTA was always 0.
(1) When use your provided json files, it can achieve your results.
(2) When use your provided weights of r101, the MOTA is 0.
(3) When I retrain a model, the MOTA also is 0.
I checked the result json file, and it showed that the result was normal (not NAN), but the track id between the two frames did not correspond.
So I would like to ask how to solve this problem. Thank you very much!
The text was updated successfully, but these errors were encountered:
Hi,
Can you share the scripts or config file you are using for (2) and (3)? Seems wired, the recall is non-trival but tracking related metrics is zero.
Thank you very much for your excellent work. I tried to reproduce your results, but found that MOTA was always 0.
(1) When use your provided json files, it can achieve your results.
(2) When use your provided weights of r101, the MOTA is 0.
(3) When I retrain a model, the MOTA also is 0.
I checked the result json file, and it showed that the result was normal (not NAN), but the track id between the two frames did not correspond. So I would like to ask how to solve this problem. Thank you very much!
@feifei-Liu
Hi, I met the same problem with you, how did you solve it later ?
Hi,
Thank you very much for your excellent work. I tried to reproduce your results, but found that MOTA was always 0.
(1) When use your provided json files, it can achieve your results.
(2) When use your provided weights of r101, the MOTA is 0.
(3) When I retrain a model, the MOTA also is 0.
I checked the result json file, and it showed that the result was normal (not NAN), but the track id between the two frames did not correspond.
So I would like to ask how to solve this problem. Thank you very much!
The text was updated successfully, but these errors were encountered: