a suggestion about the spike sorter
Page 1 of 1
a suggestion about the spike sorter
Because the "Electrode Raw Data" need huge amounts of disk space for long time recording. We often use spike sorters to keep the spike trains we need.
However, the inputs for "pre","post" and "dead time" must be integer in the current version (3.2.1.0). I don't think that's a good idea because I found that the exact waveform may play some important roles in the followed procedures.
Could you please make some changes about it? The "Offline sorter" (Plexon) gave much more choices based on the scale of microseconds.
However, the inputs for "pre","post" and "dead time" must be integer in the current version (3.2.1.0). I don't think that's a good idea because I found that the exact waveform may play some important roles in the followed procedures.
Could you please make some changes about it? The "Offline sorter" (Plexon) gave much more choices based on the scale of microseconds.
mcs- Posts : 518
Join date : 2008-06-10
Re: a suggestion about the spike sorter
Hello
Thank you for your suggestion.
I have added it to our MC_Rack ToDo list for the next release, and I have informed the reponsible software engineers.
Best wishes
Thank you for your suggestion.
I have added it to our MC_Rack ToDo list for the next release, and I have informed the reponsible software engineers.
Best wishes
mcs- Posts : 518
Join date : 2008-06-10
Similar topics
» Spike sorter
» Spike sorter
» A little suggestion for the release of MCSUSBNET api dll
» MC_Rack suggestion thread (please discuss)
» MEA suggestion
» Spike sorter
» A little suggestion for the release of MCSUSBNET api dll
» MC_Rack suggestion thread (please discuss)
» MEA suggestion
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum