Closed ajschadler12 closed 1 year ago
Hello, thank you for the observation, could you please provide us with the command that would not apply the rescaling or the bvalues? or are you referring to the BZeroThreshold
used in the processing? because indeed the default BZeroThreshold is set to 61 but this behaviour could be customize. thank you
Hi, yes, you will need to append -bvalue_scaling no
to mrconvert
when initially converting from nifti to mif.
E.g.
mrconvert -bvalue_scaling no -fslgrad sub-abcd_ses-01_dir-AP_dwi.bvec sub-abcd_ses-01_dir-AP_dwi.bval sub-abcd_ses-01_dir-AP_dwi.nii.gz sub-abcd_ses-01_dir-AP_dwi.mif
In case you were curious, Dr. Tournier left an in-depth comment on why bvalue scaling might fail in some settings, particularly our data.
Thank you for the observation, we added this feature on the latest v0.1.5 version of the pipeline this week. We are still building a new docker container updated.
The docker was successfully built and this option is include in the versions v0.1.5
and v0.2.0
What is the current behaviour?
Micapipe uses default behavior of mrconvert, which includes bvalue scaling.
What is the motivation / use case for changing the behaviour?
For ABCD multishell RSI sequences, bvalue-scaling leads to incorrect DTI estimation. Allowing for an option to not scale bvalues in mrconvert would make the DTI pipeline much more flexible.