-
Notifications
You must be signed in to change notification settings - Fork 222
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
Positive crossing detection #33
Comments
The step you point out to find good channels is independent of how the rest of Kilosort2 works. The amplitudes are the positive scalar values that multiply the templates to best match the raw data spike. The reason your axonal templates get cut off is that they have very small spatial extent, and they therefore get lost in-between the sites as the probe drifts. You can even see them emerging from the noise as they come into view when the probe drifts. There is nothing anyone can do here I'm afraid to recover the data in-between channels. You can try reducing the amplitude even further (it's already very low at 4) but I doubt you'll be better able to separate them from the background. |
Closing for inactivity. |
Going ahead with the merge. Will submit a new PR if additional steps are needed to facilitate GUI plots.
Hi!
First of all thanks for the really useful piece of software you have built.
We are a bit confused about the interaction of kilosort with positive spikes. In the wiki it reads:
"First we determine which channels contain significant numbers of negative threshold crossings ". However when we are looking in phy, very often we encounter waveforms like the following:
Interestingly, however, these cells tend to get hard cut from the noise very frequently. Hence my question is: does the amplitude view calculate the overall amplitude of the waveform (be it positive or negative) OR does it only take into consideration the negative deflection component of the waveform?
The text was updated successfully, but these errors were encountered: