-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Hi,
I tried to spikesort one of my recordings again due to many channels being removed from the first spikesorting. First i just changed the name of the last spikesorting in the folder and ran a new spikesorting without registering the action again (tested with auto_threshold 3, 2.5 and the default). I have also tried to register the action from scratch and run the spikesorting again. In all cases the mountainsort4 spikesorting is not working as it should and i end up with units with hundred thousands of spikes (see n_spikes in phy).
I also tested with another action, to make sure it was not related to the specific recording, but the same thing happened again. Both of these actions have been successfully spikesorted previously with mountainsort4 around october 2024 (which is around the time when both Sarah and i finished most of our spikesorting, so mountainsort4 has not been used much in 2025).