We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Both SpikeGLX and Open Ephys - Neuropix-PXI can optionally save a 385th SYNC channel in the binary file.
While both IOs have a load_sync_channel option, all cases are not currently handled. In particular:
load_sync_channel
load_sync_channel=False
load_sync_channel=True
Expected behaviour SpikeGLX and OpenEphys correctly handle the SYNC option of NP probes in a similar way, handling all possible cases.
Additional context Currently on GIN we only have:
We need to gather:
The text was updated successfully, but these errors were encountered:
I do not think @DradeAW is the correct candidate for this because he is writting the thesis manuscript!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
Both SpikeGLX and Open Ephys - Neuropix-PXI can optionally save a 385th SYNC channel in the binary file.
While both IOs have a
load_sync_channel
option, all cases are not currently handled. In particular:load_sync_channel=False
(see here).load_sync_channel=True
, but not present in the data (same for SpikeGLX)Expected behaviour
SpikeGLX and OpenEphys correctly handle the SYNC option of NP probes in a similar way, handling all possible cases.
Additional context
Currently on GIN we only have:
We need to gather:
The text was updated successfully, but these errors were encountered: