Open tsalo opened 3 weeks ago
@mattcieslak what should QSIRecon do in the following scenarios? Which ones are already covered, or are impossible to reach?
The two key pieces of anatomical data that qsirecon uses are
Here's what currently happens:
- No T1w or T2w
If will try to load in a T1w from the --freesurfer-input and will register that to the dwi reference. If there's nothing, then it makes any workflows that require an anatomical image raise an error.
- T1w only in native anatomical space
The resampled T1w in template space isn't used for anything in qsirecon.
- T2w only in native anatomical space
I think it results in an error because t1w is hardcoded into the ingress interfaces.
T1w only in MNI space I've never seen this happen, but this would result in the same behavior as if there is no t1w space anat.
T2w only in MNI space
Same as ^
- T1w and T2w in same native anatomical space
Ignores T2w and uses T1w in everything
- T1w and T2w in different anatomical spaces
As long as there is a space-T1w T1w image and a pair of transforms to MNI, things will function normally
- T1w and T2w in same MNI space
Both will be ignored.
Regarding the T2w-related scenarios, what should happen (esp. with HBCD data)? The main one is when T1w and T2w are both present. Should QSIRecon default to using the T2w as the main anatomical modality when both are present? I assume that should depend on if infant
mode is enabled. E.g., T1w as primary for adults, T2w as primary for infants. WDYT?
_Originally posted by @mattcieslak in https://github.com/PennLINC/qsirecon/pull/49#discussion_r1717183969_