Hi,
We have a python preprocessing script, which calls on eddy. We wanted to save the eddy_movement_rms file, and have used fsl/5.0.11
Although the format of the file is correct (2 columns * 'n' rows), the values are nearly identical. I've pasted an example of the output file, which has been executed on a dti sequence of 31 volumes.
0 0
0.2600684803 0.2600684803
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
0.2600684803 0
This cannot be correct, as I ran this on raw unprocessed data. Can someone help me troubleshoot this problem? I can provide more information as needed.
It should be noted that this isn't the first time we've used eddy. It performs as expected on the actual NIFTI file, but the way it is writing the movement_rms values seems incorrect.
########################################################################
To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1
|