Duplicate spikes should be removed before SLAy refractory period penalty calculated

[corbennett]

I often see that when putative oversplitting occurs there are "duplicate spikes" that get assigned to both clusters, giving a very large peak near 0 in the cross correlogram (see example below). This makes it difficult for SLAy to find such merges given the refractory period violation penalty (indeed, it doesn't find the one below unless you set k2 to 0). We should probably filter out duplicate spikes before calculating the refractory period penalty. Also, these duplicate spikes should be removed after automerging (regardless of the algorithm used).

[alejoe91]

Hi @corbennett

I'll think that's a very good idea. Would you say that removing just the 0 bin is enough? Or would it be better to discard a small delta (e.g. 0.1 Ms)?

We have a censor_period parameters when it comes to the actual merging/apply curation to remove duplicated spikes

[corbennett]

I think it's probably better to have a small delta as you suggest to account for jitter in the times assigned to the two clusters.