-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to reproduce MOTA on MOT17 #20
Comments
Hi, I find that the pixel_means and stds comes from src/fpn/fpn/model/fpn/resnet.py |
I trained a FPN model which is compatible to your release model. The problem is that when pretrained is set True, RPN will try to download weights from aws and hard code pixel means and stvds. Fix is simple as following: +++ b/trainval_net.py
|
Hello @withinnoitatpmet . Have you reproduced the reported result successfully? |
Hi,
Thank you for your wonderful work! I am trying to reproduce you tracktor++ result in MOT17 dataset. Using your trained weights, 61.6 MOTA was reproduced on mot17_train_FRCNN17 as described from paper. However, when I tried to train FPN and siamese network, I only get 49.8 MOTA on mot17_train_FRCNN17.
I noticed that the config.yaml file downloaded and the config file produced by training RPN are different. Here is part of the difference. It seems that parameters are saved in model.
< FEAT_STRIDE: &id012
I evaluated the downloaded model and the model trained by myself, mAPs are roughly the same on val set(0.79x). However, the PIXEL MEANS and STDVS are different.
trained by myself:
'PIXEL_MEANS': array([[[123.675, 116.28 , 103.53 ]]]),
'PIXEL_STDVS': array([[[58.395, 57.12 , 57.375]]]),
downloaded from you(also same as pascal voc pre file):
'PIXEL_MEANS': array([[[102.9801, 115.9465, 122.7717]]]),
'PIXEL_STDVS': array([[[1., 1., 1.]]]),
Do you have any ideas?
The text was updated successfully, but these errors were encountered: