Body: <p>I am wondering if anyone has had success using the package <code>ohun</code> for energy-based detection and successful evaluation of their detection routines. I have used the <a href="https://marce10.github.io/ohun/" rel="nofollow noreferrer">vignette</a> to learn a lot, but I am coming upon regular challenges and would love to speak with others about it.</p>
  <p>My main challenge with <code>ohun</code> right now has to do with the detection of true positives calculated upon using <code>optimize_energy_detector()</code>. I noticed that the number of “Total Detections” and “True Positives” is always the same, when I thought (based on signal detection theory and the vignette) that the number of total detections should probably include the sum of true positives and false positives. Perhaps more importantly, I am finding that when I use <code>optimize_energy_detector()</code>, I find MORE true positives in the sound file than exists in the reference file I have created (selection table). For example, my reference table has 24 sounds called snap-jumps, and <code>optimize_energy_detector()</code> counts 59 total detections, 59 true positives, and 10 false positives. Somehow, the package is finding more sounds - and calling them true positives - than there could possibly be. This does not make sense to me, and does not make sense based on the description of how the package works (I could be missing something). I saw on <a href="https://bioacoustics.stackexchange.com/questions/295/software-options-for-diagnosing-the-performance-of-a-detection-routine">this page</a> that @lostanlen mentioned a problem with counting true positives, and I wonder if that is related to the problem I'm having. Thanks in advance folks.</p>
  <p>Kristen</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-11-30T03:09:34.773Z
Comments.Text: Have you reached out to Marcelo (the package creator) about your issues? He would probably be in the best position to help.
Comments.UserDisplayName: Carly Batist
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-11-30T21:31:07.460Z
Comments.Text: Hi! Yes I have, but not yet about this particular issue. However, it seems like he is really busy or unable to respond, so I thought it best to try on here and see if others have tried the package. Thank you for your help!
Comments.UserDisplayName: ksh530
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-12-01T08:03:10.120Z
Comments.Text: Yeah, ohun is a fairly new package so I think people are just learning about it/trying it out now! His other more matured packages (like warbleR) have more users/resources just due to time. Sorry I couldn't be of more help!
Comments.UserDisplayName: Carly Batist
Tags: <signal-detection><ohun>
Title: Question on true positives calculated in R package ohun
ThreadText: # Question on true positives calculated in R package ohun
  
  (Asked by: username_0 on 2022-11-29)
  
  I am wondering if anyone has had success using the package `ohun` for energy-based detection and successful evaluation of their detection routines. I have used the [vignette](https://marce10.github.io/ohun/) to learn a lot, but I am coming upon regular challenges and would love to speak with others about it.
  
  My main challenge with `ohun` right now has to do with the detection of true positives calculated upon using `optimize_energy_detector()`. I noticed that the number of “Total Detections” and “True Positives” is always the same, when I thought (based on signal detection theory and the vignette) that the number of total detections should probably include the sum of true positives and false positives. Perhaps more importantly, I am finding that when I use `optimize_energy_detector()`, I find MORE true positives in the sound file than exists in the reference file I have created (selection table). For example, my reference table has 24 sounds called snap-jumps, and `optimize_energy_detector()` counts 59 total detections, 59 true positives, and 10 false positives. Somehow, the package is finding more sounds - and calling them true positives - than there could possibly be. This does not make sense to me, and does not make sense based on the description of how the package works (I could be missing something). I saw on [this page](https://bioacoustics.stackexchange.com/questions/295/software-options-for-diagnosing-the-performance-of-a-detection-routine) that @lostanlen mentioned a problem with counting true positives, and I wonder if that is related to the problem I'm having. Thanks in advance folks.
  
  Kristen
  
  **Tags:** signal-detection, ohun
  
  > **Comments:**
  > **username_1**: Have you reached out to Marcelo (the package creator) about your issues? He would probably be in the best position to help.  
  > **username_0**: Hi! Yes I have, but not yet about this particular issue. However, it seems like he is really busy or unable to respond, so I thought it best to try on here and see if others have tried the package. Thank you for your help!  
  > **username_1**: Yeah, ohun is a fairly new package so I think people are just learning about it/trying it out now! His other more matured packages (like warbleR) have more users/resources just due to time. Sorry I couldn't be of more help!  
  
  ---
  
  ## 0 answers
  
  