You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BIDS allows to specify SliceEncodingDirection. How about adding a parameter to afni.TShift to use this information and SliceTiming from BIDS sidecar files directly.
BIDS allows to declare SliceEncodingDirection to specify the direction of SliceTiming. What do you think about adding a SliceEncodingDirection input ({k, k-}) to afni.TShift. If this is k-, reverse the slice timing list before running the correction.
Does it make sense to also add i, j, i-, j-? Or does it make sense to always assume that slices have been acquired along the third axis?
What do you think?
The text was updated successfully, but these errors were encountered:
fliem
changed the title
adding SliceEncodingDirection to afni.TShift
adding SliceEncodingDirection to afni.TShift
Oct 25, 2018
Summary
BIDS allows to specify
SliceEncodingDirection
. How about adding a parameter toafni.TShift
to use this information andSliceTiming
from BIDS sidecar files directly.This comes via fmriprep. @effigies suggested to add this here.
BIDS allows to declare
SliceEncodingDirection
to specify the direction ofSliceTiming
. What do you think about adding aSliceEncodingDirection
input ({k, k-}
) toafni.TShift
. If this isk-
, reverse the slice timing list before running the correction.Does it make sense to also add
i, j, i-, j-
? Or does it make sense to always assume that slices have been acquired along the third axis?What do you think?
The text was updated successfully, but these errors were encountered: