-
Notifications
You must be signed in to change notification settings - Fork 15
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
Some subjects have different image and label dimensions and resolution #144
Comments
Yup! This is exactly it. Thank you for catching that @valosekj 🙏 Not sure what is the best course of action from there... I guess it depends how these manual labels are used. |
Right, it really depends on the processing steps which are run. I noticed this because I was using "raw" T2w images without applying the resampling. If resampling is applied, everything is fine. Perhaps we could add the following paragraph to the README.md file (as we did for canproco) to inform future users: ## Derivatives
Note: T1w and T2w images were preprocessed prior to spinal cord segmentation and disc labeling.
Namely, reorientation to RPI and resampling to 1mm (T1w) and 0.8mm (T2w) isotropic voxel size was performed.
Therefore, for some subjects, the original T1w and T2w images have different dimensions than the segmentation and disc labeling.
Applied preprocessing steps for T1w image:
https:/spine-generic/spine-generic/blob/master/process_data.sh#L146-L157
Applied preprocessing steps for T2w image:
https:/spine-generic/spine-generic/blob/master/process_data.sh#L175-L183 |
Some subjects have different image and label dimensions and resolution.
For example, for subject
sub-beijingGE02
, T2w image has differentdim
andpixdim
than T2w spinal cord segmentation:This discrepancy probably originates from processing, where
T2w
image was resampled and then segmented:In other words, data-multi-subject contains the original non-resampled T2w image but SC seg obtained from resampled T2w image.
So far, I noticed this for
sub-beijingGE
andsub-brnoUhb
subjects.The text was updated successfully, but these errors were encountered: