-
Notifications
You must be signed in to change notification settings - Fork 198
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
Classification Benchmark and false positives #11
Comments
There is not enough information to be able to know what is going on. Please post
|
UPDATE --> I tried the iPhone app is working 100%, so i expect a technical Problem here !!! Here are my coordinates: LATITUDE=49.584 I didn't give the command line parameter for the week, the one liner runs nevertheless. Only for testing purposes, I don't have a microphone. |
Thats what i get for the "Amsel":
The iPhone BirdNet.app recognizes the correct bird "Amsel". |
The easiest explanation would be that you swapped LAT and LON . . . |
Nope:
I exchanged LAT LOG and get the same result ?!? |
Can you reproduce with the attached file with BirdNET-Lite and BirdNET.app and compare? |
Please tell us exactly what you installed. |
I installed the repro fom here, and exchanged the labels.txt from the model to the german one. |
I would propose you make the base install and test that. |
Did you get the same Latin names for the examples from Stefan?
|
I cannot compare the examples if i don't have a reference, anyone here who can post the results for the shipped XC... files? |
Your results are wrong. |
Plase, can you provide the reference result? The Latin names are the same in the labels file provided here: #4 |
Ok, found the Bug the labels file is totally wrong:
|
Have now installed the BirdNET-Lite from scratch without the German labels file. Getting this for the 'Amsel" (Blackbird):
In the BirdNET app i get the correct result. Don't undestand that. |
Well the app is different, don't know which model it has but it probably does some temporal pooling, and the results are better and more filtered than those from BirdNET-Lite. Then your Third, none of the results raise above .7 in confidence, which implies that they are quite uncertain. How is the sound quality of your file? I have ended up grepping only results with confidence>.7, and even those are not all right. You need to do a bit of "temporal pooling" yourself, and familiarise yourself with the common errors the network makes. But Junco hyemalis doesn't sound like a Blackbird at all, as far as I can tell. There can still be something wrong with your installation. Try with other files, and the examples provided with the software. The most obvious thing to mess up with the translated files is to get async with the positions of the lines in the file. If you have an offset of one somewhere, the results are all garbage. |
The app uses this model --> https://github.com/kahst/BirdNET-CoreML . Corrected the week and get:
which is correct. :-) Was also able to reproduce this on the live system from Patrik. |
See #4 - I (hopefully) fixed the labels. |
Can confirm that the labels are now fixed and work for all languages. |
Hello,
I was able to reproduce and run the Lite System on a MacBook M1 and also on a Raspberry Pi with the live system from Patrik. I run a lot of benchmark tests with Germany Species which are transcribed (at least with there German names) available on YouTube. I used also the German localization provided in with the new labels file. The classification result (output labels) was on both systems more less the same. I used the following Input sound files:
I transformed the YouTube videos to mp3 and used my home location (Rhineland Pfalz) as parameter for analyse script. I did not support and week of the year flag. The results i get where really bad, i get approximately:
One interesting fact that even trough I specified the geo coordinates (lat/long) from Germany most species are from South-America and the South-East Pacific area. I want to discuss the problems with the classification here in detail:
UPDATE --> I tried the iPhone app is working 100%, so i expect a technical Problem here !!!
The text was updated successfully, but these errors were encountered: