Hi All. Spring peeper season will soon be upon us. Last spring, BirdVoxDetect would produce thousands upon thousands of detections of spring peepers. Adjusting the threshold did not alleviate the problem since most detections were still peepers. Is there any work around for this problem within BirdVoxDetect? The only solution I can think of is filtering out all calls in the peeper frequency band by my AudioMoth. However, all birds within this range, namely, thrushes will also be filtered out. Thanks for considering this issue.John
You received this message because you are subscribed to the Google Groups "birdvox" group.
To unsubscribe from this group and stop receiving emails from it, send an email to birdvox+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/birdvox/06194f3b-9f00-4bce-9a87-c0c8af3ca8fdn%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hello John, Justin and all,
> The only way I can with any accuracy tell them apart is by
listening to the recording or viewing a segment of the recording
so one can hear or see the cadence of the spring peeper calls.
I agree. Telling apart one from the other is more a matter of call rate ("cadence") than of spectrotemporal pattern.
We don't have a model for call rate yet in BirdVoxDetect. The species classifier make a prediction based on a small amount of context (150 milliseconds), encompassing a single call.
We have published a version of our flight call detector which is
"context-adaptive" in the sense that it takes into account the
background noise at a duration of 30 minutes. This is mostly for
dealing with variations in insect noise.
But the call rate of spring peepers range between those two time constants (150 ms and 30 minutes), and thus beyond the scope of BirdVoxDetect. For this reason, we expect BirdVoxDetect to perform better during the fall than during the spring.
Distinguishing flight calls from frog calls is an open research question and one that we'd like to tackle in the long term; but it's unclear why. A straightforward approach would be to replace the convolutional neural network (CNN) by a convolutional _recurrent_ neural network (CRNN), but these are much slower than CNN, both at training time and at prediction time. So i'm not convinced that this is an approach worth investigating. For the time being, we're focusing on bird-vs-bird classification which is already a challenging problem when posed at the level of individual flight calls.
I hope this helps and thanks again for your interest in BirdVox
To view this discussion on the web visit https://groups.google.com/d/msgid/birdvox/2758b193-8029-429a-a791-fbea31615d1en%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/birdvox/CAKS_OiRd9dgiSVjSS-2oK55KouoAPB%3DEyBH8j%3DkkUCwzbQGJ3g%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/birdvox/CAMJwWBQhfTpkiLNMCit0kKwbOKs4jftBaEz-yp1PfyeVwwFe7g%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/birdvox/CAMJwWBRWngfwF6sV9ViMu3joN6z3%3DW9bbFLcc5ceXeOpPvF%3DOw%40mail.gmail.com.