X-Git-Url: https://git.creatis.insa-lyon.fr/pubgit/?a=blobdiff_plain;f=Doc%2FWebsite%2FNews.html;h=f44d24354fc321cf7afd33cdf6d237fa41c06973;hb=998942248b883bf900e3b6918d4ff13aa8084aaf;hp=1acc042cc79a964c0f3e0fc9204719186e56e1a8;hpb=5309cf35068555280610775b250a6eb82002cb8b;p=gdcm.git diff --git a/Doc/Website/News.html b/Doc/Website/News.html index 1acc042c..f44d2435 100644 --- a/Doc/Website/News.html +++ b/Doc/Website/News.html @@ -7,9 +7,105 @@ - + +

Gdcm News

+ + +

+ + Missing features +

+We know the following are missing; don't loose time looking for them ...
+We know they could be helpfull. We shall add them some day.
+Any contribution is welcome. +

Decoders +
- gdcm doesn't read yet JPEG-LS encoded files. +
  +
- gdcm doesn't read yet JPEG2000 encoded files. +
  +
- gdcm doesn't read yet MPEG2 encoded files. +
  +
+
Reader +
- Allow user to tell gdcm::Document constructor he just wants + to load a given list of DocEntries + (to save CPU time and RAM space) +
- Allow 'frame by frame' reading (should be helpfull for huge + multiframe images) +
- Allow subvolume selection / frames selection before reading. +
- Expose Read/Decompression mechanisms to allow user getting + information from DICOMDIR
  -or from his own Data Base- + and reading his images without parsing + the header, one more time. +
+
Writer +
- Allow user to tell the Writer he doesn't want to write down + SeqEntry (if any) +
- Allow user to tell the Writer he doesn't want to write down + Shadow groups (if any) +
- Allow user to tell the Writer which compression mode he wants
  + (Right now, no one is available) +
- Allow user to tell the Writer he wants to split a + Multiframe image into a serie of + Single frame images. +
- Allow user to tell the Writer he wants to agregate a + Serie of Single frame images into a + Multiframe image. +
+
Reader / Writer +
- Full Icon Image management (Read and Write) +
- Full Overlays management (Read and Write)
  + both for 'ACR-NEMA style' (using groups 0x6000 + and nexts) and 'DICOM V3 style' (using Sequences) +
+
DICOMDIR +
- DICOMDIR full management (not limited to + PATIENT/STUDY/SERIE/IMAGE) +
- Allow user to add an entry (belonging to the file header Dicom + entries)to the default entry list, before + making a DICOMDIR from a root directory +
- Allow user to add an entry of his owns (for instance an Icon + to each image, or to each Serie). +
+
SerieHelper +
- An accurate SerieHelper
  + Right now SerieHelper only works on 'bona fide Series', and + breaks on wrongly forged Series.
  + We are still looking for any heuristics... +
- A SerieHelper that would use the DICOMDIR (if any) + instead of parsing all the files within the Root Directory +
+
Other +
- 16-bits-LUT full Management +
- User friendly management of Rescale Slope and + Rescale Intercept +
- Allow parsing the Shadow groups against a user supplied + private Dicom Dictionary (pfff!...) +
+

@@ -23,79 +119,96 @@

gdcm UML Class Diagram current version. -

New Features / Bug fixes +

New Features

-
+
Both vtkgdcmViewer and vtkgdcmViewer2 + are available to allow easy displaying of single/multiframe + GreyLevel/RGB/PaletteColor images +
DICOMDIR anonymiser (Load and Noload mode) +
User is now allowed to tell gdcm::Document constructor + he doesn't want to deal with SeqEntry + (every time it's possible)
and/or he doesn't + want to deal with Shadow groups (every time it's + possible)
+ use :
+ gdcm::File *f = new gdcm::File(); + f->SetLoadMode(NO_SEQ | NO_SHADOW); + f->Load(fileName); + + instead of :
+ + gdcm::File *f = new gdcm::File(fileName);
+ (old style still available) + +
User is now allowed to tell gdcm::DicomDir constructor + he doesn't want to deal with SeqEntry + (every time it's possible)
and/or he doesn't + want to deal with Shadow groups (every time it's + possible)
+ use :
+ gdcm::DicomDir *dcmdir = new gdcm::DicomDir( ); + dcmdir->SetParseDir(true); + dcmdir->SetLoadMode(NO_SEQ | NO_SHADOW); + dcmdir->Load(dirName); + + instead of :
+ + gdcm::DicomDir *dcmdir = new gdcm::DicomDir(dirName, true);
+ (old style still available) +

A.P.I. breaking modifications (since previous version) -

+
Bug fixes +
- The difference between MONOCHROME1 (low values = bright, + high values = dark) and MONOCHROME2 (low values = dark, + high values = bright) is now taken into account.
  + It's no longer up to the user to change the pixels value +
- Writing a 'True Dicom' image after reading an ACR-NEMA image + does not request any longer from the user to build up + 'manually' the Meta Elements group (Ox0002) +
- Old '24 Bits' ACR-NEMA are now correctly re-written + in DICOM V3 mode. +
- Element 0x0000 of Shadow groups is always forced to be a + ValEntry and its VR is forced to UL
-
Missing features -
- gdcm doesn't read yet JPEG-LS and JPEG2000 encoded files. -
- Allow user to tell gdcm::Document constructor he doesn't - want to deal with SeqEntry Allow user to tell gdcm::Document constructor he doesn't - want to deal with Shadow groups -
- Allow user to tell the Writer he doesn't want to write down - SeqEntry (if any) -
- Allow user to tell the Writer he doesn't want to write down - Shadow groups (if any) -
- Icon Image management (Read and Write) -
- DICOMDIR full management (not limited to - PATIENT/STUDY/SERIE/IMAGE) -
- Allow user to add an Entry to the default entry list, for - making a DICOMDIR from a root directory -
- DICOMDIR anonymiser (Load and Noload mode) -
- 16-bits-LUT full Management -
- User friendly management of Rescale Slope and - Rescale Intercept -
- Allow parsing the Shadow groups against a user supplied - Private Dicom Dictionary (pfff!...) -
- An accurate SerieHelper -
+
A.P.I. breaking modifications (since previous version : 1.0) +
- NEVER more API breaking modifications !!! +
Known bugs
- The difference between MONOCHROME1 and MONOCHROME2 - is not taken into account. It's up to the user to change the pixels - value -
- Writing a 'True Dicom' image after reading an ACR-NEMA image requests - from the user to build up 'manually' the Meta Elements group (0002) -
- Management, on Big Endian Processors, of unloaded BinEntries +
- Use of Implicit Value Representation writting mode may + causes troubles, when there are some SQ belonging to a + Shadow Group.
  + Better you use Explicit Value Representation writting mode ...
+

Version 1.0 (Feb 14 2005)

- - - - -

State of the art
- - gdcm 1.0 UML Class Diagram version. -
- User Documentation" -
- Developper -Documentation" +
- + gdcm 1.0 UML Class Diagram version. +
- User Documentation" +
- Developper + Documentation"
- 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
  @@ -104,51 +217,52 @@ Documentation"
-
A.P.I. breaking modifications (since previous version) +
A.P.I. breaking modifications (since previous version : 0.6)
- 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 +
- Use of namespace : all the methods formerly named + className::gdcmXxx() are now named className::Xxx() +
  End user will have to call them as gdcm::className::Xxx() +
- a gdcm::Document is now specialized in : +
  - gdcm::DicomDir +
  - gdcm::File +
  +
- a gdcm::DicomElementSet is composed of a set of + gdcm::DicomDocEntry +
- a gdcm::DicomDocEntry can be : +
  - a gdcm::ContentEntry, specialized in : +
    - gdcm::ValEntry +
    - gdcm::BinEntry (no longer a specialization of + gdcm::ValEntry) +
    +
  - a gdcm::SeqEntry +
  +
- Removal of useless accessors GetXxxByname, SetXxxByname +
- Renaming of accessors GetXxxByNumber, SetXxxByNumber + as follow : +
  - GetEntryByNumber + + --> GetEntryValue +
  - GetEntryLengthByNumber --> GetEntryLength +
  - GetEntryOffsetByNumber --> GetEntryOffset +
  - GetEntryVRByNumber + --> GetEntryVR +
  - +
  - GetDocEntryByNumber + --> GetDocEntry +
  - GetValEntryByNumber + --> GetValEntry +
  - GetBinEntryByNumber + --> GetBinEntry +
  - GetSeqEntryByNumber + --> GetSeqEntry +
-

- -
-

-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
-

- - -

@@ -159,29 +273,38 @@ We consider now that : This version will be used by Insight Tool Kit (ITK 2.0) at the beginning of 2005.
It's not yet packaged ...

-
gdcm 0.6 UML Class Diagram version.
User Documentation"
Developper Documentation"
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 `gdcmSQItem`s -
a `gdcmSQItem` is_a `gdcmElementSet` -
-
Improvement of the jpeg sub-library: jpeg - compressed Dicom files (lossless and lossy) - might be read (check-it out) +
any dicom related file is a `gdcmDocument` +
a `gdcmDocument` can be : +
+
a `gdcmHeader`, if it contains pixel data +
a `gdcmDicomDir`, if it contains only informations + on the files in a given directory +
+ +
a `gdcmDocument` is_a `gdcmElementSet`, + composed of a set of `gdcmEntry` separated into : +
+
`gdcmValEntry`
+ a specialization of `gdcmValEntry`, for 'non + `std::string` representable' values is + `gdcmBinEntry` +
`gdcmSeqEntry` (VR = `SQ`, i.e Dicom Sequences)
+ they are dealt as tree-like structures :
+ - a `gdcmSeqEntry` is considered as a set + of `gdcmSQItem`,
+ - a `gdcmSQItem` is_a `gdcmElementSet`, composed + of `gdcmDocEntries`, recursively
+
+ +
Improvement of the jpeg sub-library: jpeg + compressed Dicom files (lossless and lossy) + might be read (check-it out) @@ -192,9 +315,9 @@ We consider now that :

gdcm 0.4 UML Class Diagram. -
User Documentation" -
Developper Documentation +
gdcm 0.4 UML Class Diagram. +
User Documentation" +
Developper Documentation
Introduction of a jpeg sub-library: some very simple jpeg-lossy compressed Dicom files might be working (check-it out). @@ -203,6 +326,10 @@ We consider now that : supporting both Swig and vtk wrapping.
Introduction of a RLE (Run-Time Encoding) library
Color images (RGB or Palette Color) are dealt with +
Confusing names gdcmPatient, gdcmStudy, + gdcmSerie, gdcmPatient changed to + gdcmDicomDirPatient, gdcmDicomDirStudy, + gdcmDicomDirSerie, gdcmDicomDirPatient