Open JehandadKhan opened 5 years ago
They are valid and correct. As you can see that from the metadata.
Or you can load these files in any DICOM viewer, i.e., RadiAnt (https://www.radiantviewer.com/).
Ok, I will investigate it further On Mon, Feb 18, 2019 at 3:12 PM Ghulam Rasool notifications@github.com wrote:
They are valid and correct. As you can see that from the metadata.
Or you can load these files in any DICOM viewer, i.e., RadiAnt ( https://www.radiantviewer.com/).
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/grasool/Load_ct_data/issues/1#issuecomment-464880821, or mute the thread https://github.com/notifications/unsubscribe-auth/AFXcuXpNmGEvVQSPB4T7OKmzZS7MDeWsks5vOxdPgaJpZM4bBd7r .
Not a big fan of windows ....
The issue is in pillow
while the transfer syntax for the Not_Working
images should be supported by pillow
it errors out while trying to read the image. Our best bet right now is to either use GDCM
to read these images or open an issue on pillow
's github repo
GDCM
?
Its an alternative to Pillow as a backend for reading images. On Sat, Feb 23, 2019 at 3:01 PM Ghulam Rasool notifications@github.com wrote:
GDCM?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/grasool/Load_ct_data/issues/1#issuecomment-466694539, or mute the thread https://github.com/notifications/unsubscribe-auth/AFXcuTj5IT3K3VwUQScRa6G6rRQFfifCks5vQaw6gaJpZM4bBd7r .
@grasool can you confirm if the files in
Not_Working
are valid and correct. From the error it looks like either the file is corrupt or has a feature that thepyDICOM
library does not support.