-
Notifications
You must be signed in to change notification settings - Fork 124
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
Arbitrary directories indexed in version 0.7.0 #364
Comments
Yes, you're breaking BIDS. Per the spec, derivatives have to go either under That said, it would be a good idea to have the ability to exclude arbitrary directories/files from indexing (and I'll come back to this at some point once the 0.8 refactoring is done). One way you can do that at the moment is to drop a config file (I believe it's named |
Noted - thanks! |
oh, @AdinaWagner , look above at the hidden treasure disclosed by Tal which could be of help ;-) |
already drafting one of these and looking forward to get rid of our hardcode-hacking ;-) |
Keep in mind this hidden treasure will be going away fairly soon... |
This is now supported in 0.8 via the |
Hey team,
I'm using the new
0.7.0
release and encountered an "undocumented feature" that's been a bit annoying for me. First of all, thanks for the descriptive release notes - it was really easy to transition from0.6.5
->0.7.0
just going through the list.What I'm experiencing is that I have arbitrary directories in my dataset, such as "
derivatives_old
" and "derivatives_phacked_save_for_later
", etc., and whilederivatives
isn't being indexed automatically, and then some files in sub-directories there are being identified erroneously as my raw data file.I can't seem to find a way to cleanly exclude these from being indexed. Am I just breaking bids and should put these all inside the
derivatives
folder?The text was updated successfully, but these errors were encountered: