Open Lestropie opened 1 year ago
Note that by implementing the necessary functionality in MRtrix3's dwicat
, and then utilising that script here to deal with voxel grid differences, #64 will be closed.
Dealing with fmap/
images may be a little trickier than first anticipated.
A susceptibility field map can only be used reliably by eddy
if the first volume of the input to topup
is the same as the first volume of the input to eddy
. There is some existing trickery within dwifslpreproc
to deal with this; for instance, inserting the first DWI b=0 volume into the SE-EPI series to pass to eddy
, and resampling the series provided via -se_epi
to the DWI voxel grid if necessary. However the changes to dwicat
potentially make this even more complex. Because we're no longer just dealing with voxel grid differences: dwicat
may have actually moved the image content in space, particularly in the avoidance of interpolation to concatenate data from multiple series with different header transforms.
So I think maybe what needs to be done is:
fmap/
image:
fmap/
image to concatenated DWIsfmap/
imagesfmap/
image:
fmap/
imagesFor step 3.i.a., I think that it should be the transformed images that get resampled and not the originals:
dwicat
there's a certain presumption of centredness of the head within each individual image FoV, such that aligning the FoVs makes sense rather than assuming that the head has remained centred in scanner space and the FoVs mismatch erroneously.fmap/
images to be perfectly axis-aligned.
Need to be able to support data for which execution otherwise fails with this error.
mrtransform -replace
; if not, thenmrtransform -template
will be necessary Ensure that gradient directions are rotated accordingly Ensure that phase encoding directions remain faithfulfmap/
images onto the same image grid (there are already cases where this can occur, but if step 4 above is invoked then this is guaranteed to be necessary)