flywheel/curate-bids
Flywheel Gear that curates files within a Flywheel project according to BIDS Spec
1.5K
Flywheel Gear that curates files within a Flywheel project according to BIDS Spec
Before running BIDS curation on your data, you must first prepare your data with the following steps:
No inputs need to be set for this gear. By default, it will step through the entire project and look at all subjects and sessions. If the "entire_project" configuration parameter (see below) is un-checked, it will only step through the current session.
Run bids curation on the entire project. If this is not checked, curation will take place on only the currently selected subject. Default (when decked) is to run on entire project.
Remove all BIDS info from files before curating. Default is unchecked, to not reset the curation.
Warning: if you have manually selected any container or file to be ignored by checking the "bids ignore" flag in the BIDS info, this will remove that also, so you will need to do that again if it is important to you. As an alternative to using that ignore flag, you can add "_ignore_BIDS" to the end of an acquisition container's name, and it will be ignored even if it is re-curated with the reset flag checked. This behavior is only for the Default template and for acquisitions. Similar behavior can be had by using a custom template.
Which template type to use. Options: Default, ReproIn, or Custom. Note: Custom expects a BIDS Project Curation JSON Template as a project-level file with the filename ending in project-template.json.
This defaults to INFO but set it to DEBUG to see exactly what is happening to help with figuring out BIDS curation.
The "outputs" of this gear are metadata written to the "BIDS" namespace in all container's and file's Custom Information. See the BIDS Introduction for more information.
docker pull flywheel/curate-bids