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
Hi, I am very new to kilosort, I encountered a problem that looks like many people had encountered before, after reading the old issue posts, it seems that the previous issues were mostly caused by a mismatch of channel count, after checking my data it seems not my case, can someone help me figure out why? I had a short recording with 128 recording channels and 8 ADC channels, so I create a channel map with the last 8 channel set to disconneted. This is a test dataset with only channel 112 with realy spikes, is that a problem? I previously used kilosort with our 16 channel data with more spikes in most channels it worked fine. Data in openephys binary format.
Hi, I am very new to kilosort, I encountered a problem that looks like many people had encountered before, after reading the old issue posts, it seems that the previous issues were mostly caused by a mismatch of channel count, after checking my data it seems not my case, can someone help me figure out why? I had a short recording with 128 recording channels and 8 ADC channels, so I create a channel map with the last 8 channel set to disconneted. This is a test dataset with only channel 112 with realy spikes, is that a problem? I previously used kilosort with our 16 channel data with more spikes in most channels it worked fine. Data in openephys binary format.
Data and channel map at:https://drive.google.com/drive/folders/1htXZH4Y9C6p1KRAc4DvDcLMRnaOfjakY?usp=sharing
Error message:
Error using gpuArray/subsasgn
An unexpected error occurred trying to launch a kernel. The CUDA error was:
invalid configuration argument
Error in extract_spikes (line 97)
st(5,:) = cF;
Error in ksGUI/runSpikesort (line 795)
[obj.rez, st3, tF] = extract_spikes(obj.rez);
Error in ksGUI>@(
,)obj.runSpikesort() (line 339)'Callback', @(
,)obj.runSpikesort());Error while evaluating UIControl Callback.
The text was updated successfully, but these errors were encountered: