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

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Load a 3D +t DICOM dataset with debugging enabled -> shows the correct 
length of Pixel Data
2. 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 reported on code.google.com by tho...@stehle.cc on 10 Sep 2012 at 9:51

[GoogleCodeExporter]

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

Original comment by tho...@stehle.cc on 10 Sep 2012 at 11:01

[GoogleCodeExporter]

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?

Original comment by Suever@gmail.com on 10 Sep 2012 at 1:17

[GoogleCodeExporter]

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.

Original comment by tho...@stehle.cc on 10 Sep 2012 at 2:25

[GoogleCodeExporter]

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

Original comment by tho...@stehle.cc on 30 Oct 2013 at 3:31

[GoogleCodeExporter]

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

Original comment by darcymason@gmail.com on 31 Oct 2013 at 12:01

• Changed state: Invalid