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 using gpuArray/subasgn: Subscript indices must either be real positive integers or logicals. #360

Closed
jrnvndtslr opened this issue Mar 19, 2021 · 2 comments · Fixed by #595

Comments

@jrnvndtslr
Copy link

Hi,

I've been running into this error, while trying to run kilosort2. It occurs in the isolated_peaks_new function, but I suspect the issue is caused much earlier in the code. From some earlier entries (45 & 142) I gathered that it may have something to do with the number of batches. However, setting ops.NT to a lower value does not resolve it. The file I'm trying to process has an ops.sampsToRead value of 68046020. I could try downsampling but I don't know if/when this will affect the quality of the outcome.

Any thoughts on how to mitigate this issue?

@marius10p
Copy link
Contributor

It probably has to do with empty batches. If you really have batches with no spikes, then you should probably increase ops.NT substantially (by a factor of 8 or more). If you switch to kilosort3, then this shouldn't happen any more.

@jrnvndtslr
Copy link
Author

It turned out to be (partially) due to the fact that the GPU on our cluster loads the wrong CUDA version by default. I can get my data through now but only with very lenient criteria, and the result is all noise. If I high-pass filter the data at 150Hz and inspect the trace I also can't identify any spikes. Given that one of the first steps in KS2 is a threshold-based detection of z-scored data, I'm afraid I have to conclude that my data quality is just too poor for spike detection.

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