[Insight-developers] Re: Proposal: Change default DICOM
fromDICOMImageIO2 to GDCMImageIO
Miller, James V (Research)
millerjv at crd.ge.com
Mon Apr 18 16:36:36 EDT 2005
Keep in mind that under most circumstances, we would NOT use the
same instance of GDCMImageIO to read files and to write files.
Under this model, wouldn't a single "SetDirectory" call be
sufficient?
Jim
-----Original Message-----
From: insight-developers-bounces at itk.org
[mailto:insight-developers-bounces at itk.org]On Behalf Of Mathieu
Malaterre
Sent: Monday, April 18, 2005 1:31 PM
To: Lorensen, William E (Research)
Cc: Insight Developers
Subject: [Insight-developers] Re: Proposal: Change default DICOM
fromDICOMImageIO2 to GDCMImageIO
Lorensen, William E (Research) wrote:
> Folks,
> I'd like to start a discussion about making GDCM the default DICOM reader/writer in itk. Please add your comments to:
> http://www.itk.org/Wiki/Proposals:Make_GDCM_the_default_DICOM
No sure if this is usefull to add to the wiki:
1. DICOMSeriesFilenames
There is a lot of work to do. Keep in mind that those class were written
against gdcm 0.5 which had lot less advanced features. Anyway to enhance
the class I would also suggest it can have multiple choices of
generating names:
a) Keep the original name, but then we have to write files in another
directory (thus we need an 'input' dir and an 'output' dir).
b) Since DICOM does not specify the naming convention for the filename,
we should be able to write the file under its UID (it's garantee to be
unique!).
c) Another approach (more conventional) would be to specify a prefix and
a pattern. (we don't require two differents directories anymore).
2. DICOMSeriesFilenames
gdcm 0.6 could only handle one serie within a directory. gdcm 1.0 and
above have a much easier API to manipulate multiple series (and order
files) within the same directory. For more info see gdcm::SerieHelper
Mathieu
_______________________________________________
Insight-developers mailing list
Insight-developers at itk.org
http://www.itk.org/mailman/listinfo/insight-developers
More information about the Insight-developers
mailing list