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
Looking into this now - one question: is the docker wrapper meant to provide a very high level fmriprep call, while the fmriprep callable allows more fine-grain control? Or have we just not been synchronizing the two?
The Docker wrapper is meant to turn something that looks like an fMRIPrep invocation into a docker command. Any option that's valid in fMRIPrep should be valid in fMRIPrep docker. But it passes most things through, uninspected, only parsing options that will require it to mount a volume or some other manipulation of Docker.
We've been keeping some deprecated command-line arguments for some time - it is now the moment to drop them. These are:
--ignore-aroma-denoising-errors
--debug
--output-space
--template
--template-resampling-grid
--no-freesurfer
--output-grid-reference
(this is only present on the wrapper).The text was updated successfully, but these errors were encountered: