Fix order of pixel spacing converting ITK->DICOM. #486
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The order in which the values for pixel spacing in ITK and DICOM are stored is different. In DICOM the first value is the row spacing (i.e. Y axis) while in ITK the first value is spacing along the X axis. Reading asymmetric spacings from DICOM segmentations has already been fixed in 46c6f0. This commit fixes writing DICOM segmentation objects with asymmetric spacings.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The order in which the values for pixel spacing in ITK and DICOM are stored is different. In DICOM the first value is the row spacing (i.e. Y axis) while in ITK the first value is spacing along the X axis.
Reading asymmetric spacings from DICOM segmentations has already been fixed in 46c6f0.
This commit fixes writing DICOM segmentation objects with asymmetric spacings.