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

Kilosort Sorting Flat "Clusters" #301

Closed
djsoper opened this issue Jan 5, 2021 · 10 comments · Fixed by #595
Closed

Kilosort Sorting Flat "Clusters" #301

djsoper opened this issue Jan 5, 2021 · 10 comments · Fixed by #595

Comments

@djsoper
Copy link

djsoper commented Jan 5, 2021

Hi,

I am having trouble using Kilosort2.5 to sort a Neuropixel recording which is approximately 10 minutes long. It will run through the sorting, but the Phy results leave me confused. Most of the clusters are nothing. They aren't noise or artifacts, they are just calm nothingness. Here is an example of one of the hundreds of "calm" units:
DBS05PHYExample

The strange thing to me is that the supposed amplitude listed for this is 108.53. I wouldn't care about those arbitrary units so much if the things that actually looked like units weren't so close in amplitude. one of the very few examples of potential units I got from this recording is here, and the amplitude is just shy of 150:
DBS05Chan141Unit

I'm very confused about this. Are the amplitudes relative/arbitrary for each cluster? Also, why are there so many (~300) clusters that are nothingness when it can clearly sort unit-like events. I'm very lost on this. Can you please help? I haven't changed the config file from its default(though I have tried changing some things around to no avail). Let me know if you want any more info.

Thanks,
Dan

@djsoper djsoper changed the title Kilosort Sorting Flat "Units" Kilosort Sorting Flat "Clusters" Jan 5, 2021
@sachira-denagamage
Copy link

I had been having a similar issue as well and tried what another user mentioned where they changed params.py to look at the raw binary instead of the drift corrected version. I think there is some issue with the drift corrected version being read into phy.

@marius10p
Copy link
Contributor

This appears to indeed be related to the drift-corrected binary file being weird. Were you setting ops.trange(1) to be larger than 0? I think this was a problem before, should be fixed now. Can you please try Kilosort3 and let me know if it's still an issue?

@rivlinoa
Copy link

rivlinoa commented Feb 4, 2021

I am having the same issue with Kilosort3, all units from lowest amplitude to highest are flat nothing... I used default settings on Neuropixels1.0 data.

@marius10p
Copy link
Contributor

I can't replicate this problem. Do you have ops.trange = [0 Inf], like the default? How many connected/disconnected channels do you have?

@rivlinoa
Copy link

rivlinoa commented Feb 4, 2021

I have ops.trange = [0 Inf],
and all the channels in the 1.0 probe are connected (384), ops.NchanTOT = 385
It happened in 2 ut of 3 files I have managed to analyze.

thanks!!!

@marius10p
Copy link
Contributor

If the 3rd one was good, can you tell what was different about it? Can you cut a very small section of your file (first 10sec), replicate the problem, and send it via dropbox or google drive? Thanks,

@rivlinoa
Copy link

rivlinoa commented Feb 4, 2021

There is nothing different (that I know of) with the successful file...
sure, I can send you a segment of one of the faulty files... where to send it to?

@marius10p
Copy link
Contributor

if you don't want to drop it here, please find my email address on the Cellpose paper.

@rivlinoa
Copy link

rivlinoa commented Feb 4, 2021

Hi Marius!
I was able to figure out what went wrong… the working directory and save directory didn’t update automatically in the GUI once I chose a bin file to process, and I missed it… so I got results saved in the previous run folder and loaded the wrong traces into phy.
thank you so much for the support! And sorry for the mistake …

@marius10p
Copy link
Contributor

No worries. I think this problem is fixed now, @djsoper feel free to reopen otherwise.

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.

4 participants