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
Hello all,
I will appreciate your help with this question: most tutorials and examples for retraining yolov4 use pretrained weights from the yolov4.conv.137 file .... which is the original network used to obtain those weights? the "complete" weights files at the model zoo all of them specify the native resolution for training (416, 512, 608 ...), but I cannot find it for this partial weights file.
I understand that using the same resolution in my dataset , in the network for retraining, and in the pretrained wedights should give the best results?
Additionally, I am wondering what happend to the anchors if the size of my dataset is not the same as the size of the network. I have calculated my anchors for a 608x608px dataset, if the network's size is 416 and all images are resized, are the anchors still valid?
Thanks in advance for your help!
ADolfo.
The text was updated successfully, but these errors were encountered:
Hello all,
I will appreciate your help with this question: most tutorials and examples for retraining yolov4 use pretrained weights from the yolov4.conv.137 file .... which is the original network used to obtain those weights? the "complete" weights files at the model zoo all of them specify the native resolution for training (416, 512, 608 ...), but I cannot find it for this partial weights file.
I understand that using the same resolution in my dataset , in the network for retraining, and in the pretrained wedights should give the best results?
Additionally, I am wondering what happend to the anchors if the size of my dataset is not the same as the size of the network. I have calculated my anchors for a 608x608px dataset, if the network's size is 416 and all images are resized, are the anchors still valid?
Thanks in advance for your help!
ADolfo.
The text was updated successfully, but these errors were encountered: