-
Notifications
You must be signed in to change notification settings - Fork 74
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
Clinical tumor data #23
Comments
Did you try the steps described here: https://github.com/MIC-DKFZ/TractSeg#small-bundles-like-the-ca-and-fx-are-incomplete ? Those tend to make the segmentations more complete. |
Did you rigidly move the images to MNI space? |
Yes, I used |
Great that it works now! |
Ok, great, thanks again.. |
When you talk about |
Yes, with the flipped peaks It must be related to the FA image somehow? I updated all segmentations with the newly flipped peaks. |
Do all of your images (the bundle segmentations, the tract orientation maps, brain mask and the FA) have the same spacing and dimensions? |
The segmentations,toms and mask do have the same dimensions, but not the FA images.
|
It seems like you used the FA_MNI.nii.gz image which is generated by TractSeg when using the option |
Great, that works fine now, thanks! |
If you look into the folder |
Hi, |
You can see all the changes for each version in the CHANGELOG.md file (https://github.com/MIC-DKFZ/TractSeg/blob/master/CHANGELOG.md). There is one change to the preprocessing in v1.7.1. Peaks are not automatically flipped anymore. You should see a warning message if TractSeg thinks the peaks need to be flipped. You have to flip them manually then. Does that solve your problem? |
Thanks for the changelog hint. However, after feeding various data - manually flipped and non-flipped, it seems to fail to provide non interrupted tract segmentations. |
Hi, we now downgraded to version 1.6. After we flip the peaks it works perfectly fine for our clinical data with version 1.6. |
I did not experience such problems. It is hard to tell what might be the problem. If you send me the data of one subject where it works in 1.6 but fails in 1.7.1 I can have a look if I can reproduce the problem. |
ok thanks, we've sent it via wetransfer |
I had a look at the data. It is a bit tricky because it only works if you move it to MNI space (which you should always do) and flip it along the z dimension. TractSeg tells you to flip it along the x axis, but that is wrong. If there is a tumor in the brain TractSeg is getting it wrong quite often unfortunately. So you have to look at it manually in mrview (Tools->fixel plot) or MITK Diffusion to determine how you have to flip them so that it aligns properly with the Diffusion image. If you are not sure you can try all three options: Flip along x, y and z and see which one gives proper results.
|
Ok thank you very much! We used as well |
Hi, I'm testing with a clinical data set of a tumor patient. I noticed that when feeding a preprocessed and upscaled
Diffusion.nii.gz
file and it'sbvecs/bvals
, the results are slightly better (afterdwidenoise
,mrdegibbs
,dwipreproc
,dwibiascorrect
(ants),mrresize
(1.25 voxel size) in the respective order).Still, the
bundle_segmentation
files are partly empty or incomplete but not necessarily at the tumor location where one would assume interruption or difficulties.Manually, fibers are traceable at the interrupted areas.
Can you provide a hint?
(I'll continue testing on different tumor patients.)
Best, Lucius
The text was updated successfully, but these errors were encountered: