AW: [Insight-users] No DICOM magic number found, but file appears to be DICOM.

Luis Ibanez luis . ibanez at kitware . com
Fri, 26 Sep 2003 16:44:22 -0400


Hi Thimmaiah,

Thanks for sending the DICOM files that are producing
read errors.

I put them in a single directory and they work fine
for reading. The slices can be read individually with
the ImageViewer application, and the three together
can be read as a volume using the DICOMImageSeriesReader.


It looks like you have in the same directory other
files that are not DICOM slices.  The DICOMImageSeries
reader may be attempting to read *ALL* the files in
the directory and having trouble with the ones that
are not real DICOM slices.


Please verify that the directory *only* contains DICOM
files.



  Thanks


   Luis


---------------------------
Thimmaiah, Sandhya wrote:
> Hi Luis,
> I don't have any ftp to post but I am sending 3 zipped Dicom files. When I
> run itkDICOMImageSeriesTest with these files I get the following message.
> Hope you can help us out.Also I wanted to know how I can get the patients
> data(name, age.....). Thank you
> 
> C:\ITK\BDICOMSeries\Release>itkDICOMImageSeriesTest.exe DICOM3 0
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> DICOMSeriesFileNames (00224788)
>   RTTI typeinfo:   class itk::DICOMSeriesFileNames
>   Reference Count: 2
>   Modified Time: 4
>   Debug: Off
>   Observers:
>     none
>   Directory: DICOM3
>   File name sorting order: SortByImagePositionPatient
>   FileNames[0]: DICOM3/1.3.12.2.1107.5.2.4.7399.20030828092545000003026
>   FileNames[1]: DICOM3/1.3.12.2.1107.5.2.4.7399.20030828092545000003025
>   FileNames[2]: DICOM3/1.3.12.2.1107.5.2.4.7399.20030828092545000003024
> 
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> No DICOM magic number found, but file appears to be DICOM.
> Proceeding without caution.
> Image (002274B0)
>   RTTI typeinfo:   class itk::Image<unsigned short,3>
>   Reference Count: 1
>   Modified Time: 67
>   Debug: Off
>   Observers:
>     none
>   Source: (00225520)
>   Source output index: 0
>   Release Data: Off
>   Data Released: False
>   Global Release Data: Off
>   PipelineMTime: 16
>   UpdateTime: 155
>   LastRequestedRegionWasOutsideOfTheBufferedRegion: 1
>   LargestPossibleRegion:
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [256, 256, 3]
>   BufferedRegion:
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [256, 256, 3]
>   RequestedRegion:
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [256, 256, 3]
>   Origin: [-135.445, -138.381, -2.3]
>   Spacing: [1.07422, 1.07422, 2]
>   PixelContainer: ImportImageContainer (002275A0)
>   RTTI typeinfo:   class itk::ImportImageContainer<unsigned long,unsigned
> short>
> 
>   Reference Count: 2
>   Modified Time: 68
>   Debug: Off
>   Observers:
>     none
>   Pointer: 002275D0
>   Container manages memory: true
>   Size: 196608
>   Capacity: 196608
> 
> -----Original Message-----
> From: Luis Ibanez [mailto:luis . ibanez at kitware . com]
> Sent: Thursday, September 25, 2003 12:02 PM
> To: jiang
> Cc: Thimmaiah, Sandhya; ITK
> Subject: Re: AW: [Insight-users] Create 3D image data by a series of 2D
> dicom files
> 
> 
> 
> 
> Thimmaiah, Jiang,
> 
> Could any one of you post somewhere one of the DICOM
> slices that is giving you trouble for reading ?
> (it could be in an FTP site or in a Web page...)
> 
> That will give us a chance to try reading it and figure
> out what is special about these images.
> 
> The DICOM implementation in ITK is not suppossed to be
> bullet proof, it is just covering a reasonable large
> set of DICOM files.
> 
> Did anyone of you tried to read this files with MRIConvert ?
> 
> 
> Thanks
> 
> 
>    Luis
> 
> 
> 
> ------------------------
> jiang wrote:
> 
>>Hi, Thimmaiah,
>>I also saw your message. It is a pity that I didn't yet solve this
> 
> problem.
> 
>>I am waiting for someone might answer your question. It is also helpful
> 
> for
> 
>>me.
>>
>>Good luch!
>>
>>
>>
>>-----Ursprüngliche Nachricht-----
>>Von: Thimmaiah, Sandhya [mailto:sthimmaiah at neurosurgery . wayne . edu]
>>Gesendet: Mittwoch, 24. September 2003 22:46
>>An: 'jiang'
>>Betreff: RE: [Insight-users] Create 3D image data by a series of 2D
>>dicom files
>>
>>
>>Hi Jiang,
>>I saw that you have got same messages as I am getting now....
>>No DICOM magic number found, but file appears to be DICOM.
>>Proceeding without caution.
>>I wanted to know if you were able to fix it. I would really appreciate if
>>you can reply me. Thank you
>>
>>-----Original Message-----
>>From: jiang [mailto:jiang at TI . Uni-Trier . DE]
>>Sent: Friday, September 19, 2003 12:19 PM
>>To: Lorensen, William E (Research)
>>Cc: ITK
>>Subject: AW: [Insight-users] Create 3D image data by a series of 2D
>>dicom files
>>
>>
>>Hi, Bill,
>>I tried your code to read the data that I sent you. However, it always
>>doesn't work. The message printed out are:
>>No DICOM magic number found, but file appears to be DICOM.
>>Proceeding without caution.
>>No DICOM magic number found, but file appears to be DICOM.
>>Proceeding without caution.
>>No DICOM magic number found, but file appears to be DICOM.
>>Proceeding without caution.
>>......
>>DICOMSeriesFileNames (010B2270)
>>  RTTI typeinfo:   class itk::DICOMSeriesFileNames
>>  Reference Count: 2
>>  Modified Time: 4
>>  Debug: Off
>>  Observers:
>>    none
>>  Directory: C:\jcy\Qt\TestApp\DICOMSeries\Series
>>  File name sorting order: SortByImagePositionPatient
>>  FileNames[0]:
>>C:\jcy\Qt\TestApp\DICOMSeries\Series/1.3.12.2.1107.5.2.1.5603.20
>>030731093845884002024
>>  FileNames[1]:
>>C:\jcy\Qt\TestApp\DICOMSeries\Series/1.3.12.2.1107.5.2.1.5603.20
>>030731093845884002023
>>  FileNames[2]:
>>C:\jcy\Qt\TestApp\DICOMSeries\Series/1.3.12.2.1107.5.2.1.5603.20
>>030731093845884002022
>>......
>>
>>Do you get the same messages when you run itkDICOMImageSeriesTest.cxx?
>>
>>
>>
>>Thank you for your help.
>>
>>
>>Chunyan
>>
>>_______________________________________________
>>Insight-users mailing list
>>Insight-users at itk . org
>>http://www . itk . org/mailman/listinfo/insight-users
>>
>>_______________________________________________
>>Insight-users mailing list
>>Insight-users at itk . org
>>http://www . itk . org/mailman/listinfo/insight-users
>>
> 
> 
> 
> 
>