search

suever / pydicom-experimental

pydicom test
0 stars 1 forks source link

Length of pixel data array wrong in 3D + t data sets #117

Closed suever closed 9 years ago

suever commented 9 years ago

From tho...@stehle.cc on September 10, 2012 05:51:17

What steps will reproduce the problem? 1. Load a 3D +t DICOM dataset with debugging enabled -> shows the correct length of Pixel Data

  1. print all dicom tags to screen -> wrong output 3. What is the expected output? What do you see instead? There is a discrepancy of 1154 or 1156 or 1138 or 1136 bytes (only in very few cases it fits). This does not allow me to reshape the image data according to the image dimensions as it complains that the size of data must not change during reshape. What version of the product are you using? 0.9.7 _NOTE_: any text or attached files posted with the issue can be viewed by anyone. You are solely responsible to ensure that they contain no confidential information of any kind. Please provide any additional information below. An examplary data set can be provided on request.

Original issue: http://code.google.com/p/pydicom/issues/detail?id=117

suever commented 9 years ago

From tho...@stehle.cc on September 10, 2012 04:01:02

The discrepancy seems to occur during conversion of raw_data_elements to Dataset in read_dataset(...) -> Dataset(raw_data_elements)

suever commented 9 years ago

From Suever@gmail.com on September 10, 2012 06:17:33

Could you attach your example 3D+t DICOM file (be sure to anonymize it first)?

Are you accessing the PixelData through Dataset.pixel_array or are you accessing Dataset.PixelData directly?

suever commented 9 years ago

From tho...@stehle.cc on September 10, 2012 07:25:55

I've got the impression that my data somehow (probably during a transfer from a FTP server) became corrupted somehow. An analysis tool tells me that the file length and size of pixel data is inconsistent. I'll first check whether this is the case.

I'll let you know whether this is the problem.

suever commented 9 years ago

From tho...@stehle.cc on October 30, 2013 08:31:29

It was indeed a problem with the DICOM file, so this issue can be closed.

suever commented 9 years ago

From darcymason@gmail.com on October 31, 2013 05:01:45

It was indeed a problem with the DICOM file, so this issue can be closed.

Status: Invalid