-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Own dataset doesn't work on latest commit #39
Comments
@RickvanHek Sorry, its possible one of the latest commits broke something, as I've been updating quite often. I've been running internal tests with a more advanced version with no issues. I just committed these changes now as b07ee41. Can you try to download this from scratch and rerun? If this works I'd advise you to check back in a day or two, I'm compiling updates that should increase performance significantly. These updates are not reflected in the latest commit, they are being tracked in #2 (comment) and should be implemented in one single commit in the next few days. FYI in your particular case you may have issues with your local dataset with SGD burn-in, which is supposed to last the first 1000 batches (you only have 99). So your first epoch may be doing nothing really, as the lr is programmed to ramp exponentially from zero to the initial lr = 0.001 over those 1000 batches. Lines 139 to 143 in b07ee41
|
Thank you for the fast reply, when I disable the SGD (on the last commit, like you said), I don't get the nan anymore, if i enable it i still get these nan's. These are my results after 4 epochs,
My dataset has 70000 training and validation images, I was just using a 100 for testing purpose. |
I did 6 epochs on 7000 images (batch size = 1), and i still got 0 precision, here are the results:
Any idea why i'm getting 0 precision? Left the code untouched only edited the writing to result.txt (to not do an mAp calculation, because this gives an error for me) |
Ah that's perfect, everything is fine. The new The mAP calculation in test.py now adds P and R to results.txt in the last 3 columns. Is test.py still crashing? |
Oh that's why, didn't know that.
|
Ok. Layers 81, 93 and 105 are the yolo detection layers. 80 classes makes them size 255 but your model seems to have more classes as you can see. If you are using a custom dataset you need to adjust test.py to work with it, just like you adjust train.py (i.e. set |
@RickvanHek I just had an idea that might smooth things a bit after seeing #40 recently. If I pass the train.py namespace arguments ( If you ran test.py by itself you'd still need to properly set them again though. Do you think this change might have solved your training issues? |
Hello, this fixed the problem! Thank you! |
For some reason I can't seem to train my own dataset on the latest commit. I am able to do it from an earlier commit e.g. this state. In this state if i run my training (with the exact same cfg files, dataset etc), i get these results after a couple epochs:
If I use the latest commit, i get this:
Also in the latest commit, line 197 of train.py causes the following error:
So I replaced it with (the old) code:
I don't know if this is normal but i can't seem to find a solution.
Do you know why i get nan whilst using the exact same cfg files and data? My txt files for each image is spot on, the bounding boxes, width, height etc are all relative to the image width and height.
The text was updated successfully, but these errors were encountered: