Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CUDA error invalid configuration #453

Closed
dwhzlh2021 opened this issue Oct 24, 2021 · 1 comment · Fixed by #595
Closed

CUDA error invalid configuration #453

dwhzlh2021 opened this issue Oct 24, 2021 · 1 comment · Fixed by #595

Comments

@dwhzlh2021
Copy link

dwhzlh2021 commented Oct 24, 2021

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.

@gersgers
Copy link

Hi,
I have the same error. Did you find a solution?
Best.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants