-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
T2w-ACPC image not being output #676
Comments
Ah! I forgot to add a datasink to the T2w. Thanks for opening a bug report. Also, have you taken a look at the html report using the TOPUP+DRBUDDI? If you have "rpe_series" data then you'll see a new FA-alignment figure in there. |
I don't see the new FA-alignment figure in the HTML unfortunately - happy to share any data that may help |
And you're sure it's multiple dwi series in multiple phase encoding directions? The report only comes out in v0.20.0. The section header (I realize now it's not very descriptive) should be Susceptibility distortion correctionResults of performing susceptibility distortion correction (SDC) on Fractional Anisotropy (FA) images. |
It's one DWI series and a RPE fmap. |
ahh ok then the FA SDC part won't run and there won't be a report. The T2w should still get sent to the derivatives directory though. do you see much movement in the DRBUDDI html report? |
Very interesting. I haven't tried TOPUP+DRBUDDI with just an epi fmap before. It looks reasonable offhand, but it will be interesting to see how downstream things are affected. |
I have a BIDS-valid dataset with T1 and T2 images. The
qsiprep
boilerplate suggests thatHowever, I do not see any T2 images in my output directory:
QSIPrep completed without errors:
singularity run -e -B ${scratch},${cache_dir} ${qsiprep_img} $scratch/data $scratch/data/derivatives participant --participant_label ${subject:4} -w $scratch --fs-license-file ${scratch}/data/code/license.txt --denoise-method patch2self --pepolar-method TOPUP+DRBUDDI --unringing_method mrdegibbs --recon-spec $scratch/data/code/recon_spec.json --output-resolution 1.25 --freesurfer-input ${scratch}/data/derivatives/freesurfer/ --fs-license-file $scratch/license.txt --skip-odf-reports --notrack --mem-mb $mem_mb --nthreads 16 --omp-nthreads 8
I've noticed this with 0.19.0 and 0.20.0
Thanks for your attention,
Steven
The text was updated successfully, but these errors were encountered: