Greetings DSI studio team
I'm Javier Arcos Hódar, a research assistant based on the Alberto Sols Institute for Biomedical Research on Madrid. I've been tasked to investigate other software for MRI data processing in case we end up having problems with our homemade Matlab software. First of all I'd like to be thankful for the developing of DSI Studio, since it seems to work faster and provide many options ours doesn't. Unfortunately I might be mismanaging something since even for the very simple task I wanted to start with (exporting AD, MD and FA values) it's giving me some problems. I attached to the dropbox the relevant files, from both DSIstudio (src, fib and exported maps) the raw Bruker data and the results from our software.
The files from our alternative software are not a .nii stack but can be opened on imageJ under Import -> Raw -> DTI_FA_Raw, with settings (I think those are the default but please double check to avoid problems) -image type 64-bit Real -Width and Height 128 pixels, -offset of first image 0, -number of images 1, -gap between images 0 bytes, and -only little-endian byte order ticked on, with the three other settings on blank.
I think it is evident (both from checking with my group and the literature, see for example
Li XY et al (2017) https://www.sciencedirect.com/science/article/pii/S1995764517304492) that the high FA values in the .nii file DSI Studio creates cannot be correct, with the typical in slice 1 close to 0.60 in some areas (0.17 for contralateral region with no tumour and 0.31 for tumour are the values cited in the literature, our own are similarly in that range, mostly in the .20s for non-tumour areas) but it might be just that I'm misusing DSI Studio in some way rather than a problem with the software itself. My settings for reconstruction are T2b(1) DTI, T2b(2) check b-table and tensor matrix marked on while helix angle and scheme balance are marked off. While the b table and directions are correctly read from the 2seq file of the raw Bruker data it should be noted that when setting up the mask in the src file I also edit ->image flip X and image flip Y to fix the orientation in the final .nii export, but this shouldn't matter when it's just applying the FA formula pixel per pixel.
Initially I thought the MD values could be quite closer to reality but on the wrong unit (multiplying the values associated with each voxel by 1000 in R gave me values with a near-unity correlation with the processing of our other sofware, if always somewhat lower, our software gives MD values for each voxel in μm^2/s) and that could even be the source of the error (as in FA values would be correct if I could somehow change DSI studio's processing to also multiply all MD valuse by 1000) but now I'm beginning to doubt even that.
While attached is an example I could provide data from other subjects if necessary to narrow down the issue.
Thanks in advance