-
Notifications
You must be signed in to change notification settings - Fork 429
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
Tissue prior output volumes in random order #3213
Comments
From what I understand it should not be random, given the innate intensity difference between CSF, GM and WM. Do you have some images of how it is random? For example does CSF and GM change classes with each other sometimes? |
I see. I still think it is ordered intensity wise, but it is giving unstable results. You can see that on subject 100610 GM and CSF share labels, which is why WM got label 1 and there is almost nothing for label 2. I am not sure what happened on 102816, but it seems to be a similar problem of GM and CSF being mixed up. This seems to be a limit of the method itself, which hopefully we will be able to address later on. |
This would not be a problem with analyses using just a few subjects because one can manually identify the tissue maps. It becomes a real problem with batch processing. For example, I need to run the same algorithm through 100+ subjects and it won't be practical to check each individual. In the latter case, I don't think changing the number of classes would guarantee the consistency across subjects. |
I agree. It was just a workaround I found when dealing with few subjects. We could definitely benefit from a more robust/less tweaking required tissue segmentation. But maybe others have an easier solution for now. |
Yeah, I have a temporary solution using the aparc+aseg files provided by HCP to match the tissue masks. But general users would benefit more from something independent of additional check files. |
I think when we say 3 it is actually 4. 3 + background. |
The mean intensity for each class should be different and easy to sort. |
@Garyfallidis The current order is not random. It appears random because CSF and GM had some issues separating but as you can see from the images WM is always a higher class. |
Okay, indeed the error seems different. Good catch @pjsjongsung |
I see, now that makes sense. It's a tissue separation issue, not order issue. Nonetheless the issue seems prominent. I checked the 176 HCP 7T subjects, only about 80 had correct tissue classification like the second subject above. The rest of the subjects mostly had GM + CSF mixing like 100610, but 20+ subjects had WM + CSF mixing as well: ACT breaks down with either type of mixing. |
Great feedback. Please send us a couple of the data that fail. |
Sure, I'm using the HCP 7T data on UITS' storage /N/project/hcp_dcwan. Here are some problematic subjects:
|
Description
I generated tissue maps from some pre-computed Q-ball peaks:
The third output in
results
is the PVE volume which contains the 3 identified classes. They follow a random order when I compared the volumes from different subjects using the same script. Is there a way to make the volumes follow a fixed order? Here is what MRTrix used:https://mrtrix.readthedocs.io/en/dev/quantitative_structural_connectivity/act.html
The text was updated successfully, but these errors were encountered: