<p>For our project, we also expected both dolphins and porpoises, so we set the integration time to an intermediate value of 100μs. We raised the threshold to 12dB because it was quite a noisy environment, but indeed 10dB will be more conservative. We kept all the other settings as default. Regarding the integration time, we choose a middle value following recommendation from the manual, but didn't assess how exactly it worked compared to other settings (yet!).</p>
<p>On the endurance, we were also worried about the space the click detections would take in the SoundTrap (HF500), so we added memory cards, but that caused us more problems (see an answer to <a href="https://bioacoustics.stackexchange.com/questions/320/problems-with-soundtrap-500s">this post</a>)... In the end we used the default internal memory and were still able to get 5+ months on a 1/3 duty cycle, so it didn't seem to use up so much memory.</p>
<p>Hope this helps!</p>

CC BY-SA 4.0
2022-10-18T10:37:52.717Z
2022-10-18T10:37:52.717Z
Morgane
<p>Similarly to Morgane, during our recent long-term PAM project on the Scottish west coast we used an integration time of 100μs and 12 dB as the threshold, we raised the blanking time slightly to 2000μs and left the pre/post trigger at 750μs. These settings were aimed at finding a compromise between being able to detect dolphins and porpoises. We arrived at these setting by doing some tests with the Porpoise Alert (PAL) device before deployment.
We had good success with these settings, detecting both porpoises and various dolphin species successfully. However, more tests of these settings in the field and in comparison to full bandwidth recoridngs would be very useful, indeed.
During our project we achieved about 3 months deployment time for the Strap 300HF with battery pack, when recording at at duty cycle of 20/40 and 96 kHz sampling rate and the click detector turned on.</p>

CC BY-SA 4.0
2022-10-25T11:34:17.873Z
I should precise that besides the manual recommendation, we also aligned our settings on that of the project Denise is talking about, for consistency across datasets :)
Morgane
CC BY-SA 4.0
2022-10-22T12:27:07.123Z
2022-10-22T12:27:07.123Z
DeniseR
<p>We use them for clicky things too, mostly porpoise though we have gotten killer whales as well, so pretty broad spectrum.</p>
<p>We go with the default manufacturer settings and, like the C-PODs it's a pretty high recall detection system. So it's likely to catch most things. That said TWICE the manufacture has sent us instruments with faulty settings that needed to be cleared before we put them in the water. We missed it the first time and it crapped out the entire recording system. So...be careful of that :). I'll see if I can dig them up from our reports if that would be helpful!</p>

CC BY-SA 4.0
2022-10-26T03:52:20.250Z
2022-10-26T03:52:20.250Z
K.J. Palmer
<p>We are deploying a number of SoundTrap ST600s and are currently trying to determine the best parameters for the click detector. We are most likely to encounter Harbour Porpoise and Bottlenose Dolphins, and potentially Risso's and other dolphins. The parameters are:</p>
<ul>
<li>Threshold: we are thinking of using 10 dB to be conservative.</li>
<li>Integration time: the <a href="http://www.oceaninstruments.co.nz/wp-content/uploads/2020/12/ST600-User-Guide.pdf" rel="noreferrer">ST user guide</a> suggests 70 μs for most delphinids and 150-300 μs for porpoises and NBHF delphinids.</li>
<li>Blanking time: currently using the default 1000 μs.</li>
<li>Snippet pre- and post-trigger durations: we have been using the default 750 μs for each. The ST user guide states <code>&quot;The snippet starts pre-trigger seconds before the detection and ends post-trigger seconds after the detection.&quot;</code> Does this mean the post-trigger snippet begins after the start or end of the detection? I.e. should we be using a longer post-trigger snippet length to account for the signal duration?</li>
</ul>
<p>I wondered if anyone has used the ST600 click detector for similar species and has recommendations.</p>
<p>I also notice that the endurance calculator doesn't factor in the click detector and wondered if anyone has any advice about energy usage when the click detector is running.</p>

