Unfold sMRIPrep as a separate pipeline? #3615
Description
What would you like to see added in fMRIPrep?
In the next TechMon, I'd like to discuss the merits of fully embracing a YODA approach and separate sMRIPrep from fMRIPrep (down the line, we could think similarly about SDCFlows, btw).
This would disallow some parallelization of sMRIPrep nodes and fMRIPrep nodes by moving the frontier between the two, but it would establish a way simpler interface for fMRIPrep, right? That quickly propagates to other tools because then, e.g. PETPrep, could have specific FreeSurfer requirements while remaining compatible with the standard sMRIPrep stack.
I assume that for infants we have a similar benefit: rather than implementing the workflows, calling an external tool that drops the derivatives in its own sourcedata/ folder could be of great interest.
WDYT?
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
No response