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

Input data contains NaN and Inf Error #96

Closed
sandraromerop opened this issue Aug 5, 2019 · 2 comments · Fixed by #595
Closed

Input data contains NaN and Inf Error #96

sandraromerop opened this issue Aug 5, 2019 · 2 comments · Fixed by #595

Comments

@sandraromerop
Copy link

Hi all

I'm trying to set up Kilosort2 , using datasets from Neuralynx

My device is : using GeForce GTX 1060 , Matlab 2019a, Windows 10
testCSCFile.zip
64 bit, and Microsoft Visual C++ 2017.

Until now I've come to this point:

  • I've managed to run the e-Mouse data drift sample data/code and it went through.
  • I loaded the data from .CSC files from Neuralynx to matlab-- writing them as int16 (I sort of played with the read/write functions, see code below as don't know if it's accurate)
  • When loading the dataset to the gui I see the traces and the spikes look ok by eye.
  • Preprocessing went through ok

Now the error comes when I run the spike sorting :

  • During the spike sorting I get some warnings : 'Warning: data batch Positive crossing detection #33 only had 12 spikes' and then I get the error 'Error running Kilosort! Input matrix contains NaN or Inf '

Do you if that's caused by the input data format or by the sparsity in the spikes of the recording? or neither. ?

I attached the channel ap files and the code I'm using to write the int16 format .dat file

thanks!!!!!
testCSCFile.zip

@marius10p
Copy link
Contributor

Can you please check your data in the Matlab GUI? Does it look like it was loaded correctly (i.e. the channels are contiguous and in the right order). Kilosort2 only sees the "filtered" version of the data which you can see in the GUI by pressing 2.

@marius10p
Copy link
Contributor

Issue has become inactive. Closing.

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