[Suspected Spam][Insight-developers] Image3D ==> DicomSeries : Proposal

[Lorensen, William E (GE, Research)]

Luis,
I have added the following to the Wiki proposal:

Lorensen Comments 
I would rather not add DICOM specific code to ImageSeriesWriter. Some sort of a helper class could be created that would populate the MetaDataDictionary for each slice. Helper classes would permit us to produce a variety of DICOM headers if need be. Many of the commercial Radiology workstations such as GE's Advantage Windows require tags that vary depending upon the vendor. 

However, there is a know problem in image series writer. It invokes a 2D reader for each image. It passes down a 2D position and 2D orientation. DICOM, even though it is a 2D format, has a 3D position. This needs to be resolved for GDCMImageIO to generate proper image position patient. 


-----Original Message-----
From: insight-developers-bounces+lorensen=crd.ge.com at itk.org
[mailto:insight-developers-bounces+lorensen=crd.ge.com at itk.org]On Behalf
Of Luis Ibanez
Sent: Monday, March 20, 2006 8:13 PM
To: Insight Developers List
Cc: Julien Jomier; Mathieu Malaterre
Subject: [Suspected Spam][Insight-developers] Image3D ==> DicomSeries :
Proposal



We found recently that with the current ITK version
we cannot perform correctly the following task:


     Read a 3D image from a non-DICOM source
     and write it as a series of 3D DICOM slices.


If we use the ImageSeriesWriter + GDCMImageIO
for doing this the following undesirable behaviors
take place:

   1) The information for the DICOM header is the
      same for all the DICOM slices.

   2) Interslice spacing is set to zero

   3) Origin of all the slices is incorrectly set.

   4) Orientation of the original image is lost.


We would like to correct for these deficiencies.
With that goal in mind a proposal

http://www.itk.org/Wiki/ITK_Oversight_Committee#Proposals

has been added to the page:

http://www.itk.org/Wiki/Proposals:Writing_DICOM_from_non-DICOM

and a Example with the desired "Use Case" has been
added to the directory Insight/Examples/IO/  with
the name

          ImageReadDicomSeriesWrite.cxx

The current suggested solution is to add code to the
ImageSeriesWriter for managing the case when a meta
data dictionary is not provided. In this case the
ImageSeriesWriter should internally create a meta
data dictionary using information from the Input image
and update for each slice the data corresponding to the
image-slice origin, orientation and spacing


   Any feedback on this proposal is welcome,



      Thanks


         Luis




_______________________________________________
Insight-developers mailing list
Insight-developers at itk.org
http://www.itk.org/mailman/listinfo/insight-developers