X-Git-Url: https://git.creatis.insa-lyon.fr/pubgit/?a=blobdiff_plain;f=Doc%2FWebsite%2FNews.html;h=f44d24354fc321cf7afd33cdf6d237fa41c06973;hb=998942248b883bf900e3b6918d4ff13aa8084aaf;hp=db5827e6997b71214ec03f152e6fd37999b8de08;hpb=a837e70d25b3acfa256513549967e07c8b01cde4;p=gdcm.git
diff --git a/Doc/Website/News.html b/Doc/Website/News.html
index db5827e6..f44d2435 100644
--- a/Doc/Website/News.html
+++ b/Doc/Website/News.html
@@ -8,10 +8,10 @@
-
+
Gdcm News
-
+
@@ -21,31 +21,91 @@
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.
-
- - gdcm doesn't read yet JPEG-LS and JPEG2000 encoded files.
-
- 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 user to tell the Writer he doesn't want to write down
+
- Decoders
+
+ - gdcm doesn't read yet JPEG-LS encoded files.
+
+ We said 'JPEG-LS', not Lossless Jpeg ...
+ [JPEG-LS is the basis for new lossless/near-lossless compression
+ standard for continuous-tone images intended for JPEG2000.
+ The standard is based on the LOCO-I algorithm
+ (LOw COmplexity LOssless COmpression for Images)
+ developed at Hewlett-Packard Laboratories]
+
+ - gdcm doesn't read yet JPEG2000 encoded files.
+
+ But we are working on it.
+
+ - gdcm doesn't read yet MPEG2 encoded files.
+
+ But we are working on it.
+
+
+ - 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
+
- 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
+
- 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 to the default entry list, before
+
- 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
-
- 16-bits-LUT full Management
-
- User friendly management of Rescale Slope and
+
- 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
+
- Allow parsing the Shadow groups against a user supplied
private Dicom Dictionary (pfff!...)
-
- An accurate SerieHelper
-
- A SerieHelper that would use the DICOMDIR (if any)
- instead of parsing all the files within the Root Directory
+
-
@@ -67,7 +127,8 @@ Any contribution is welcome.
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
+ 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
@@ -79,9 +140,24 @@ Any contribution is welcome.
instead of :
- gdcm::File *f = new gdcm::File(fileName);
-
-
+ 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)
@@ -91,12 +167,13 @@ Any contribution is welcome.
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
+ 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 (0002)
- Old '24 Bits' ACR-NEMA are now correctly re-written in DICOM mode.
- Element 0x0000 of Shadow groups is always forced to be a
- ValEntry and its VR is forced to UL
+ '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
@@ -108,14 +185,12 @@ Any contribution is welcome.
Known bugs
- -
+
- 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 ...
- Sample Data
-