We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
MRSpectroscopyStorage
These shouldn't be scanned for Pixel Data, as they don't have any!
We should probably amend this:
https://github.com/SMI/IsIdentifiable/blob/main/IsIdentifiable/Runners/DicomFileRunner.cs#L235
Using the information fo-dicom provides on the SOPClassUID here:
SOPClassUID
https://github.com/fo-dicom/fo-dicom/blob/development/FO-DICOM.Core/DicomUID.cs#L31-L43
The text was updated successfully, but these errors were encountered:
Maybe just check for the PixelData tag being present?
If IsIdentifiable can also scan overlays then check for any of the 16 OverlayData tags being present?
Sorry, something went wrong.
Fair point 😉 I guess the question is whether we want to detect invalid files based on whether the SOPClass specifies pixel data should be present?
Not sure on the overlay handling - will check this.
rkm
Successfully merging a pull request may close this issue.
These shouldn't be scanned for Pixel Data, as they don't have any!
We should probably amend this:
https://github.com/SMI/IsIdentifiable/blob/main/IsIdentifiable/Runners/DicomFileRunner.cs#L235
Using the information fo-dicom provides on the
SOPClassUID
here:https://github.com/fo-dicom/fo-dicom/blob/development/FO-DICOM.Core/DicomUID.cs#L31-L43
The text was updated successfully, but these errors were encountered: