-
Notifications
You must be signed in to change notification settings - Fork 89
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
Network training #19
Comments
Hey Bavo, Sorry it has taken us a while to get around to these issues, it has been a busy couple weeks. It looks like you may just have a single enormous image somewhere in the training data. How big are the bouts you are training with? We generally use 1 second. -Kevin |
Hey Bavo, That is peculiar... Can you send me the audio file and the detection file to take a look at? -Kevin |
Hey Bavo, The way bouts works on the default settings (1s) is that a new image will be created when there are no calls for over 1s. That animal just never stops making calls for more than a 1 second! If you reduce the bout size to 0.25s then it will produce a bunch of normal sized images that will work for training. -Kevin |
Hey Kevin, Everything works fine now, thus, if you'd like you can close this issue :) Bavo |
That's great, feel free to open another if you run into anything new. |
Dear Kevin and Russell,
I have been trying training a new network out of the image bouts that I created from our data. Unfortunately, an error occurred and thus I started training a new network for each file that we have. Consequently, I have singled out the problematic files that give the error below.
Furthermore, I have compared the files that create this error with similar files to check for size. However, there are other files containing more USVs and are longer in time than the ones creating the above mentioned error. Also, running it on the stronger computer gave the same error.
Is there a way around this to reduce the array sizes of these files or does the problem lie somewhere else?
Kind regards,
Bavo Kempen
The text was updated successfully, but these errors were encountered: