Marius Pachitariu

It sounds like it did not find enough spikes for that step. This could be due to a variety of reasons. Check your data in the GUI to make sure...

Can you please confirm that the path is pointing only to Kilosort2.5 and you compiled the mex files successfully? Also please copy paste here the output of "gpuDevice(1)" in Matlab.

I am not sure these are all the same problem. The error occurs when no spike is found in the raw data. This usually happens due to bad configurations such...

Kilosort2 does not have that spike detection step. You can try reducing ops.spkTh to -4 or something like that so it can catch more spikes for that step. Are your...

Can you please try my recommendation above and answer my question?

We are trying to decide where the plugins should go, and will merge this in after we decide.

I never had a chance to merge this. @jenniferColonell do you think you could resolve the conflicts before I merge this in? Thanks.

I think the channel number is decided by Phy, which takes them consecutively from the channel map of connected channels. When KS2 sets a channel as bad, it just sets...

I don't think so, I just looked.

but the GUI doesn't actually show the channel map numbers from channel_map.npy.