Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ketos ketos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • public_projects
  • ketosketos
  • Merge requests
  • !221

Merged
Created Nov 28, 2021 by Oliver Kirsebom@kirsebomOwner

Generalized detection functions to handle multiple threshold vlaues

  • Overview 0
  • Commits 2
  • Pipelines 2
  • Changes 2

I have generalized the functions in the detection module so that users can specify a list of threshold values as opposed to a single value. Previously, the user had to call the functions repeatedly. This created a processing overhead since for every call, the same spectrograms had to be computed and passed through the trained network. Now, the repeated parts (load audio, compute spectrogram, pass through network) are only done once.

Edited Dec 08, 2021 by Oliver Kirsebom
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: detection_multiple_thresholds