CC BY-SA 4.0
2022-10-17T13:07:23.150Z
Hi EmmaL, I understand that you have at least 2 distinct questions (last bullet point and last paragraph), maybe you could make 2 different posts instead of 1 (see [here](https://bioacoustics.meta.stackexchange.com/q/136/73) for more info) or do you think they could be related to each other?
Noil
<pam><soundtrap><echolocation-clicks><dolphins><porpoise>
SoundTrap ST600 click detector for delphinids and porpoises
# SoundTrap ST600 click detector for delphinids and porpoises

(Asked by: username_0 on 2022-10-17)

We are deploying a number of SoundTrap ST600s and are currently trying to determine the best parameters for the click detector. We are most likely to encounter Harbour Porpoise and Bottlenose Dolphins, and potentially Risso's and other dolphins. The parameters are:

* Threshold: we are thinking of using 10 dB to be conservative.
* Integration time: the [ST user guide](http://www.oceaninstruments.co.nz/wp-content/uploads/2020/12/ST600-User-Guide.pdf) suggests 70 μs for most delphinids and 150-300 μs for porpoises and NBHF delphinids.
* Blanking time: currently using the default 1000 μs.
* Snippet pre- and post-trigger durations: we have been using the default 750 μs for each. The ST user guide states `"The snippet starts pre-trigger seconds before the detection and ends post-trigger seconds after the detection."` Does this mean the post-trigger snippet begins after the start or end of the detection? I.e. should we be using a longer post-trigger snippet length to account for the signal duration?

I wondered if anyone has used the ST600 click detector for similar species and has recommendations.

I also notice that the endurance calculator doesn't factor in the click detector and wondered if anyone has any advice about energy usage when the click detector is running.

**Tags:** pam, soundtrap, echolocation-clicks, dolphins, porpoise

> **Comments:**
> **username_1**: Hi username_0, I understand that you have at least 2 distinct questions (last bullet point and last paragraph), maybe you could make 2 different posts instead of 1 (see [here](https://bioacoustics.meta.stackexchange.com/q/136/73) for more info) or do you think they could be related to each other?  

---

## 3 answers

### Answer by username_2 on 2022-10-18. Score: 5

For our project, we also expected both dolphins and porpoises, so we set the integration time to an intermediate value of 100μs. We raised the threshold to 12dB because it was quite a noisy environment, but indeed 10dB will be more conservative. We kept all the other settings as default. Regarding the integration time, we choose a middle value following recommendation from the manual, but didn't assess how exactly it worked compared to other settings (yet!).

On the endurance, we were also worried about the space the click detections would take in the SoundTrap (HF500), so we added memory cards, but that caused us more problems (see an answer to [this post](https://bioacoustics.stackexchange.com/questions/320/problems-with-soundtrap-500s))... In the end we used the default internal memory and were still able to get 5+ months on a 1/3 duty cycle, so it didn't seem to use up so much memory.

Hope this helps!


---

### Answer by username_3 on 2022-10-22. Score: 3

Similarly to username_2, during our recent long-term PAM project on the Scottish west coast we used an integration time of 100μs and 12 dB as the threshold, we raised the blanking time slightly to 2000μs and left the pre/post trigger at 750μs. These settings were aimed at finding a compromise between being able to detect dolphins and porpoises. We arrived at these setting by doing some tests with the Porpoise Alert (PAL) device before deployment.
We had good success with these settings, detecting both porpoises and various dolphin species successfully. However, more tests of these settings in the field and in comparison to full bandwidth recoridngs would be very useful, indeed.
During our project we achieved about 3 months deployment time for the Strap 300HF with battery pack, when recording at at duty cycle of 20/40 and 96 kHz sampling rate and the click detector turned on.

> **Comments:**
> **username_2**: I should precise that besides the manual recommendation, we also aligned our settings on that of the project Denise is talking about, for consistency across datasets :)  

---

### Answer by username_4 on 2022-10-26. Score: 2

We use them for clicky things too, mostly porpoise though we have gotten killer whales as well, so pretty broad spectrum.

We go with the default manufacturer settings and, like the C-PODs it's a pretty high recall detection system. So it's likely to catch most things. That said TWICE the manufacture has sent us instruments with faulty settings that needed to be cleared before we put them in the water. We missed it the first time and it crapped out the entire recording system. So...be careful of that :). I'll see if I can dig them up from our reports if that would be helpful!


---

