Skip to content
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

Re-introduce padding in transformation #88

Closed
PaulBautin opened this issue Oct 25, 2020 · 2 comments · Fixed by #89
Closed

Re-introduce padding in transformation #88

PaulBautin opened this issue Oct 25, 2020 · 2 comments · Fixed by #89

Comments

@PaulBautin
Copy link
Collaborator

Images with missing CSA reported in issue #86 all present segmentations that do not cover all vertebrae levels from C3 to C5. This issue only appeared once padding was removed. Therefore, my guess is that segmentation is not performed when cord approaches the image boundaries. I do not think this issue is causing outliers presented in issue #83, because as mentioned in issue #86 removing subjects with missing CSA mostly removes subjects with high COV and low error.

@jcohenadad, What do yout think of re-integrate padding to see if it resolves this issue?

example:
Cropped and transformed image:
sub-barcelona04_T1w_RPI_r_crop_r0.98_t1.zip
segmentation of ^ image
sub-barcelona04_T1w_RPI_r_crop_r0.98_t1_seg.zip

@jcohenadad
Copy link
Member

I would definitely not reintroduce padding, because the problem here is not padding, but extreme transformation:
image

We can clearly see here that the spinal cord is cropped, causing a wrong estimation of the CSA, and wrongly contributing to a higher intra-subject COV. Adding padding will not solve this issue, it will only "hide" it.

So, I would instead reconsider this hard-coded number "15", and increase it to something safer, like 30:

sct_maths -i ${file_seg}.nii.gz -dilate 15 -shape cube -o ${file_seg}_dil.nii.gz

@jcohenadad
Copy link
Member

Illustration of the problem:
image

Suggestion of a solution:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants