Steven Meisler

I could be wrong, but I think that is because LPS is the standard FSL orientation, and FSL is used for the later stages of processing (EDDY, TOPUP, etc).

Got it, thanks! I’ll start with a modified iFOD2 on the TOMs and see how that works.

Hi @earoy and @mattcieslak, I encountered this same error on some older dataset while using version 0.19.1. Matt I will reach out to you to share the data. Edit: Error...

``` Node: sub_reader403_wf (template_iterator_wf (select_xfm (utility) ================================================================== Hierarchy : fmriprep_23_2_wf.sub_reader403_wf.template_iterator_wf.select_xfm Exec ID : select_xfm.a0 Original Inputs --------------- * anat2std_xfm : ['/om2/scratch/tmp/oozernov/READER_fitlins/sub-reader403/data/derivatives/fmriprep/sub-reader403/anat/sub-reader403_run-1_from-T1w_to-MNIPediatricAsym_mode-image_xfm.h5', '/om2/scratch/tmp/oozernov/READER_fitlins/sub-reader403/data/derivatives/fmriprep/sub-reader403/anat/sub-reader403_run-1_from-T1w_to-MNI152NLin2009cAsym_mode-image_xfm.h5', '/om2/scratch/tmp/oozernov/READER_fitlins/sub-reader403/data/derivatives/fmriprep/sub-reader403/anat/sub-reader403_run-1_from-T1w_to-MNI152NLin6Asym_mode-image_xfm.h5'] * key : MNIPediatricAsym:cohort-4 * keys :...

I can give it a shot. I shouldn't have trouble setting up a dev environment (changes will be happening in https://github.com/smeisler/smriprep/tree/fix/cohort_res) but will update here if I run into issues.

Actually before I do too much, I should make sure the dev environment was set up correctly. Steps I took: 1. Fork the repo `smeisler/smriprep` 2. Start a new branch...

Haven't had much time to work on this yet, hope to get to it tomorrow.

Hmm, does this persist in 0.17.0? I have not encountered this error, and the `scale` argument seems to be valid according to the SVGUtils documentation (https://svgutils.readthedocs.io/en/latest/_modules/svgutils/transform.html#FigureElement.moveto).

I think as long as the QSIPrep outputs work with the QSIRecon workflows, there is no need to introduce a change. Have you run into any issues in this respect...

Of note, it is being integrated in DIPY 0.17.0 release, should make integration easier.