Drifting issue about kilosort HOT 1 OPEN

Hi Dario - one parameter you can play with is the number of templates you ask to be fit (ops.Nfilt). If you make this smaller, Kilosort will do the best it can with that restriction and so it'll end up being more inclusive about which spikes get included in each template, i.e. it should do some of the merging for you. However there is a tradeoff in that you will also get more instances in which spikes from separate neurons are incorrectly combined into a single template, requiring you to split them out. Since splitting takes longer and is more error-prone than merging, the general recommendation is to err on the side of doing more merging.

More generally, of course everyone's recordings do have drift including ours so we are definitely aware of the problem. The Neuropixels probes potentially offer a great opportunity to overcome this computationally since the same neurons are usually still observed by some other sites when the brain moves. Marius has been working on an implementation of a post-hoc drift correction, and he'll have to provide you with more details, but the short answer is we don't have any working solution for it yet.

Nick

from kilosort.