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

Cluster amplitude is missing … #292

Closed
rivlinoa opened this issue Dec 6, 2020 · 1 comment · Fixed by #595
Closed

Cluster amplitude is missing … #292

rivlinoa opened this issue Dec 6, 2020 · 1 comment · Fixed by #595

Comments

@rivlinoa
Copy link

rivlinoa commented Dec 6, 2020

I am trying Kilosort2.5 on Neuropixels1.0 data (used Kilosort2 up till now). I don’t know if my question addresses a change from Kilosort2 to kilosort2.5 or am I doing something wrong in the installation or usage.
When I try to go over the sorting results in Phy I cannot see clusters amplitude in the clusters view. I find the amplitude a useful metric for throwing noise clusters, which are usually of low amplitude. If I look at the files in the folder, there is no ‘cluster_Amplitude.tsv’ that used to be there for Kilosort2, and in ‘cluster_info.tsv’ there is no column for cluster amplitude like I used to have before. Moreover, there is no ‘cluster_KSlabel.tsv’ file, whereas ‘cluster_group’ contained KS labels overwritten by my manual labels in Phy …
If I am missing something, I would be happy to get any advice.
If those parameters are indeed missing from Kilosort2.5 would you consider adding them again?
Thank you very much!
Noa

@rajatsaxena
Copy link
Contributor

I have run the recent version, and it saves the cluster_Amplitude.tsv and cluster_KSlabel.tsv as well as the amplitude in the info file. Are you sure that you have the most recent version?

Another possibility is that there was an error in the rezToPhy.m script while saving the output, and you missed that?

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