-
Notifications
You must be signed in to change notification settings - Fork 111
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
BUG (?) - scans.tsv backslash path #1408
BUG (?) - scans.tsv backslash path #1408
Comments
related: bids-standard/bids-specification#867 which was brought up here: bids-standard/bids-specification#820 (comment) If I understood it correctly, Windows can actually deal with both It's relatively straight forward for tools to make this easy for users, so we just need to make this clearer everywhere (and find consensus, if this is actually controversial) |
Okay, that's actually great news, and pretty much answers my question. |
Buuut, I am not entirely sure about this comment of mine:
Maybe some Windows users can chime in? @VisLab for example? Or you can test it on your machine? |
So, since I am pretty inexperienced with this kind of stuff, I am not sure if I need to test this in a specific piece of code, but the following cases work:
|
Dear all,
I write my BIDS datasets with FieldTrip's data2bids function.
This function writes out filenames in scans.tsv with a backslash, e.g.:
The bids validator gives the following error:
I don't know enough about path styles and back and forward slashes, but my feeling is that file path separators are system-dependent, bids-validator should work in both cases and optimally convert the slash to the system-specific separator when checking if the file actually exists.
I am not sure if this makes sense or is even possible, but I am happy to hear your opinions and I am happy to contribute to the code if necessary :)
Thanks in advance!
The text was updated successfully, but these errors were encountered: