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

Incorrect use of gpuArray/subsref : when I was using 16 linear channel EP data #502

Closed
AmaranthCao opened this issue May 21, 2022 · 2 comments · Fixed by #595
Closed

Incorrect use of gpuArray/subsref : when I was using 16 linear channel EP data #502

AmaranthCao opened this issue May 21, 2022 · 2 comments · Fixed by #595

Comments

@AmaranthCao
Copy link

when I used KS to run my 16 linear channel EP data, after I clicked "run" , it returned following mistakes:

Time 0s. Computing whitening matrix..
Getting channel whitening matrix...
Channel-whitening matrix computed.
Time 1s. Loading raw data and applying filters...
Time 4s. Finished preprocessing 144 batches.

Incorrect use of gpuArray/subsref
Subscript indices must either be real positive integers or logicals.
Error extractTemplatesfromSnippets (56)
wTEMP = dd(:, round(linspace(1, size(dd,2), nPCs)));
Error datashift2 (line 4)
[wTEMP, wPCA] = extractTemplatesfromSnippets (rez, NrankPC);
Error ksGUI/runPreproc (line 732)
Obj. Rez = datashift2 (obj. Rez, 1);
Error ksGUI/runAll (line 633)
Obj. RunPreproc;
Error ksGUI> @(,) obj.runall () (line 321)
'Callback' @ (~, ~) obj. RunAll ());

Error calculating UIControl Callback.

Could anyone help solve this issue or explain why this happened?
Thanks a lot!

@GrimmSnark
Copy link

See issue #383 try using the try catch suggestion. That seemed to work for me.

Michael

@marius10p
Copy link
Contributor

It sounds like it did not find enough spikes for that step. This could be due to a variety of reasons. Check your data in the GUI to make sure the channel map is correct and the number of channels. If this is part of a longer recording, it could also help to try to spike sort the entire data at the same time to find more spikes. Try lowering the thresholds too (in advanced options).

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.

3 participants