-
Notifications
You must be signed in to change notification settings - Fork 73
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
Track specific bundles #38
Comments
So far there is no option to only track a specific bundle. You could adapt line 132 in |
Thanks! |
Sorry, but I am completely new to this, so I have another question! How would you edit the |
The file is here |
Just wanted to point out a potential bug - I ran TractSeg on a VMware CentOS 7 system with all the pre-requisites installed. Tractseg gave an error:
`
The dimensions of dwi.mif and mask.mif are different which might be causing the problem. I commented out lines 87, 88, 95-99 in dwi2response, essentially forcing Mrtrix to generate its own mask.mif and that has solved the error. However, due to memory errors, I wasn't able to run the complete TractSeg command and track specific bundles according to your suggestion above. On to that now! |
I was not able to reproduce this problem. When running on ubuntu 16.04 and using mrtrix 3.0 RC3 and fsl build 509 it works fine. |
I don't know if it has got anything to do with the fact that I'm running TractSeg on a virtual machine - it is the VMWare CentOS 7 installation that comes with FSL download; and with Mrtrix 3.0 RC3 as well. |
This works; I can now track just the corpus callosum. I also wanted to ask if there is a way to do something similar for the TractSeg command - while creating the endings_segmentations, bundle_segmentations etc.. Is there a way to segment just the corpus callosum? I have been looking at the code but couldn't figure it out. This is just to save time if possible since I plan to do some batch processing on a lot of images. |
|
Ok, thanks! |
Hi,
Just wondering if there is a way that I can use TractSeg to track only specific bundles, e.g. only the corpus callosum. I am studying the corpus callosum and it seems unnecessary to have to wait till the code has tracked all fibre bundles, to analyse just one tract.
Thanks,
Surya
The text was updated successfully, but these errors were encountered: