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

Contamination Percent #143

Closed
sina253 opened this issue Nov 25, 2019 · 6 comments · Fixed by #595
Closed

Contamination Percent #143

sina253 opened this issue Nov 25, 2019 · 6 comments · Fixed by #595
Labels
bug Something isn't working

Comments

@sina253
Copy link

sina253 commented Nov 25, 2019

Hi
Kilosort2 calculating a value named: ContamPct, which I guess should be contamination percentage.
For some of our sorting sessions this number is low for good labeled clusters and all 100 for the MUA labeled clusters. However, for the other sorting sessions ContamPct values are very different and are even more than 100 for clusters.

Is this a bug?

@marius10p
Copy link
Contributor

Share screenshots please. I don't know why it would be above 100.

@Stefxnia83
Copy link

Hi Marius,
I attached two example where you can see the value of the contamination percentage for all the multiunits is always 100. I also attached an example of a cluster labeled as good and the value of the contamination percentage is always 100.
Also, the data have been collected by a 96 channels Utah Array. The recording loci do not have different depths, but as you can see the channels are attributed to different depths and look like they are attributed to one shank. Could that affect the output of the sorting?

ContamPct_MUA_100
ContamPct_MUA_100_2
ContamPct_SUA_100

@marius10p
Copy link
Contributor

I am not sure why a cluster would be labelled as good even though the contamination is computed as 100%. I'll double check, but in any case, that label is meant to be used as guidance. Works very well on some data, and poorly on other data.

"Depth" is interpreted as the y-dimension of your channel map file. This won't really make an impact on the sorting in your case, it's just for visualization in Phy.

@JoseGuzman
Copy link
Contributor

I have exactly the same issue (see attached screenshot).
ContamPct

  • There are clusters with ContamPct = 100 labeled as 'good' (green line)
  • There are clusters with ContamPct > 100 (pink line)

I am not sure what can be the reason, but it seems to happen when the templates are on the same channel (see colors in the figure). I am using 128 channels from Cambridge Neurotech probes.

@Stefxnia83
Copy link

Thank you!

@marius10p
Copy link
Contributor

Ok, I'll have to look into that. Looks like the ones labelled as good with ContamPct=100 might have very few spikes. I thought I had a special case to exclude those, but I'll have to check it.

@marius10p marius10p added the bug Something isn't working label Dec 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants