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

Error pre-processing with single channel data #379

Closed
Rinkode opened this issue Apr 21, 2021 · 0 comments · Fixed by #595
Closed

Error pre-processing with single channel data #379

Rinkode opened this issue Apr 21, 2021 · 0 comments · Fixed by #595

Comments

@Rinkode
Copy link

Rinkode commented Apr 21, 2021

Greetings !
My lab is new to Kilosort and we would like to use it with our data, acquired with a single-channel probe, via LabChart. Unfortunately, when I start pre-processing, I get the following error :

Time  92s. Loading raw data and applying filters... 
Time 107s. Finished preprocessing 12 batches. 
Error using gpuArray/subsref
Subscript indices must either be real positive integers or logicals.

Error in extractTemplatesfromSnippets (line 56)
wTEMP = dd(:, round(linspace(1, size(dd,2), nPCs)));

Error in learnTemplates (line 19)
[wTEMP, wPCA]    = extractTemplatesfromSnippets(rez, NrankPC);

Error in learnAndSolve8b (line 35)
    rez     = learnTemplates(rez, rez.iorig);

Error in main_kilosort (line 45)
rez = learnAndSolve8b(rez, iseed);

We don’t know if the problem comes from :

  • The way we put our data in a .bin file
  • The probe file
  • Something else

I posted .mat and .bin files of the data + the probe file generated with Kilosort if it can help. https://github.com/Rinkode/Data_and_probe_for_kilosort

I want to point out that my lab was using Klusta before trying Kilosort. It was working well with our data, so there are spikes to be detected.

I would be very thankful to anyone who’ll take time to help me on this one.

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.

1 participant