-
Notifications
You must be signed in to change notification settings - Fork 12
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
Flying fox recognizer #239
Conversation
Branch for Issue-#238
Issue-#238 Further work on the flying fox recogniser. Refactored a method used for frog recognisers and made it generally available in the class StandardSpectrograms.cs
Issue-#238 Main work was to add a new method to AcousticEvents.cs in order to find events located at a score maximum. All such events have the same (user defined) time duration centred on the maximum.
REmoved a lot of unnecessary commented code. Also improved call detection. Next step is to add additional contraints to the call spectrum to match that of bat call.
@towsey is this ready for review? |
Issue #238: change method which makes first attempt to look for FF chirps. Start second method which filters those on the basis of the similarity of their spectral profile to that of a flying fox.
Issue #238 This recogniser now works well on a ten minute recording containing 14-16 FF calls. TODO: The search parameters need to be read from config file. At moment hard coded.
Issue #238 Add Wingbeat profile to recogniser. It picks up wingbeats but also some human speech. Also set up to read parameters from the config file.
Did not work so far.
Issue #238 Do final work on Flying Fox wing beat detection. Produce event spectra for experimental debug purposes.
Issue #238 Reviewed FF recogniser on a four extra recordings. In particular worked on a 60 minute recording and was able to pick up most ac events of interest with few FPs and FNs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@towsey, lots of goof work here.
Most of the changes requested are just nits and cleanup.
However, the largest omission is a lack of unit tests.
Test are expected for the following:
- The entire pulse train class (using no audio)
- The
SpectrogramTools.GetSonogramPlusCharts
method (using no audio) - And the
AcousticEvent.GetEventsAroundMaximia
method (again, no audio required)
Additionally, there is no mention of the resource packet that was used to train/test this recognizer. Can you please describe where we can find a zip file with short segments of audio (no more than a minute) along with associated true/false labels for each expected event generated.
Thanks
src/AnalysisConfigFiles/RecognizerConfigFiles/Towsey.PteropusSpecies.yml
Show resolved
Hide resolved
src/AnalysisConfigFiles/RecognizerConfigFiles/Towsey.PteropusSpecies.yml
Outdated
Show resolved
Hide resolved
Issue #238 work on changes suggested by Anthony.
What has happened. I am working on all the issues you raised. Committed some yesterday - still more to go! |
Sorry - accidentally deleted too early. I'm on a mistake-making-productivity-steam-train! I've restored the branch. |
Closes #238