-
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
Changing parameter 'nt0' results in a crash #337
Comments
Sure, yes, but I think the CUDA code will crash with nt0 >61. Unless your data is recorded at >=50Khz, there shouldn't be a reason to change nt0. |
Could you please show that neuron in Phy with multiple snippets? I am curious if multiple events have the same stereotypical pattern after the initial depolarization. |
This example is very noisy overall. If the positive phase is stereotypical, but the rest of the spike is variable, then Kilosort won't be able to deal with that correctly. In that case, you are better off setting a small nt0, so the clusters don't get split by the variability in the complex part of the spike. It's possible the "tail" of the complex spike will be assigned to a noise unit, which is fine. |
Alright, thank you! |
Hi,
I tried running Kilosort with a different value for
nt0
(from 61 to 75), and I obtained this crash:From what I saw, this is because in
clustering/template_learning.m
, line 103,rez.W
is defined as:Shouldn't this
61
be replaced byops.nt0
?The text was updated successfully, but these errors were encountered: