-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Severe over-splitting in KS3 #551
Comments
To clarify, many of these spikes are counted as being part of multiple neurons (multiple overlapping colors not visible in traceview above). This keeps me from merging the clusters, because it would result in a very high number of 0 ms refractory period violations |
I'm having the same issue, quite identical issue actually. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to optimize my sorting pipeline for my 64-channel Neuronexus mouse cortex recordings. For sessions with many clear spikes, ks2.5 and ks3 perform decent enough, where only minimal manual merging / splitting is necessary. However, sessions with slightly more noise or fewer good units tend to be sorted very poorly. In these cases, ks tends to split the data in many "good" neurons, with only a few hundred spikes each (on a 60-90 minute recording). When looking at the traceview, it is clear that over splitting is happening (see image below for an example, ks3 + default settings).
I'd like to do a parameter sweep and re-sort the same session to see how clustering is affected. Which parameters, and which ranges, make sense in this case?
Thanks in advance!
The text was updated successfully, but these errors were encountered: