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

Issues on images with BitsAllocated (0028,0100) set to 16 and BitsStored (0028,0101) set to 8 #94

Closed
jmcoelloidonia opened this issue Jul 18, 2019 · 3 comments

Comments

@jmcoelloidonia
Copy link

Describe the bug
We've found a DICOM modality that somehow creates images with BitsAllocated (0028,0100) set to 16 but BitsStored (0028,0101) set to 8 and this doesn't seem to be rendering properly on weasis.

To Reproduce
Steps to reproduce the behavior:

  1. Load a dcm with (0028,0100) set to 16 and BitsStored (0028,0101) set to 8

Expected behavior
It should render correctly, as shown in attachment.

Desktop (please complete the following information):

  • OS: Both Linux and Windows, 64-bits
  • Java Runtime: OpenJDK Runtime Environment (build 1.8.0_212-8u212-b03-0ubuntu1.19.04.2-b03)
  • Weasis Version: 3.5.2-SNAPSHOT (portable)

Screenshots
470ac4e2-a261-11e9-9099-7aee65d9ab48_0_HD
470ac4e2-a261-11e9-9099-7aee65d9ab48

@nroduit
Copy link
Owner

nroduit commented Jul 19, 2019

I never have a file with this configuration that seems a little absurd to me because we double the size with useless information!

Could you send me a sample?

@jmcoelloidonia
Copy link
Author

Yes, no problem.

470ac4e2-a261-11e9-9099-7aee65d9ab48.dcm.zip

@nroduit
Copy link
Owner

nroduit commented Jul 19, 2019

This special case was not taken into account because the reader step was the bitstored rounded to the upper byte.
Fixed for 3.5.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants