5ttgen gif fractions don't sum to 1


#1

Hi everyone,

I ran 5ttgen with gif option. I had the same issue as Amir. As you suggested I investigated the voxels where the tissue fraction don’t sum up to 1 (figure bellow)

. In black are the voxels that don’t sum to 1 and in white the voxels that sum to 1.
It seems the grey matter tissue is where the problem occurs. I tried using fsl and T1 images but I got the same problem. And help?
Thank you.

Hassna


5ttgen stuck at first-L_accu_first.vtk
#2

OK, there’s a lot of different concepts / issues getting blurred together in this thread… In general, if your issue is not described well by the title of an existing thread, it’s best to create a new thread, and simply include a link to the other thread in your post in case if it has some relevance.

The issue of non-unity partial volume sums described earlier above is caused by some hard-to-reproduce issue in the FSL command fast, which then propagates through to the 5ttgen fsl script. There was also an issue with an earlier version of the 5ttgen fsl script that caused the same warning to be issued, but with a much greater number of voxels; that was an issue with my own code that has since been fixed. The fact that you are using the 5ttgen gif algorithm means that neither of those are applicable: this is something else, which, given how lightweight the 5ttgen gif script is, may be something to do with the GIF software rather than 5ttgen gif. I would suggest looking closely at the raw output from that software, and contacting the developers if you believe there to be some issue. Alternatively, if you can better isolate the root cause of the issue (e.g. maybe some fraction of those voxels is being assigned to some other tissue class that the 5ttgen gif algorithm is ignoring? Maybe it’s just a floating-point tolerance issue?), then that’s something we can chase up here.

The fact that you receive a similar warning using the 5ttgen fsl script is probably not some intrinsic deficiency or curse in your image data, but just luck that you happen to be receiving the same error that is occurring for a different reason. However if you’re using an up-to-date MRtrix3 installation, I would expect the number of non-unity voxels with the 5ttgen fsl algorithm to be significantly less than that of the image you have provided.

Rob


#3

Hi @hassna,

I split your post into its own topic, as Rob suggested. This will help others better discover it, so they can assist you or learn from the experiences and answers in the following thread.

Cheers,
Thijs