Operating system: Win 10 Pro x64
Slicer version: 4.10.2
Some segmentation file resolutions are different with originial mri image resolutions.
ex1) mri - (150, 512, 512) / seg - (44, 101, 101)
This seems to happen to the most of the segmentation files with multiple segmentations.
I created multiple nodes for each tumor and merged them into one node. Was this the cause for it?
Is there any way to fit seg’s res to mri’s? and if the above method causes problems, how do i make a segmentation file with multiple segmentations?
Thank you in advance.
The segmentation’s resolution matches the master volume’s resolution but the extent is cropped to the minimum necessary by default (the origin is adjusted accordingly, so the segment’s physical position remains correct). You can export the segmentation to labelmap volume before saving it if you prefer saving the blank parts of the segmentation (so that extents are exactly the same as the master volume’s).
We see that many users are surprised by this behavior, so we will change it to not crop to minimum extent by default (see Segmentation image size).
Thank you for explanation.
Then is it impossible to fit the resolution of segmentation which was saved already to that of mri image in this situation?
It is not just possible but very easy to do. In Segmentations module Export/import section, choose your MRI image as reference volume before clicking Export button:
I appreciate your help.
I solved this with your answer.