Spikes after the end of the recording.

cortex-lab / phy

phy: interactive visualization and manual spike sorting of large-scale ephys data

BSD 3-Clause "New" or "Revised" License

311 stars 157 forks source link

Spikes after the end of the recording. #1142

Closed ensorpalacios closed 2 months ago

ensorpalacios commented 2 years ago

Hello, I'm seeing this message when opening params.py with phy template-gui: 'there are xx/xxx spikes after the end of the recording. It seams the same issue of #953 '. I spikesorted dataset 1, 2 and 3 (with KS3), and manually curated 1, 2, 3 in this order and before spikesorting the next one. Once I finished with the third one, if I try to open again dataset 1 and 2 it throws this message, and I notice that the length of the recording is equal to dataset 3. Any idea how to solve this? Thanks

zm711 commented 2 months ago

This occurs with Kilosort sometimes. SpikeInterface can help clean this up. We are not sure why this happens.