You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
Thank you,
The text was updated successfully, but these errors were encountered:
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.
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?
Thank you,
The text was updated successfully, but these errors were encountered: