Issue #238 flying fox recognizer #272
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Issue #238 work on changes suggested by Anthony.
Issue #238 Only unit tests to be done.
Issue #238 Changes mostly to get acoustic event information transfered to the FF methods.
Issues-#238 Set up unit tests for the flying fox recogniser. Currently he two methods have dummy content pasted from elsewhere
Issue #238 More work on unit tests
Prepare a one minute recording contaiing both wingbeats and territorial calls. Set up both tests for wingbeats and calls.
Issue #238 Revert file name in SonogramTests.cs which was mistkenly changed yesterday.
Issue #238 Complete two tests of methods used in the Flying Fox recogniser.
Issue # 238 Write new test for generating spectrogram image with plots and events annotated. Make other tests more efficient
Commented out methods in this class because the idea was not yielding good enough results.
Issue #238 More work on Oscillation recognizer to pick up bat wing beats.
For some reason, acoustic event bounds were not being calculated. Had to fix acoustic event class, and then do slight readjustments to the expected bounds of wing-beat events.
atruskie
approved these changes
Nov 14, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have fixed the unit tests for flying fox recogniser.
Do not understand how they could have broken.
I have created a new class called Oscillations2019 - I want to explore some new ideas.
But I will continue with those in a new branch.