<p><code>PAMpal</code> has been updated so that it can now read in Click Train Detector data (requires v0.20.0 or later). As of this writing it is only available on GitHub, not yet on the CRAN build.</p>
<p>By default it will now read in Click Train Detector click trains when processing with <code>mode='db'</code>, so if you are following the tutorial materials that is the processing mode you want to use for working with the click trains. Click train events will have the prefix &quot;CT&quot; before the event number (compared to &quot;OE&quot; for click events and &quot;DGL&quot; for Detection Grouper events). Click trains will be read in as separate &quot;events&quot; in <code>PAMpal</code>.</p>
<p>Default behavior when processing with <code>mode='db'</code> is to read in all types of events - from the Click Detector Offline Events, Detection Grouper, and now from the Click Train Detector. If you want to read in <em>only</em> click train data, you can use</p>
<pre><code>clickTrainOnly &lt;- processPgDetections(pps, mode='db', grouping='clickTrain')
</code></pre>

CC BY-SA 4.0
2023-06-28T20:28:31.767Z
2023-06-28T20:28:31.767Z
Taiki Sakai
<p>I am processing some data collected with a towed array, where we aimed to detect a species of porpoise in Peru. After setting up the click detector, I am trying now to add the click train detector module to improve the classification as porpoises but I am finding it quite complicated and confusing.</p>
<p>The main thing that I would like to receive some help with is extracting the results from the click trains with R (preferably) or Matlab. I've been checking the PAMpal guide to extract the info from Pamguard but I can't find anything regarding the click train module (or at least not that I know because I get really confused with the click train identification inside of the click detector), so how can I extract the click trains from the module???</p>
<p>Besides, I think I got an okay configuration for the click trains but this definitely could be improved, as it is taking many trains but skipping also quite a lot. Here I attach an image of my pamguard viewer, where it detected 2 good click trains but it missed the first one, which to me looks almost the same as the other two. In the image you can see also my current click train settings. If anyone has any idea of how to improve it it would be great.</p>
<p>Thank you in advance for any help!
Ruth</p>
<p><a href="https://i.sstatic.net/lP6m4.png" rel="noreferrer"><img src="https://i.sstatic.net/lP6m4.png" alt="This is an example of my click detector missing click trains" /></a></p>

CC BY-SA 4.0
2023-06-13T22:30:28.413Z
Ruth-- Welcome to Bioacoustics Stack Exchange! The PAMpal package accesses data from the click, whistle & moan, cepstral, and GPL detector, but it does not include the click train detector (at this time, anyhow!). Sorry! One of the main developers of the click train module is on Paternity leave-- hopefully someone else can help you in his absence (I have not used this).
Shannon
CC BY-SA 4.0
2023-06-17T11:35:47.703Z
@Shannon  Thank you for your reply! I see, then I think I'll skip this for now, I hope they will release a way to extract this info soon
Ruth
<pamguard><r><data-processing><matlab>
Extracting Click trains (from the click train module) in R
# Extracting Click trains (from the click train module) in R

(Asked by: username_0 on 2023-06-12)

I am processing some data collected with a towed array, where we aimed to detect a species of porpoise in Peru. After setting up the click detector, I am trying now to add the click train detector module to improve the classification as porpoises but I am finding it quite complicated and confusing.

The main thing that I would like to receive some help with is extracting the results from the click trains with R (preferably) or Matlab. I've been checking the PAMpal guide to extract the info from Pamguard but I can't find anything regarding the click train module (or at least not that I know because I get really confused with the click train identification inside of the click detector), so how can I extract the click trains from the module???

Besides, I think I got an okay configuration for the click trains but this definitely could be improved, as it is taking many trains but skipping also quite a lot. Here I attach an image of my pamguard viewer, where it detected 2 good click trains but it missed the first one, which to me looks almost the same as the other two. In the image you can see also my current click train settings. If anyone has any idea of how to improve it it would be great.

Thank you in advance for any help!
username_0

[![This is an example of my click detector missing click trains](https://i.sstatic.net/lP6m4.png)](https://i.sstatic.net/lP6m4.png)

**Tags:** pamguard, r, data-processing, matlab

> **Comments:**
> **username_1**: username_0-- Welcome to Bioacoustics Stack Exchange! The PAMpal package accesses data from the click, whistle & moan, cepstral, and GPL detector, but it does not include the click train detector (at this time, anyhow!). Sorry! One of the main developers of the click train module is on Paternity leave-- hopefully someone else can help you in his absence (I have not used this).  
> **username_0**: @username_1  Thank you for your reply! I see, then I think I'll skip this for now, I hope they will release a way to extract this info soon  

---

## 1 answers

### Answer by username_2 on 2023-06-28. Score: 3

`PAMpal` has been updated so that it can now read in Click Train Detector data (requires v0.20.0 or later). As of this writing it is only available on GitHub, not yet on the CRAN build.

By default it will now read in Click Train Detector click trains when processing with `mode='db'`, so if you are following the tutorial materials that is the processing mode you want to use for working with the click trains. Click train events will have the prefix "CT" before the event number (compared to "OE" for click events and "DGL" for Detection Grouper events). Click trains will be read in as separate "events" in `PAMpal`.

Default behavior when processing with `mode='db'` is to read in all types of events - from the Click Detector Offline Events, Detection Grouper, and now from the Click Train Detector. If you want to read in *only* click train data, you can use

```
clickTrainOnly <- processPgDetections(pps, mode='db', grouping='clickTrain')

```


---

