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

Check for Secondary Capture spacing following DICOM Part 3 Sect A.8.1.3 #170

Merged
merged 1 commit into from
Apr 29, 2024

Conversation

thewtex
Copy link
Contributor

@thewtex thewtex commented Apr 11, 2024

Following the Secondary Capture Image IOD Module Note:

If Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037) (from the Image Plane Module) are present, then the values of Pixel Spacing (0028,0030) (from the Image Plane Module and the Basic Pixel Spacing Calibration Macro included from the SC Image Module) are intended to be used for 3D spatial computations, rather than any values of Nominal Scanned Pixel Spacing (0018,2010) (from the SC Image Module), which may also be present.

However, we make sure to throw a warning in ImageHelper::GetSpacingTagFromMediaStorage when the tag for a Secondary Capture MediaStorage is requested and SecondaryCaptureImagePlaneModule is enabled because returning a single tag is insufficient for this requirement. This function should not be called on this type of media storage.

Following the Secondary Capture Image IOD Module Note:

> If Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037) (from the Image Plane Module) are present, then the values of Pixel Spacing (0028,0030) (from the Image Plane Module and the Basic Pixel Spacing Calibration Macro included from the SC Image Module) are intended to be used for 3D spatial computations, rather than any values of Nominal Scanned Pixel Spacing (0018,2010) (from the SC Image Module), which may also be present.

However, we make sure to throw a warning in `ImageHelper::GetSpacingTagFromMediaStorage` when the tag for a Secondary Capture MediaStorage is requested and SecondaryCaptureImagePlaneModule is enabled because returning a single tag is insufficient for this requirement. This function should not be called on this type of media storage.

Co-authored-by: Mihail Isakov <[email protected]>
Co-authored-by: Mathieu Malaterre <[email protected]>
Co-authored-by: Steve Pieper <[email protected]>
thewtex added a commit to thewtex/ITK that referenced this pull request Apr 11, 2024
…A.8.1.3

Following the Secondary Capture Image IOD Module Note:

> If Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037) (from the Image Plane M  odule) are present, then the values of Pixel Spacing (0028,0030) (from the Image Plane Module and the Basic Pixel   Spacing Calibration Macro included from the SC Image Module) are intended to be used for 3D spatial computations  , rather than any values of Nominal Scanned Pixel Spacing (0018,2010) (from the SC Image Module), which may also   be present.

However, we make sure to throw a warning in `ImageHelper::GetSpacingTagFromMediaStorage` when the tag for a S  econdary Capture MediaStorage is requested and SecondaryCaptureImagePlaneModule is enabled because returning a si  ngle tag is insufficient for this requirement. This function should not be called on this type of media storage.

Pushed upstream here: malaterre/GDCM#170

Co-authored-by: Mihail Isakov <[email protected]>
Co-authored-by: Mathieu Malaterre <[email protected]>
Co-authored-by: Steve Pieper <[email protected]>
hjmjohnson pushed a commit to InsightSoftwareConsortium/ITK that referenced this pull request Apr 12, 2024
…A.8.1.3

Following the Secondary Capture Image IOD Module Note:

> If Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037) (from the Image Plane M  odule) are present, then the values of Pixel Spacing (0028,0030) (from the Image Plane Module and the Basic Pixel   Spacing Calibration Macro included from the SC Image Module) are intended to be used for 3D spatial computations  , rather than any values of Nominal Scanned Pixel Spacing (0018,2010) (from the SC Image Module), which may also   be present.

However, we make sure to throw a warning in `ImageHelper::GetSpacingTagFromMediaStorage` when the tag for a S  econdary Capture MediaStorage is requested and SecondaryCaptureImagePlaneModule is enabled because returning a si  ngle tag is insufficient for this requirement. This function should not be called on this type of media storage.

Pushed upstream here: malaterre/GDCM#170

Co-authored-by: Mihail Isakov <[email protected]>
Co-authored-by: Mathieu Malaterre <[email protected]>
Co-authored-by: Steve Pieper <[email protected]>
@malaterre
Copy link
Owner

@thewtex I missed that note in my earliest attempt, I'll try to review the previous attempt to see if it still make sense to preserve it. thanks

@thewtex
Copy link
Contributor Author

thewtex commented Apr 24, 2024

@malaterre thank you!

@malaterre malaterre merged commit 2664155 into malaterre:release Apr 29, 2024
3 checks passed
@malaterre
Copy link
Owner

Fixed in the end with 836f7a7 hopefully with test added I did not make any regression this time.

cc: @seanm

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 this pull request may close these issues.

2 participants