-
Notifications
You must be signed in to change notification settings - Fork 222
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 loading data #121
Comments
What is the correct number of channels in the file? The guess of 33
channels is just based on some heuristics but it seems that it was wrong in
this case - you just want to put the correct number into the box and you
should be fine.
I didn't understand what you mean went wrong with your custom channel map,
if you can explain that more I could try to advise.
…On Wed, Sep 25, 2019 at 10:21 PM MarkDTu ***@***.***> wrote:
Hi
I am having a real issue trying to load data from the buzsaki a64 probes
[image: buzsakichannel]
<https://user-images.githubusercontent.com/35493169/65603239-32ffdf80-df9d-11e9-836e-b0673c2f8bbd.JPG>
I have recorded the data into individual continuous .dat(x64) files at
25000hz and resample before saving into the .bin format at 5000hz for data
size (3 hour long recordings)
If I load the .bin file into kilosort2 using the default 16x1 linear
mapping I can see traces for the 16 channels and it presumes there are 33
channels
[image: kilosortimg]
<https://user-images.githubusercontent.com/35493169/65604571-9f7bde00-df9f-11e9-8330-1a70c579a1b3.JPG>
I have created a channel map for the 64 channel probe but it does not
recognise the data
[image: buzsakikilo]
<https://user-images.githubusercontent.com/35493169/65604525-883cf080-df9f-11e9-99d7-fb846c797e71.JPG>
I can preprocess the data through the linear 16x1,it starts to spikesort
the batches before a 'kilosort cuda error invalid configuration' occurs. I
am guessing this is due to the presumed 33 channels instead of the actual
64.
Interestingly I can load the an individual .dat file that is only for one
of the 64 channels and it allows it to load the data, but obviously the raw
file is a mess as it is only one channel.
[image: kilosort64]
<https://user-images.githubusercontent.com/35493169/65604435-68a5c800-df9f-11e9-9734-c7c559b5c797.JPG>
I am using an 8650u processor and 1050 gpu, which has been working fine
with other data sets.
Any help would be much appreciated
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#121>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABZ5IPYL5R4F7UDH6ZEVO4DQLNQW3ANCNFSM4I2MXPHA>
.
|
You have to fill in all the parameters, I am not sure why you are not getting the defaults there. Be advised that you won't be able to sort anything at 5000Hz. Stick with the 25kHz sampling rate. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
I am having a real issue trying to load data from the buzsaki a64 probes
I have recorded the data into individual continuous .dat(x64) files at 25000hz and resample before saving into the .bin format at 5000hz for data size (3 hour long recordings)
If I load the .bin file into kilosort2 using the default 16x1 linear mapping I can see traces for the 16 channels and it presumes there are 33 channels
I have created a channel map for the 64 channel probe but it does not recognise the data
I can preprocess the data through the linear 16x1,it starts to spikesort the batches before a 'kilosort cuda error invalid configuration' occurs. I am guessing this is due to the presumed 33 channels instead of the actual 64.
Interestingly I can load the an individual .dat file that is only for one of the 64 channels and it allows it to load the data, but obviously the raw file is a mess as it is only one channel.
I am using an i5-8500 processor and 1050 gpu, which has been working fine with other data sets.
Any help would be much appreciated
The text was updated successfully, but these errors were encountered: