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
Thank you for your code and very impressive explanation,
I am a spike-sorting beginner. I have a stupid question, the example shown used a single-channel ncs file. How to handle the multiple channel data. when the recording lasts a few hours or even more.
i have an idea(stupid again),
e.g., 32 channels last 6 hours.
cut the 6 hours into 1-minute epochs?
then detect spikes for all 32 channels?
many thanks for considering my request. I am always confused about how to manage this.
The text was updated successfully, but these errors were encountered:
Hi @Jianfengliu0413,
sorry for my delayed response just saw your message. The approch that you outlined in your comment will most likely identify spikes within the each epoch but will define different clusters for every epoch. Therefore you will have a hard time monitoring the activity of the same cluster across your recording.
The code in this notebook is an outline of the common principle of spike sorting. However, it is not a state of the art method.
I recommend for datasets like yours to use more advanced and peer-reviewed approaches like Kilo-Sort.
Thank you for your code and very impressive explanation,
I am a spike-sorting beginner. I have a stupid question, the example shown used a single-channel ncs file. How to handle the multiple channel data. when the recording lasts a few hours or even more.
i have an idea(stupid again),
e.g., 32 channels last 6 hours.
cut the 6 hours into 1-minute epochs?
then detect spikes for all 32 channels?
many thanks for considering my request. I am always confused about how to manage this.
The text was updated successfully, but these errors were encountered: