Taylor Salo

QSIRecon now has a parameter to control where reports go: `--report-output-level {root,subject,session}`. We're planning to implement it in QSIPrep and XCP-D as well.

@feilong I think this is a natural place to follow up on https://github.com/nipreps/fmriprep/issues/3330#issuecomment-2247075427. Just so I understand, there seem to be three issues here: 1. TemplateFlow's file naming doesn't distinguish...

1. Okay that makes sense. Does the `space` entity indicate the same thing? E.g., `tpl-fsLR_space-fsaverage_sphere.surf.gii`? If so, is that sufficient to distinguish registration from resampling spheres? 2. I guess the...

Sorry, I think I was a little mixed up. My current understanding is that templateflow contains (or should contain) three types of sphere: 1. Transform/registration sphere, where the vertices correspond...

Wow, I was _way_ off! Apologies everyone. @Shotgunosine, does @feilong's answer match your understanding?

Should the updated Schaefer atlases be added to templateflow as new atlases, or should the old ones in templateflow just be replaced with the new ones?

Yikes, sorry about that! I will dig into this today.

The individual workflows show up in my local HTML build, but not here. I need to figure out why.

It might be easier to just merge this as-is and revisit the workflow graphs and Docker/Apptainer interfaces in a future PR. @mattcieslak do you mind if I merge this?