-
Notifications
You must be signed in to change notification settings - Fork 97
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
NrrdToFSL: DWIConvert vs ConvertBetweenFileFormats #342
Comments
ConvertBetweenFileFormats attempts to maintain the input images direction cosines as closely as possible. DWIConvert tries to match the FSL standards. Due to the fact that the BVEC and BVAL information is implicitly in an LAS corrdinate system (and the fact that the measurement frame is implicitly an identity matrix), we needed to re-organize some data sets to ensure that a consistent representation from the DWI data was maintained. |
Great, thanks. |
@hjmjohnson I'd like to re-open this to discuss the current behavior for FSL Nifti -> NRRD
For (1):
For (2): |
In addition to the links provided by @ihnorton, I would suggest this link. Fortunately, DWI data is is virtually always acquired axially, but if you do encounter coronal or sagittal acquisitions, I would be very cautious of hard coding the LAS reorientation, as Eddy assumes that slices are the 3rd dimension and altering this will impact options like |
Description
Given an LPS DWI nrrd, DWIConvert makes an LAS nifti, and given a single diffusion volume of that nrrd, ConvertBetweenFileFormats makes an LPS nifti. This has consequences when converting back to nrrd, namely the
j
inijk
space is flipped in the first case, but remains unchanged and matches the original in the latter case. (The world coordinates are fine and correct).Issue
Here's an example of where this affected me:
Usually I mask a nrrd using
unu 3op ifelse
but that does so in ijk space, so 1 does not work, but 2 is fine.So my questions are:
Reproduce
git clone https://github.com/pnlbwh/BRAINSTools-debug
cd BRAINSTools-debug && make
The text was updated successfully, but these errors were encountered: