|Message: problem reading DICOM files||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
I am using the DICOM example to read several different DICOM files. Apart from the examples included with the code and another CT that I tried, all other DICOM CT images I tried to read seem to have some problem with the DicomHandler.
For some reason it seems that the info is not read correctly (reading wrong, or at wrong positions from the binary?) and several errors occur. For example, when it creates the g4dcm files, the first few material lines that come directly from Data.dat are of course ok, but later on there is some wrong info. Usually it starts by reading wrong coordinates/image size.
So, while it finds the rows and columns correct and the X dimension also correct, Y and Z dimension are wrong (even 0) and sometimes densities are also negative ( "@@@ Error density = -1 ..."). I have checked those images with external viewers and they are definitely OK. Looking a bit at the DicomHandler itself in the case of 0 Y dimension:
343 fPixelSpacingX = atof( datas.substr(0,iss).c_str() );
344 fPixelSpacingY = atof( datas.substr(iss+2,datas.length()).c_str() );
fPixelSpacingX is ok while datas.substr(iss+2,datas.length()).c_str() is an empty string and fPixelSpacingY is 0. And I suspect that similar problems occur later on in the process. Then the image is a single line in the XY plane, unless I edit Y myself in the g4dcm file and it is able to create a 3D geometry (although is has some negative densities).
I would be grateful if someone can help me with what is going on with the binary (dcm) reading, as it is not really my strong point in C++.
I can also send the corresponding dcm files so that the same problems could be reproduced.
Thanks in advance,
|Inline Depth:||Outline Depth:||Add message:|