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

GUI: Spikesorting of Neuropixels Sample Data Fails #92

Closed
AGenews opened this issue Jul 23, 2019 · 9 comments · Fixed by #595
Closed

GUI: Spikesorting of Neuropixels Sample Data Fails #92

AGenews opened this issue Jul 23, 2019 · 9 comments · Fixed by #595

Comments

@AGenews
Copy link

AGenews commented Jul 23, 2019

Dear Folks,
first of all, thanks for this great piece of software!

However, I have some problems running KiloSort2 on the admittedly huge sample data set Hopkins_20160722_g0_t0.imec.ap_CAR.bin from UCL found here.

My system:
Windows 10 Education, Intel i7-8700K, MATLAB 2016b, CUDA 7.5, GeForce RTX2080, 32GB RAM

I am using the GUI and the preprocessing works fine, however after ~10 min of spikesorting it fails telling me:
Error running kilosort! Undefined function 'zscore' for input arguments of type 'gpuArray'.

I hope this is not MATLAB 2016b related ...

Yours sincerely and many thanks!
Andreas

UPDATE:
... so I've just tested my install with the "not-drifting" sample data sim_binary.dat generated by KiloSort1 master_eMouse.m and this works nicely with KiloSort2!
I'll try to get the drifting version to run ....

@nsteinme
Copy link
Collaborator

nsteinme commented Jul 23, 2019 via email

@AGenews AGenews changed the title Spikesorting of Neuropixels Sample Data Fails GUI: Spikesorting of Neuropixels Sample Data Fails Jul 24, 2019
@AGenews
Copy link
Author

AGenews commented Jul 24, 2019

Dear Nick,
thank' lot for the quick reply! Indeed I had to install the "statistics & machine learning" toolbox for the eMouse simulation, and running Kilosort2 with the master_kilosort.m works nicely now.
However, the GUI still fails in part, but now with a different error:
Error saving data for phy! Reference to non-existent field 'Wphy'.

Yours sincerely and many thanks,
Andreas

@KBillel
Copy link

KBillel commented Jul 24, 2019

Hi I think it's because you need to have the folder npy-matlab-master in your path. You can find it here : https://github.com/kwikteam/npy-matlab

@xintangg
Copy link

xintangg commented Sep 7, 2019

Hi

Have you solved this problem?

@AGenews
Copy link
Author

AGenews commented Sep 9, 2019

Hi there ...
well I had all the respective software packages installed all along, so I figured I simply use the matlab script which works nicely. But with the GUI it didn't work and I haven't tried since then.
Best,
A.

@marius10p
Copy link
Contributor

My guess is that 2016b does not support z-score on the GPU, which the GUI uses but not the main code. You could write a little z-score function of your own and replace it in the code? I'd be happy to check any pull requests on this.

@jvschweim
Copy link

Dear Nick,
thank' lot for the quick reply! Indeed I had to install the "statistics & machine learning" toolbox for the eMouse simulation, and running Kilosort2 with the master_kilosort.m works nicely now.
However, the GUI still fails in part, but now with a different error:
> Error saving data for phy! Reference to non-existent field 'Wphy'.
Yours sincerely and many thanks,
Andreas

On that issue, I sometimes get the same error message when I run kilosort2 on several files after each other. Clearing the .phy folder usually helps to get around the issue.

@erc84
Copy link

erc84 commented Oct 30, 2019

I'm also receiving the same error when using the GUI. I've made sure to add the npy-matlab-master folder to the path, have all the toolboxes otherwise properly installed, and I at least don't see any .phy folder in the kilosort directory to clear or modify. I'm also running R2019a. Any other suggestions?

@nsteinme
Copy link
Collaborator

nsteinme commented Nov 1, 2019 via email

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.

7 participants