The Visual Coding Neuropixels dataset has not changed since it was initially released in 2019, so it doesn’t have this fix applied. It is unlikely we will resort everything with the patched version of Kilosort – given that the bug results in at most 0.3% of spikes being missed, we do not think it will impact scientific conclusions drawn from this dataset.
I have a couple of follow-up questions if you don’t mind.
1. For the Neuropixels dataset, was the default batch size of Kilosort2 used for the spike sorting?
2. Could you clarify how the estimate that at most 0.3% of spikes are missed was derived?