-
Notifications
You must be signed in to change notification settings - Fork 70
[WIP] Update tutorial to use BIDSDataGrabber #131
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
Conversation
Oops, looks like some of my changes didn't save, so wait for those |
No problem. And don't worry about the circleci errors. The building of the docker image is currently broken but should be fixed quickly. |
Okay, there we go. I had a weird issue with user permissions in |
Thank you @adelavega! Sorry for bothering you with this. But for easier reviewing reasons, could you commit the notebook with empty output cells? Such an approach also keeps the overall repo size small. |
I also rewrote history to get rid of that data in the repo. |
Did that work? I cleared outputs but now I don't see the "hide" button for Examples. |
That looks good. The "hide" button is not visible on github, but is still contained in the actual notebook. |
hey @miykael , I refined the notebook a bit, and I think it's ready for your review/merge. The upstream updates to I think I'll be adding metadata support, and smarter iterables for |
Small correction of the notebook metadata to keep it the same as the other notebooks.
Hey @adelavega - thanks for the updates! This looks all fine to me and can be merged. The circleci errors are taken care of on An metadata support and smarter iterables for BIDSDataGrabber would be awesome! 👍 |
Sounds good! Go for it. |
Above, you mention the |
Yes, basically what happened is that although pybids use the term We're waiting until this weeks BIDS-Model meeting at Stanford (and more testing to think about merging. We are hoping this is the least time we break the API ... at least in a while :) |
Hehe :-) That sounds good. Will merge this for now, and once pybids 0.7 comes out we can update this notebook again. |
I've gone through and updated
basic_data_input_bids
to use niype'sBIDSDataGrabber
interface. Check it out and let me know if it makes sense to you.There are a few more changes to make (not all of which may make into this PR)
BIDSDataGrabber
I may want to highlight. E.g. the defaults are quite usefunc (func
&anat
by default), and more complex queries are possible.modality
is no longer a supported entity. It was a mistake to include it and according toBIDS
spec its actuallydatatype
BIDSDataGrabber
(for same reason as above, and to support derivatives, and new pybids syntax in 0.7)Also, you're example of loading meta-data makes it obvious it would be quite useful if an interface made that easier (rather than having to wrap in a
Function
)