Open jbwexler opened 1 year ago
Same error for every subject in ds000120-fmriprep and ds000203-fmriprep
Need to check for TRT/EES, not just phase-encoding direction to fail.
@mgxd @oesteban When TRT/EES are missing for SyN-SDC, should we just not do it, or fall back to per-BOLD SyN-SDC?
I think we should not do it because there's no certainty that all BOLDs will have the same TRT/EES. If the researcher knows the value, it should be encoded with the dataset. Sharing data without TRT should be flagged (in a way, it is similar to sharing data without TR).
In that case, should I just run those subjects without --use-syn-sdc
?
Yes, but I agree that is inconvenient. fMRIPrep should disable fieldmap estimation and make a lot of noise about the missing SDC step (alternatively, have a flag to be more lenient and instead of crashing completely, issue the warning).
We have --use-syn-sdc error
(default) and --use-syn-sdc warn
. My initial thought was to just expand our early checks (which only look for PE direction) to fail/warn if TRT/EES is also missing.
The point, though, is that this isn't really required metadata, it's just useful for binning multiple BOLD series together to save computation and get a less biased fieldmap estimate. In the absence of the binning information, we could fall back to the pre-21.0 behavior of creating a separate fieldmap estimate per BOLD series.
This happened for majority of subjects: