[Insight-users] Warning message by using ApplicationModel, cont'

[Luis Ibanez]

Hi Jiang,

Information for creating the image is collected
directly from the headers of your DICOM files.

It seems to me that the real problem is arising
from your data. Your images doesn't seem to be
compliant and henceforth there is few that you
can ask from any software for displaying the
images correctly.

I would suggest you to contact the your image
provider and get some feedback on the mechanism
they used for generating your images. It is
quite possible that they will be able to provide
you with more consistent data.

The fact that MRIConvert refuses to load your
images is a clear indication that there is room
for improvement in your DICOM encoding.


You can keep trying to use the Hammer... but
it seems that what you got there is not a Nail.



Regards,



    Luis,



--------------------
jiang wrote:
> Hi Luis,
> I try to use VolView to load the same test images as I used in
> ApplicationModel. I got the same result as ApplicationModel with
> itk::DICOMImageIO2. VolView gives a message that the distance between two
> images is 6.5. It is why the 3d object looks so "fat". But VolView has no
> warning message "No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution."
> 
> Best regards,
> 
> Chunyan Jiang
> 
> -----Ursprungliche Nachricht-----
> Von: jiang [mailto:jiang at ti . uni-trier . de]
> Gesendet: Dienstag, 7. Oktober 2003 14:01
> An: Luis Ibanez
> Cc: ITK
> Betreff: Warning message by using ApplicationModel
> 
> 
> Hi Luis,
> I tried both itk::DICOMImageIO2 and itk::DicomImageIO. I got different
> result.
> 1. Both of them have waring message "No DICOM magic number found, but file
> appears to be DICOM. Proceeding without caution." Application with
> itk::DicomImageIO has 9 warning messages. While application with
> itk::DICOMImageIO2 has more than 30 warning messages. There are 9 images in
> the test folder.
> 2. I use both versions read same series of DICOM images. But the results are
> not same in coronalView and saggitalView. When the application with
> itk::DICOMImageIO2 runs, in the coronalView and saggitalView, the image is
> very "thin". Since there are 9 images in the folder, in the coronalView and
> saggitalView, the thickness of image is almost same as 9*unit. It appears
> that the object is compressed. When the application with itk::DicomImageIO
> runs, in the coronalView and saggitalView, the image is very "fat". It seems
> that the object is enlarged.
> I don't know how ApplicationModel handles the thickness of the image and the
> distance between two images to build 3D image. It seems that results of the
> two versions both are incorrect.
> 
> Best regards,
> Chunyan
> 
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk . org
> http://www . itk . org/mailman/listinfo/insight-users
>