Skip to content
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

Closed
RikkelBob opened this issue Jun 26, 2023 · 4 comments · Fixed by #595
Closed

Severe over-splitting in KS3 #551

RikkelBob opened this issue Jun 26, 2023 · 4 comments · Fixed by #595

Comments

@RikkelBob
Copy link

RikkelBob commented Jun 26, 2023

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!

Capture2

@RikkelBob
Copy link
Author

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

@kingsEffy
Copy link

I'm having the same issue, quite identical issue actually.

@kingsEffy
Copy link

I'm having the same issue, quite identical issue actually.

Screenshot 2024-02-02 133716

@kingsEffy
Copy link

I'm having the same issue, quite identical issue actually.

Screenshot 2024-02-02 133716
find this example, you can see actually green spikes and grouped together with artifacts - the large amplitude across all channels..

anyone know why is this happening?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants