You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i'm using neuropixels 1.0 probes with SpikeGLX.
the .bin files are 385 channels (384+1 sync channel).
how does kilosort2 deal with that?
it knows there are 385 not 384 channels in the data. should i make a custom channel config file with 385 channels and disable the last channel?
if so what variables should i include in the file to disconnect the last channel?
The text was updated successfully, but these errors were encountered:
This is taken care of because the channel map file only specifies that
1:384 are part of the probe. As long as the total number of channels is
correctly specified as 385, then the data will be read correctly.
On Sun, May 26, 2019 at 6:03 AM WeissShahaf ***@***.***> wrote:
i'm using neuropixels 1.0 probes with SpikeGLX.
the .bin files are 385 channels (384+1 sync channel).
how does kilosort2 deal with that?
it knows there are 385 not 384 channels in the data. should i make a
custom channel config file with 385 channels and disable the last channel?
if so what variables should i include in the file to disconnect the last
channel?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#71>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABZ5IP5QQ7N6BQLQBQAQWYTPXKDCFANCNFSM4HPWUCTA>
.
i'm using neuropixels 1.0 probes with SpikeGLX.
the .bin files are 385 channels (384+1 sync channel).
how does kilosort2 deal with that?
it knows there are 385 not 384 channels in the data. should i make a custom channel config file with 385 channels and disable the last channel?
if so what variables should i include in the file to disconnect the last channel?
The text was updated successfully, but these errors were encountered: