-
Notifications
You must be signed in to change notification settings - Fork 1
Improve registration of AMU WM/GM mask and PAM50 template #41
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
base: master
Are you sure you want to change the base?
Conversation
Various new options, notably: - mode: average vs. flip - specify output dtype
Using thresholding, and output as UINT16 type (like for PAM50_t2) Fixes #44
Easier to insert Python code
Implemented an approach that uses adjacent slice registration for better performance.
Will create another PR specific to the update of the PAM50_cord file
It was unecessary, and created an indentation that limits clarity
Agree. When looking in the axial plane, it looks like the T2* image is still a bit dilated toward the anterior (top) direction. One or two pixels (+ bean shape for T2 versus circular shape for T2*) |
@vcallot That might stem from the pipeline used to generate the AMU15. Ideally, the AMU15 and PAM50 should follow a similar pipeline. One workaround, would be to regenerate the AMU15, which means I would need access to the original data and code that was used to generate the AMU15 template. This would also help address one of my concern regarding the validity of the probabilistic values of the AMU15. Depending on the type of registration parameters that was used to generate the AMU15, it is possible that part of the reason the original AMU15 GM mask looks so "smooth" (with, overall, lower probability values than the current PAM50 GM mask), is that the inter-subject registration was imperfect, leading to this increased smoothness. |
Following a discussion with the Marseille group, we decided to update the PAM50 template to fix some of the issues reported in #32.
Fixes #32 #40