You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Otherwise, the validity test can take a very long time (if the BIDS dataset has hundreds of subjects or more)
If it's not supported downstream in the BIDS validator, maybe can make a temporary BIDS directory consisting of only the desired subjects using symbolic links, and run the BIDS validator there.
The text was updated successfully, but these errors were encountered:
The latter suggestion would be quite the hack, given the concern would be equally applicable to all BIDS Apps. There is surely a neater way of doing this; and if there isn't, it's probably worth escalating up the chain.
I'm not very familiar with the validator, but looking at their latest README, I see a couple of options:
Following parsing of the desired participant / subject labels, auto-generate a config file that excludes all data outside of the user's selection for processing, and pass that to the validator when invoking.
Over time, hopefully the Python capabilities will extend beyond just checking compatibility of file extensions to running validation on subsets of a dataset.
Otherwise, the validity test can take a very long time (if the BIDS dataset has hundreds of subjects or more)
If it's not supported downstream in the BIDS validator, maybe can make a temporary BIDS directory consisting of only the desired subjects using symbolic links, and run the BIDS validator there.
The text was updated successfully, but these errors were encountered: