-
Notifications
You must be signed in to change notification settings - Fork 6
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
If the output clustering results are in the atlas space? #1
Comments
Hi! glad to see the code works for you and the results look good in Slicer! For your questions:
Please let me know how it works. Regards, |
Thank you for your patient answer! Based on your guidance, I have transformed the clusters back to the diffusion space successfully using "wm_harden_transform.py". It helps a lot. For 2, I realized the orientation issue with your reminder. Probably I don't need to transform orientation in my case. If any questions, I will give you feedback. Best, |
I knew the subject-specific tractography data is transformed into the atlas space and then perform clustering. So I wonder if the output clustering results are in the atlas space?
If so. How can we transform it back into subject-specific space for further analysis?
We use SupWMA on HCP 7T data and merge all 198 clusters into one file. The result looks good in 3DSlicer 👍👍 but then we transform vtp file to tck file and loaded in MRview. The tractogram is not aligned with the subject-specific b0_mean.
If the 'Tractograpy Display' modules in 3dslicer would coregister tractogram with image automatically? However, they are not actually in the same space?
Thank you!
The text was updated successfully, but these errors were encountered: