Gdcm News

Current Version

• Final check of the jpeg sub-library: all 'classical' jpeg compressed Dicom files can be read
  All the previously gdcm-breaker images are now readable
  gdcm doesn't read yet JPEG-LS and JPEG2000 encoded files.
• Use of namespace : all the methods formerly called className::gdcmXxx() are now called className::Xxx()
• Removal of accessors GetXxxByname, SetXxxByname and GetXxxByNumber, SetXxxByNumber replaced by GetXxx, SetXxx
• a gdcm::Document is now specialized in gdcm::DicomDir and gdcm::File
• A huge number of memory leaks removed
• Improvement of write process

For people who get this new release :

We consider now that :
- any dicom related file is a gdcm::Document.
- a gdcm::Document can be :
      - a gdcm::File,     if it contains pixel data,
      - a gdcm::DicomDir, if it contains only informations 
                          on the files in a given directory

- in a gdcm::Document, there are gdcm::DocEntry, that can be :
     - gdcm::ContentEntry (any entry that has an actual value,
                           *not* an embedded set of other gdcm::DocEntry)
                           a gdcm::ContentEntry can be :
          - gdcm::ValEntry (whose value is std::string representable 
                            e.g. character values, or integers),
          - gdcm::BinEntry (whose value is not std::string representable 
                            e.g. color palettes, overlays, icons , ...)
     - gdcm::Sequence (no proper 'value', but a set of gdcm::SQItems, 
                       composed of a set of gdc::DocEntry, recursively)
 
- in a gdcm::DicomDir, we only deal, hierarchically, with :
     - gdcmPatient
     - gdcmStudy
     - gdcmSerie
     - gdcmImage

Version 0.6 (June 8 2004)

This version will be used by Insight Tool Kit (ITK 1.10) at the beginning of 2005.
It's not yet packaged ...


• The new gdcmDocument class is a parent class of gdcmHeader class and gdcmDicomDir class.
• Massive modifications in the Class Diagram :
  • Entries (gdcmEntry) are now separated into ValEntry and SeqEntry (whose VR = SQ)
  • a gdcmDocument is_a gdcmElementSet, composed of a set of gdcmValEntry and gdcmSeqEntry
  • a gdcmSeqEntry is considered as a set of gdcmSQItem
  • Dicom Sequences (VR = SQ) are now dealt as tree-like structures within gdcmSQItem class.
    they are considered as a set of gdcmSQItems
  • a gdcmSQItem is_a gdcmElementSet
• Improvement of the jpeg sub-library: jpeg compressed Dicom files (lossless and lossy) might be read (check-it out)

Version 0.4 (February 6 2004)

• Introduction of a jpeg sub-library: some very simple jpeg-lossy compressed Dicom files might be working (check-it out).
• And also, fewer memory leaks, cleaned-up stl usage (should work with gcc-3.x), python disutil installer (see file setup.py) supporting both Swig and vtk wrapping.
• Introduction of a RLE (Run-Time Encoding) library
• Color images (RGB or Palette Color) are dealt with

Version 0.3 (July 8 2003)

• gdcmFile class now enables acces to the data i.e. the image[s] content. Previously only parsing of the Dicom header was available through usage of gdcmHeader class.
• a VTK plugin of gdcm is now available through the vtkGdcmReader vtk class (see it as a vtk wrapper of gdcm), which enables
  • Loading of a single image,
  • Loading of a stack of images from multiple Dicom files,
  • this class is wrapped for vtkPython (by using native vtk wrappers).
• Introduction of a jpeg sub-library: lossless-jpeg compressed Dicom files work.
• vtkgdcmViewer allows easy displaying of single/multiframe GreyLevel/RGB/PaletteColor images

Version 0.1 (April 1 2003)

---

Version 0.0 (March 14 2003)

---