-
Notifications
You must be signed in to change notification settings - Fork 0
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
Undefined appearance of the spinal cord in the generated template #17
Comments
ALWAYS tell us in the GH issue what your plan is BEFORE moving forward with analysis (eg: i don’t agree with removing one subject– it does not make sense)-- also, i do NOT agree that one dog shows the ‘dark circle’. Also. These images only show one axial slice– this is not a thorough overview. I think that all dogs should be considered for this template. In some cases, we do see a dark ring, but I don't think this will be a problem when generating the average template (it will average out). A more important think that needs to be done, is to investigate how each individual dog’s spinal cord look across the template generation pipeline (eg: after 5 iterations: how does it look like? is there a dog where the registration is completely ‘off’, which would explain the weird appearance in the final template?). If that's the case, then what needs to be done to fix it is to provide manual segmentation for individual dogs during template generation process. |
Referred to the (a) MNI-AMU-Poly template paper, (b) PAM50 paper, (c) Unbiased average age-appropriate atlases for pediatric studies (in which the template generation pipeline we are using was introduced) to understand the effect of parameters. I drew inspiration from the above manuscripts to change parameters mentioned in this part of the template generation pipeline. Below are the trials:
The dark circle around the spinal cord still exists.
Link to outputs from trials: https://drive.google.com/file/d/1dPfYtxXxMrg66cA0yxVGhww8C68zBP98/view?usp=share_link |
|
As per #16, the spinal cord is defined on the template as being much smaller than the area that seems to coincide with the CSF boundary:
I suspect this is a glitch that was produced when non-linearly registering and then averaging several dog images.
To rule in/out this hypotheses, this issue looks at individual dog images around this lumbar region.
The text was updated successfully, but these errors were encountered: