At present, due to naming convention that distortion correction pairs are numbers 1,..,n, with no leading 0, when creating SEtargets*.nii.gz files, we're aligning the incorrect run for each pair. The input to afni_proc.py is interpreted as blip_for10, blip_for1, blip_for2, ..., due to UNIX filename sorting.
A possible fix (untested yet) is to add leading 0 for blip pairs when 10 or more. If this works, I'll drop the issue. Otherwise, more adjustment needed (procedurally generate blip pair list for afni_proc call for SEtargets distortion correction)
At present, due to naming convention that distortion correction pairs are numbers 1,..,n, with no leading 0, when creating SEtargets*.nii.gz files, we're aligning the incorrect run for each pair. The input to afni_proc.py is interpreted as blip_for10, blip_for1, blip_for2, ..., due to UNIX filename sorting.
A possible fix (untested yet) is to add leading 0 for blip pairs when 10 or more. If this works, I'll drop the issue. Otherwise, more adjustment needed (procedurally generate blip pair list for afni_proc call for SEtargets distortion correction)