SpikeInterface / SpikeInterface/spikeinterface
Duplicate spikes should be removed before SLAy refractory period penalty calculated
@alejoe91 is already working on this.
Since Apr 16, 2026.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
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).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.