Taylor Salo

I think this was more for me than any actual users, so I'm going to close.

@LuciMoore any update on this?

Thanks @Lestropie and @jelleveraart! > Do you want to make a feature request? Sure! I'll open an issue requesting a variance explained output map. >1. I found the denoising under...

That makes sense.

>IMO, the output spaces syntax is already quite complicated, so I'm a bit hesitant to add another special value (auto). For what it's worth, QSIPrep and QSIRecon need the ability...

>"MNIInfant:cohort-auto" will only be added if no MNIInfant output spaces are present - if a user is explicitly requesting 1 (or more), I assumed they looked up the bucket information...

What about throwing in other CIFTI extensions? dscalar, ptseries, pconn, etc.

Would this apply to workflow names and variables as well? E.g., `fmriprep.registration.init_bold_t1_trans_wf()` --> `fmriprep.registration.init_bold_individual_trans_wf()`. EDIT: I assume we wouldn't use the `scanner` term in the code, since `scanner` can refer...

I'd like to revisit this given that, in Nibabies, the primary anatomical modality may be T1w or T2w, so a general space label would be helpful for post-processing pipelines like...

That sounds great. It seems like this could end up being distinct from T1w or T2w (at least for the secondary anatomical contrast). For example, with fMRIPrep, where T1w is...