Providing users of Call Recognizers with more diagnostic feedback #451
Comments
towsey
added a commit
that referenced
this issue
Feb 19, 2021
…riodicity Issue #451 Also write a new method to convert an array of real values to a string.
towsey
added a commit
that referenced
this issue
Feb 19, 2021
Issue #451 Add feedback about filtering events on syllable duration, bandwidth, sideband activity etc.
towsey
added a commit
that referenced
this issue
Feb 20, 2021
Issue #451 Add info concerning combining events and also add more to determination of side-band activity.
towsey
added a commit
that referenced
this issue
Feb 22, 2021
…ilters Issue #451 In particular provide more info on side-band activity filters. Also temporarily comment out calls to method that writes the results.csv file because it is not working.
towsey
added a commit
that referenced
this issue
Feb 23, 2021
Issue #451 These recognizers are either not needed or are unusable and would be extremely difficult to resurrect. Their development was discontinued around 2015 when they were in an embryonic state.
towsey
added a commit
that referenced
this issue
Feb 23, 2021
Issue #451 1: Add some booleans into the config file to control event filtering. 2: Edit the Call Recognizer Guide to reflect recent changes in the names of config parameters. 3: Remove a unit test for a discontinued call recognizer.
towsey
added a commit
that referenced
this issue
Feb 24, 2021
Issue #451 Rewrite the event detection/post-processing algorithm so that post-processing steps are performed for each level of decibel detection threshold. The guide.md file has been edited to explain this change and to make it consistent with changes to the config parameter names.
towsey
added a commit
that referenced
this issue
Feb 24, 2021
towsey
added a commit
that referenced
this issue
Feb 25, 2021
Issue #451 Final changes to the use of post-processing parameters in config files.
towsey
added a commit
that referenced
this issue
Feb 25, 2021
Issue #451 Changes to config.yml files and to generic recognizer tests to accommodate changes to post-processing parameters.
towsey
added a commit
that referenced
this issue
Feb 26, 2021
Issue #451 Major changes were to allow some parameter values to be nullable to avoid the use of booleans.
towsey
added a commit
that referenced
this issue
Feb 26, 2021
Issue #451 Remove an unnecessary line inserted into a unit test.
towsey
added a commit
that referenced
this issue
Feb 26, 2021
Issue #451 All these changes are to do with post-processing of acoustic events.
towsey
added a commit
that referenced
this issue
Mar 1, 2021
towsey
added a commit
that referenced
this issue
Mar 2, 2021
Issue #451 Changes to documentation involved shifted some documentation to other guides and to class summaries.
towsey
added a commit
that referenced
this issue
Mar 2, 2021
Issue #451 A few further changes to make a parameter available to the user with changes accordingly to the documentation.
towsey
added a commit
that referenced
this issue
Mar 3, 2021
Issue #451 Made some final tweaks to the guide.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please describe your problem.
The call recognizers need to offer the user more feedback at the post processing and filtering steps. The small amount of feedback currently provided is extremely useful but could be amplified.
Currently it is difficult to figure out why a particular filter is having the effect that it does.
The text was updated successfully, but these errors were encountered: