As far as I know, in the click detector parameters, the max click length takes into account the max real click length, pre samples and post samples. In this way, max click length = pre samples + max real click length + post sample.
For a sample rate of 128 kHz, knowing from the literature that the maximum click length of a Tursiops Truncatus is 0.08 ms, this would be about 11 samples.
So if I put 11 samples for the max real click length plus 20 samples for pre and 20 samples for post, this would give a total of 50 samples for the maximum click length.
I've chosen to put 384 samples for the min click separation as the literature says that the minimum ICI for Tursiops Truncatus is 3 ms.
I ran a test with the following click length tab of the click detector:
Min click separation: 384 samples
Max click length: 50 samples
Pre-sample: 20 samples
Post-sample: 20 samples
After this configuration, the detector detects a lot of clicks, and that's maybe because it is dividing one click into several clicks because of choosing these parameters.
However, if I choose 256 samples (2 ms) as the maximum click length with a pre sample of 80 and a post sample of 80, the max real click length that it would consider would be 256-160 =96 samples. 96 samples would be around 0.7 ms which is almost 10 times larger than the maximum click length following literature...
Min click separation:384 samples
Max click length: 256 samples
Pre-sample: 80 samples
Post-sample: 80 samples
Also, in the click classifier I am setting a click length range of 0 to 0.8 because if I follow literature ( setting 0 to 0.08 as the click length range of the click detector), the program doesn't detect anything.
Maybe Pamguard is not considering as click length the same as what the literature considers.
My recordings have a lot of noise so Tursiops could change the temporal characteristic of the click but I think 10 times larger is a lot.
I'd really appreciate if someone could help me.
Thank you.