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 GUI shows no prediction before clustering #485

Closed
Minako-375 opened this issue Mar 25, 2022 · 2 comments · Fixed by #595
Closed

kilosort GUI shows no prediction before clustering #485

Minako-375 opened this issue Mar 25, 2022 · 2 comments · Fixed by #595

Comments

@Minako-375
Copy link

Minako-375 commented Mar 25, 2022

Hi
I have some trouble with kilosort GUI and spike extraction.

After the preprocessing, no spikes are detected as a "prediction" and "residual" is completely the same as a "filtered".
I also checked colormap mode but it was the same with trace mode.

I use neuropixels1.0 for recording and kilosort2.5 for manual clustering with default parameters.

After the clustering step, GUI shows the "right" prediction and residual.

Is it possible to show prediction and residual before clustering?
Because clustering takes a lot of time, it would be helpful if I could check the parameters of preprocessing before clustering.

Does anyone have some suggestions?

filtered
prediction
residual

Thank you,

@Minako-375 Minako-375 changed the title kilosort GUI shows no prediction kilosort GUI shows no prediction before clustering Apr 6, 2022
@Minako-375 Minako-375 reopened this Apr 6, 2022
@GrimmSnark
Copy link

Hello,

As far as I understand it, they GUI just tries to plot the calculated spike extractions in the predicted and residuals. So if you have not run the full KS pipeline then they will be blank and then the same as filtered, respectively.

The only thing I can suggest to quickly go through a variety of parameter values is to either cut down on the number of channels or reduce the timeframe for the analysis.

Best,

Michael

@Minako-375
Copy link
Author

Thank you for your answer.
I'll try to reduce the timeframe to find good paramaters.

Best,

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