-
Notifications
You must be signed in to change notification settings - Fork 587
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
Can't reproduce original YOLOv4 AP on coco test-dev2017? #262
Comments
weights file and yolo decoder are different. |
Thank you, your code is great. Also, it would be great if this can use the original weights as well. It can actually run them and the mAP50 was actually OK (especially on coco-val2017). Hence, I guess it needs little modifications. One other question, if I trained using these models on custom data, can I convert the output model to tensorRT? are all activation functions and small details supported in this conversion? Thanks again for the great code. |
I was also confused due to your answer on this issue here: #46 He asked about yolov3 and you said that it should run ok. |
for original yolov4 implementation, you could use u3_preview branch the master branch is same as new_coord=1 for new models. |
Hello,
I wanted to reproduce the reported AP of the YOLOv4 model available here (608 image size), which is 43.5.
[I am using the master branch]
I used the following parameters with the test.py file:
and using the weights and cfg files from the link above.
test.py outputted the detections_test-dev2017_yolov4.weights_results.json
I uploaded the file to the COCO detection evaluation server @ CodaLab, and I got the following results:
So, I got 26.2% instead of the 43.5% expected!
Am I doing something wrong? Is there something wrong with this implementation?
The text was updated successfully, but these errors were encountered: