You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For 1: there are no settings to change for this problem, @marius10p is working on a fix.
For 2 and 3: I'll let @marius10p answer those.
For 4: Which version of Kilosort4 are you using? We changed the way template amplitudes are computed in 4.0.7, which should have fixed this problem.
Just clarifying, that does not suggest the same spike is being assigned to multiple units, just spikes with a similar waveform. Given that these are all from MUA units with low spike count, it's not that surprising and the "true" cluster for that waveform is probably showing up elsewhere. In fact, it looks like that's what you're seeing in 3).
Broadly speaking, yes it looks like some of those can be merged. Specifically all of them except the unit colored blue, since that one does not have a clear refractory period for the CCGs (but the other 4 do).
There aren't any settings to tweak to "fix" this, there are always going to be cases where merging doesn't work well. For example, here it looks like something happened during the recording around t=1000 that caused a big change in amplitudes, which can mess up the clustering as well - especially for probes with low channel count like this, where drift correction is not feasible.
Describe the issue:
Hi there!
I am using Kilosort4 for spike sorting with 4 tetrodes (16 channels) on a 30-minute recording. After analysis, I encountered two issues:
Similar to issue FEATURE: Correcting for misaligned spikes within units #664, I am experiencing misaligned spikes.
The same spike is being dispersed into different units.
There are five channels with spikes that look very similar. Is that proper that I merge them?
The template waveform and the mean waveform are very different:
Could you please help me with adjusting the parameters to achieve better spike sorting results? Thank you!
The text was updated successfully, but these errors were encountered: