[Insight-users] GDCM 1.2 update status.

[Mathieu Malaterre]

Martin,

	I have update the testing and example to describe how to use the new 
API. I also wrote a document which should be available through the 
Insight Journal, or you can get it directly at:

    https://caddlab.rad.unc.edu/MIDAS/handle/1926/166

	Anyway what I would do as a test is run:

./bin/DicomSeriesReadImageWrite2 /full/path/to/my/DICOM/data bla.vtk

	The output should look like:
"""
The directory:

/full/path/to/my/DICOM/data

Contains the following DICOM Series:

1.3...
1.4...
1.5...
...

Now reading series:

1.3....


Writing the image as

bla.vtk

If you get error message esp related to anything duplicated that means 
the default values are not enough for you and you should therefore 
refine on more parameter. In particular if you have echo time, you need 
to add a restriction on DICOM Tag: 0018,0081.

Let me know if the pdf + example + testing are enough documentation
Mathieu


Martin Kavec wrote:
> Thanks a lot Mathieu,
> 
> I am downloading the cvs right now (hope the files are already updated) and 
> report back in case of troubles.
> 
> One question though: if I decide to sort a time series (4D image) based on the 
> acquisition time, can I be certain that the 3D volumes within the series will 
> be automatically sorted based on the image position?
> 
> Cheers,
> 
> Martin
> 
> On Friday 03 February 2006 16:51, Mathieu Malaterre wrote:
> 
>>Hello happy gdcm users,
>>
>>	So I believe I am done with the update of gdcm 1.0 to gdcm 1.2. Let's
>>start with the bad news:
>>
>>API Change(*)
>>	- By default I decided to turn legacy silent off. If you edit your
>>CMakeCache.txt you'll find a variable: GDCM_LEGACY_SILENT:OFF. What that
>>mean is (if you use a decent compiler) that every time you use a
>>deprecated method the compiler will yell at you. If you do not want
>>that, then you have to manually change this variable to ON, to allow
>>compiler to go on without warnings.
>>	- If you decide to turn GDCM_LEGACY_REMOVE:ON, what this means is that
>>the legacy code will simply be removed from the library. Therefore you
>>won't get warning, but compiler errors ! Turn to ON only if you want to
>>make sure you are using the latest and greatest of gdcm :)
>>
>>
>>Now for the good news:
>>User have finally a more flexible way to restrict Series.
>>1. Using AddRestriction. In the past using SetUseSeriesDetails(true)
>>would set by default the following DICOM tags to be inspected in order
>>to find out DICOM file potentially out of a particular Series. Now you
>>can explicitly specify which tag to use. What this also means, to ensure
>>full backward compatibility is that in order to use AddRestriction the
>>old default values are taken into account, and there is currently no way
>>to remove those default values.
>>See DicomSeriesReadImageWrite2 for an example of use
>>
>>2. Using operators. Let say you have a series of 1000 slices and you are
>>only interested in let say slice 500-600. Since the filenames does not
>>always explicitly says which slice they represent, you can tell the
>>GDCMSeriesFileNames to look for those slices for you.
>>See itkGDCMSeriesReadImageWrite for an example of use.
>>
>>3. Full support of JPEG2000 DICOM file ! Thanks to the OpenJPEG team we
>>have a working J2K implementation that compress/decompress even 16bits
>>images(**).
>>
>>4. Load time is now speared from construct time. This mean you can now
>>specify what skip operation you want to do (skip shadow group, skip
>>sequence...)
>>
>>5. More support of private dictionaries. Look into gdcm/Dicts to have a
>>list of shadows DICOM tag. You can either add them at compile time, or
>>at run time.
>>
>>6. More DICOMDIR support.
>>
>>
>>Ps: I tried my best to keep full backward compatibility, if you think I
>>missed something, please let me know ASAP.
>>Mathieu
>>
>>
>>(*)
>>http://insightsoftwareconsortium.org/wiki/index.php/Administration-Backward
>>Compatibility#Current_Draft_of_the_ISC_Policy_on_Backward_Compatibility
>>
>>(**) gdcm for a while was using JasPer another open source J2K
>>implementation but it suffers from a serious decompression bug for
>>16bits lossless images.
>>_______________________________________________
>>Insight-users mailing list
>>Insight-users at itk.org
>>http://www.itk.org/mailman/listinfo/insight-users
> 
>