Closed Derpimort closed 4 years ago
I got the same issue, how could this happen?
I "kind of" fixed it, more of a workaround because now I can't use the half precision advantage, by commenting out the following lines https://github.com/WongKinYiu/PyTorch_YOLOv4/blob/8f006d351bf1ac888239cfeaf6fcd4a31eb866ca/test.py#L51-L52
From what I've gathered is at some point the inputs are implicitly converted from half to float because the test code does convert them to half precision. I thought it was happening in the author's code and tried to change the following lines and add more explicit conversions... https://github.com/WongKinYiu/PyTorch_YOLOv4/blob/699acbfea3fa8773d72ea4f2f71120858b6a2435/test.py#L77-L89
But no luck, will try and update if I get it working on half precision.
it due to pytorch 1.6 contains native amp. i used pytorch 1.5.1 and install apex for amp training.
Oh ok, makes sense. Great repo btw, it really helped alot.
Trying to train the network on a custom object detection dataset. I'm running it in a docker container on a single Tesla V100. Steps:
yolov4l-mish.yaml
to parent directory and change the nc to 3.python train.py --data ../data/data.yaml --cfg ../yolov4l-mish.yaml --img-size 480 --batch-size 16 --device 0 --cache-images --weights ''
It completes one full train loop and throws the following Error on the validation loop.
Some helpful info:
Device detected and Namespace output: