-
Notifications
You must be signed in to change notification settings - Fork 4
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
Select SpikeGLX test data #852
Comments
The error suggests that you put the directory
instead of
The directory that you put should not exist. Could you share a screencast of selecting the above folder? |
Wait a second - the SpikeGLX Recording interface asks for a File Path, not a Folder. Are you sure you selected "SpikeGLX Recording" not "SpikeGLX Converter"? |
It's a common mistake in the current tutorial; careful followers will choose the 'SpikeGLX Recording' (single-stream) for the single file path, but it is not the first item that pops up when you search 'SpikeGLX' We've discussed it previously since it was seen in user testing, but I've added it to the list on #846 so it's on the record An improvement might just be to have a separate tab for 'advanced' interfaces, which this one might qualify as since the 'SpikeGLX Converter' This could remove ambiguity for various formats that have multiple interfaces |
Describe the issue
When selecting
~/NWB_GUIDE/test-data/single_session_data/spikeglx/Session1_g0/Session1_g0_imec0
from the test data, as indicated in the tutorial https://nwb-guide.readthedocs.io/en/v1.0.0/tutorials/single_session.html#source-data-information, I get the following error:If I select the parent folder ``~/NWB_GUIDE/test-data/single_session_data/spikeglx/Session1_g0` instead GUIDE is able to continue. Maybe this is just something that should be updated in the docs?
Steps to Reproduce
~/NWB_GUIDE/test-data/single_session_data/spikeglx/Session1_g0/Session1_g0_imec0
Operating System
MacSO
GUIDE Version
1.0
Code of Conduct
Yes
Did you confirm this issue was not already reported?
Yes
The text was updated successfully, but these errors were encountered: