1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
4 <META http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
5 <TITLE>Gdcm News</TITLE>
11 <!--#######################################################################-->
12 <H1>Gdcm News</a></H1>
14 <!--#######################################################################-->
16 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
18 <A CLASS="anchor" NAME="missing">
19 <B>Missing features</B></A>
21 We know the following are missing; don't loose time looking for them ...<br>
22 We know they could be helpfull. We shall add them some day.<br>
23 Any contribution is welcome.
27 <LI> gdcm doesn't read yet <TT>JPEG-LS</TT> encoded files.
29 We said '<TT>JPEG-LS</TT>', not Lossless Jpeg ...<br>
30 [<TT>JPEG-LS</TT> is the basis for new lossless/near-lossless compression
31 standard for continuous-tone images intended for <TT>JPEG2000</TT>.
32 The standard is based on the LOCO-I algorithm
33 (LOw COmplexity LOssless COmpression for Images)
34 developed at Hewlett-Packard Laboratories]
36 <LI> gdcm doesn't read yet all <TT>JPEG2000</TT> encoded files.
38 But we are working on it (a lot of troubles with Jasper).
39 Update: as of Oct 10 2005, we are currently investigating another library:
40 openjpeg. The problem still exist for this library but one of the author
41 is currently working on it:
42 http://www.openjpeg.org/forum/viewtopic.php?t=18
44 <LI> gdcm doesn't read yet <TT>MPEG2</TT> encoded files.
49 <LI> Allow user to tell <TT>gdcm::Document</TT> constructor he just wants
50 to load a given list of <TT>DocEntries</TT>
51 (to save CPU time and RAM space)
52 <LI> Allow 'frame by frame' reading (should be helpfull for huge
54 <LI> Allow subvolume selection / frames selection before reading.
55 <LI> Expose Read/Decompression mechanisms to allow user getting
56 information from <tt>DICOMDIR</TT> <br> -or from his own Data Base-
57 and reading his images without parsing
58 the header, one more time.
62 <LI> Allow user to tell the Writer he doesn't want to write down
63 <TT>SeqEntry</TT> (if any)
64 <LI> Allow user to tell the Writer he doesn't want to write down
65 <TT>Shadow groups</TT> (if any)
66 <LI> Allow user to tell the Writer which compression mode he wants<br>
67 (Right now, no one is available)
68 <LI> Allow user to tell the Writer he wants to split a
69 <TT>Multiframe</TT> image into a serie of
70 <TT>Single frame</TT> images.
71 <LI> Allow user to tell the Writer he wants to agregate a
72 Serie of <TT>Single frame</TT> images into a
73 <TT>Multiframe</TT> image.
77 <LI> Full <TT>Icon Image</TT> management (Read and Write)
78 <LI> Full <TT>Overlays</TT> management (Read and Write) <br>
79 both for '<TT>ACR-NEMA</TT> style' (using groups <TT>0x6000</TT>
80 and next) and '<TT>DICOM V3</TT> style' (using Sequences)
82 <LI> <TT>DICOMDIR</TT>
84 <LI> <TT>DICOMDIR</TT> full management (not limited to
85 <TT> PATIENT</TT>/<TT>STUDY</TT>/<TT>SERIE</TT>/<TT>IMAGE</TT>)
86 <LI> Allow user to add an entry (belonging to the file header Dicom
87 entries)to the default entry list, before
88 making a <TT>DICOMDIR</TT> from a root directory
89 <LI> Allow user to add an entry of his owns (for instance an <TT>Icon</TT>
90 to each image, or to each Serie).
95 <LI> An accurate <TT>SerieHelper</TT> <br>
96 Right now <TT>SerieHelper</TT> only works on 'bona fide Series', and
97 breaks on wrongly forged Series.<br>
98 We are still looking for any heuristics...
99 <LI> A <TT>SerieHelper</TT> that would use the <TT>DICOMDIR</TT> (if any)
100 instead of parsing all the files within the Root Directory
104 <LI> 16-bits-LUT full Management
105 <LI> User friendly management of <TT>Rescale Slope</TT> and
106 <TT>Rescale Intercept</TT>
107 <LI> Allow manual adjunction / automatic recognition (pfff!...)
108 of the private <TT>Dicom Dictionary</TT>
109 to be used to parse <TT>Shadow groups</TT> against.
112 <!#######################################################################>
113 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
115 <A CLASS="anchor" NAME="NewsCurrentVersion">
116 <B>Current Version (CVS)</B></A>
121 <LI> <A HREF="News.html#missing">Missing Features</a>
125 <a href="uml-gdcm.pdf">gdcm UML Class Diagram</a> current version.
126 <LI> <a href= "Doc1.2/html.user/index.html">User Documentation</a>
127 <LI> <a href= "Doc1.2/html.developper/index.html">Developper
135 <LI> API breaking modiffications (since previous version)
158 <!#######################################################################>
159 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
161 <A CLASS="anchor" NAME="NewsVersion1_1">
162 <B>Version 1.1 (September 14 2005)</B></A>
167 <a href="Doc1.0/uml-gdcmV1.0.pdf">gdcm 1.1 UML Class Diagram</a> version.
168 <LI> <a href= "Doc1.0/html.user/index.html">User Documentation</a>
169 <LI> <a href= "Doc1.0/html.developper/index.html">Developper
174 <TT>gdcm::Dict:AddDict(std::string fullPathPrivateDictionaryFileName)</TT>
176 <TT>gdcm::Dict::RemoveDict(std::string fullPathPrivateDictionaryFileName)</TT>
178 to allow user to choose the 'Private Dictionary' he wants to work with.
180 One can dream about a better API;<br>
181 This one allow right now anybody to see very easyly if the use
182 of a given private dicom dictionary is of any help or not.
185 <TT>PrintFile</TT> has now a new command line argument manager option :<br>
186 <TT>dict=fullPathNamePrivateDictionaryFile</TT><br>
187 to allow user to see with no extra coding what differences
188 makes the use or not of a private Dicom Dictionary.<br>
189 e.g. : use it as follow <br>
190 <TT>PrintFile filein=myGEdicomFile.dcm
191 dict=/user/userName/gdcm/Dicts/GEMS-Advance.dic</TT>
194 (Not a great one ...)
195 Stupid method names : <br><TT>DicomDir::WriteDicomDir()</TT>
196 and <TT>DicomDir::AnonymizeDicomDir()</TT> <br>replaced by : <br>
197 <TT>DicomDir::Write()</TT>
198 and <TT>DicomDir::Anonymize()</TT>
201 void Document::AddForceLoadElement(uint16_t group, uint16_t elem);
203 allows user to tell <TT>gdcm::Document</TT> Loader he wants
204 to force the loading of a given set of <TT>DocEntries</TT>,
205 even if their length exceeds the current
206 <TT>MAX_SIZE_LOAD_ELEMENT_VALUE</TT>.
209 Many users expect from <TT>vtkGdcmReader</TT> it 'orders' the images
210 (that's the job of <TT>gdcm::SerieHelper</TT> ...)<br>
211 When user <b>knows</b> the files with same Serie UID
212 have same sizes, same 'pixel' type, same color convention, ...
213 the right way to proceed is as follow :
215 gdcm::SerieHelper *sh= new gdcm::SerieHelper();
216 // if user wants *not* to load some parts of the file headers
217 sh->SetLoadMode(loadMode);
219 // if user wants *not* to load some files
220 sh->AddRestriction(group, element, value, operator);
221 sh->AddRestriction( ...
222 sh->SetDirectory(directoryWithImages);
224 // if user *knows* how to order his files
225 sh->SetUserLessThanFunction(userSuppliedComparisonFunction);
227 // if user wants to sort reverse order
228 sh->SetSortOrderToReverse();
230 // here, we suppose only the first 'Single SerieUID' Fileset is of interest
231 // Just iterate using sh->NextSingleSerieUIDFileSet()
232 // if you want to get all of them
233 gdcm::FileList *l = sh->GetFirstSingleSerieUIDFileSet();
235 // if user is doesn't trust too much the files with same Serie UID
236 if ( !sh->IsCoherent(l) )
237 return; // not same sizes, or not same 'pixel type' -> stop
239 sh->OrderFileList(l); // sort the list
241 vtkGdcmReader *reader = vtkGdcmReader::New();
242 // if user wants to modify pixel order (Mirror, TopDown, ...)
243 // he has to supply the function that does the job
244 // (a *very* simple example is given in vtkgdcmSerieViewer.cxx)
245 reader->SetUserFunction (userSuppliedFunction);
247 // to pass a 'Single SerieUID' Fileset as produced by gdcm::SerieHelper
248 reader->SetCoherentFileList(l);
251 You can see a full example in <TT>vtk/vtkgdcmSerieViewer.cxx</TT><br>
254 <TT>vtkgdcmSerieViewer dirname=Dentist mirror</TT><br>
255 <TT>vtkgdcmSerieViewer dirname=Dentist reverse</TT><br>
256 <TT>vtkgdcmSerieViewer dirname=Dentist reverse topdown</TT><br>
260 <LI> <TT>vtkGdcmReader::SetUserFunction (userSuppliedFunction)</TT><br>
262 <TT>void userSuppliedFunction(uint8_t *imageData, File *f);</TT><br>
263 allows user to reorganize the pixels of each image just after reading
264 it (to mirror, or topdown the image, for instance)<br>
265 Note : <TT>uint8_t *</TT> doesn't mean it works only on 8 Bits images.
266 <br> It's for prototyping. Feel free to cast it.
269 SerieHelper::SetUserLessThanFunction(userSuppliedComparisonFunction)
270 </TT><br> with : <br>
271 <TT>bool userSuppliedComparisonFunction(File *, File *);</TT><br>
272 allows user -when he knows more about his files than gdcm does-
273 to give his own comparison function.
274 <LI> <TT>SerieHelper::SetSortOrderToReverse</TT> allows user to ask
275 to sort the Files reverse order.
276 <LI> <TT>SerieHelper::AddRestriction</TT> has now a new constructor<br>
277 <TT>AddRestriction(group, element, value, operator);</TT><br>
278 allows user to exclude some files from the sorting, according to
279 any comparison operator <br>
280 (<TT>GDCM_EQUAL</TT>, <TT>GDCM_DIFFERENT</TT>,
281 <TT>GDCM_GREATER</TT>, <TT>GDCM_GREATEROREQUAL</TT>,
282 <TT>GDCM_LESS</TT>, <TT>GDCM_LESSOREQUAL</TT>), not only on the
285 <LI> <TT>AnonymizeNoLoad</TT> used with <TT>dirin=inputDirectoryName</TT>
286 anonymizes all the files within the given Directory.
288 User may also choose extra elements he wants to rub out: <br>
289 <TT>rubout=listOfElementsToRubOut</TT><br>
290 with <tt>listOfElementsToRubOut : group1-elem1,group2-elem2,
291 ...</TT> (in hexa, no space within the list )
293 <LI> <TT>gdcm::SerieHelper()</TT> has a new method
294 <TT>void AddGdcmFile(File *header)</TT>, that allows aware user to
295 create a '<TT>FileList</TT>' (actually a
296 <TT>std::vector< File* > </TT>).<br>
297 The <TT>FileList</TT> created this way will be the
298 'first one' in the <TT>gdcm::FileHelper()</TT> (retrieve it with
299 <TT>FileList *GetFirstCoherentFileList()</TT> ).<br>
300 It may be sorted using <TT>OrderFileList</TT>.<br>
301 No 'coherence check' will be performed on this <TT>FileList</TT>
303 It may be passed to a <TT>vtkGdcmReader</TT>
304 (to avoid parsing twice the files)
306 <LI> <TT>vtkGdcmReader</TT> can now get the result of
307 <TT>gdcm::SerieHelper</TT> (to avoid parsing twice the files)<br>
308 Proceed as follow :<br>
310 gdcmSerieHelper *sh = new gdcmSerieHelper();
311 sh->SetDirectory(myImageDirectory, true);
312 gdcmFileList *l = s->GetFirstCoherentFileList();
315 vtkGdcmReader *gr = new vtkGdcmReader();
316 gr->SetCoherentFileList(l);
319 This works with a directory that contains only one '<TT>Serie</TT>'
320 (same <TT>Serie UID</TT> for all the images).<br>
321 If it contains more than one <TT>Serie</TT>, you'll have to loop
322 on the Series, using <TT>GetNextCoherentFileList()</TT>;<br>
323 It will be up to the user to delete the <TT>gdcm::File</TT>.
325 See <TT>vtkgdcmSerieViewer</TT> for an example.
327 <LI> Both <TT>vtkgdcmViewer</TT> and <TT>vtkgdcmViewer2</TT>
328 are available to allow easy displaying of single/multiframe
329 GreyLevel/RGB/PaletteColor images<br><br>
330 <LI> <TT>DICOMDIR</TT> anonymiser (<TT>Load</TT> and <TT>Noload</TT> mode)
332 <LI> Because the <TT>gdcm::DicomDir::Load()</TT> method may be used
333 either for loading an already made <TT>DICOMDIR</TT> file or for
334 parsing all the dicom files with a given root directory we
335 syntaxically separated the operations: <br>
336 For loading an already made <TT>DICOMDIR</TT> file, use : <br>
338 gdcm::DicomDir *d = new gdcm::DicomDir();
339 d->SetFileName(fileName);
343 For parsing all the dicom files within a given root directory, use :<br>
345 gdcm::DicomDir *d = new gdcm::DicomDir();
346 d->SetDirectoryName(dirName);
350 <b>Don't</b> use any longer old deprecated style: <br>
352 gdcm::DicomDir *d = new gdcm::DicomDir();<br>
353 d->SetParseDir(true); // </TT>or <TT>d->SetParseDir(false);<br>
354 d->Load( fileName );<br>
357 <LI> User is now allowed to tell <TT>gdcm::Document</TT> constructor
358 he doesn't want to deal with <TT>SeqEntry</TT>
359 (every time it's possible, i.e for 'true length' Sequences) <br>
360 and/or he doesn't want to deal with <TT>Shadow groups</TT>
361 (every time it's possible i.e. when element <TT>0x0000</TT>
362 exists for this Group) <br>
363 or he doesn't want to deal with <TT>SeqEntry</TT> that belong to a
364 <TT>Shadow group</TT> (every time it's possible
365 -'true length' Sequence-)<br>
368 gdcm::File *f = new gdcm::File();
369 f->SetLoadMode(NO_SEQ); | depending on what
370 f->SetLoadMode(NO_SHADOW); | you want *not*
371 f->SetLoadMode(NO_SEQ | NO_SHADOW);| to load from the
372 f->SetLoadMode(NO_SHADOWSEQ); | target file
373 f->SetFileName(fileName);
376 <b>Don't</b> use any longer old deprecated style: <br>
378 gdcm::File *f = new gdcm::File(fileName);</TT> <br>
380 <LI> User is now allowed to tell <TT>gdcm::DicomDir</TT> constructor
381 he doesn't want to deal with <TT>SeqEntry</TT>
382 (every time it's possible, i.e for 'true length' Sequences) <br>
383 and/or he doesn't want to deal with <TT>Shadow groups</TT>
384 (every time it's possible i.e. when element <TT>0x0000</TT>
385 exists for this Group) <br>
386 or he doesn't want to deal with <TT>SeqEntry</TT> that belong to a
387 <TT>Shadow group</TT> (every time it's possible
388 -'true length' Sequence-)<br>
389 when he parses all the Dicom files within a given directory.<br>
392 gdcm::DicomDir *f = new gdcm::DicomDir();
393 f->SetLoadMode(NO_SEQ); | depending on what
394 f->SetLoadMode(NO_SHADOW); | you want *not*
395 f->SetLoadMode(NO_SEQ | NO_SHADOW);| to load from the files
396 f->SetLoadMode(NO_SHADOWSEQ); | within the root directory
397 f->SetDirectoryName(rootDirectoryName);
400 <b>Don't</b> use any longer old deprecated style: <br>
402 gdcm::DicomDir *dcmdir = new gdcm::DicomDir(dirName, true);</TT><br>
408 <LI> No more trouble when the 'endianess' switches within Sequences.
409 <LI> No more trouble with 'no length Sequences' belonging to a
410 <TT>Shadow Group</TT> when they are 'Implicit VR'.
411 <LI> The difference between <TT>MONOCHROME1</TT> (low values = bright,
412 high values = dark) and <TT>MONOCHROME2</TT> (low values = dark,
413 high values = bright) is now taken into account.<br>
414 It's no longer up to the user to change the pixels value
415 <LI> Writing a 'True Dicom' image after reading an <TT>ACR-NEMA</TT> image
416 does not request any longer from the user to build up
417 'manually' the Meta Elements group (<TT>0x0002</TT>)
418 <LI> Old '24 Bits' <TT>ACR-NEMA</TT> are now correctly re-written
419 in <TT>DICOM V3</TT> mode.
420 <LI> Element <TT>0x0000</TT> of <TT>Shadow groups</TT> is always forced to be a
421 <TT>ValEntry</TT> and its <TT>VR</TT> is forced to <TT>UL</TT>
425 <LI> A.P.I. breaking modifications (since previous version : <TT>1.0</TT>)
427 <LI> NEVER more API breaking modifications !!!
433 <LI> Use of <TT>Implicit Value Representation</TT> writting mode may
434 causes troubles, when there are some <TT>SQ</TT> belonging to a
435 <TT>Shadow Group</TT>. <br>
436 Better you use <TT>Explicit Value Representation</TT> writting mode ...
437 <LI> Troubles on 'Big endian' processors (i.e. Apple/Motorola, SunSparc
438 ...) when writting 16 Bits images.
439 <LI> Troubles on 64-bits processors.
446 <!#######################################################################>
447 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
449 <A CLASS="anchor" NAME="NewsVersion1_0">
450 <B>Version 1.0 (Feb 14 2005)</B></A>
456 <a href="Doc1.0/uml-gdcmV1.0.pdf">gdcm 1.0 UML Class Diagram</a> version.
457 <LI> <a href= "Doc1.0/html.user/index.html">User Documentation"</a>
458 <LI> <a href= "Doc1.0/html.developper/index.html">Developper
460 <LI> Final check of the jpeg sub-library: all 'classical' jpeg
461 compressed Dicom files can be read<br>
462 <LI>All the previously gdcm-breaker images are now readable<br>
463 <LI> A huge number of memory leaks removed
464 <LI> Improvement of write process
468 <LI> A.P.I. breaking modifications (since previous version : <TT>0.6</TT>)
470 <LI> Use of <TT> namespace</TT> : all the methods formerly named
471 <TT>className::gdcmXxx()</TT> are now named <TT>className::Xxx()</TT>
472 <br> End user will have to call them as <TT>gdcm::className::Xxx() </TT>
473 <LI> a <TT>gdcm::Document</TT> is now specialized in :
475 <LI> <TT>gdcm::DicomDir</TT>
476 <LI> <TT>gdcm::File</TT>
478 <LI> a <TT>gdcm::DicomElementSet</TT> is composed of a set of
479 <TT>gdcm::DicomDocEntry</TT>
480 <LI> a <TT>gdcm::DicomDocEntry</TT> can be :
482 <LI> a <TT>gdcm::ContentEntry</TT>, specialized in :
484 <LI> <TT>gdcm::ValEntry</TT>
485 <LI> <TT>gdcm::BinEntry</TT> (no longer a specialization of
486 <TT>gdcm::ValEntry</TT>)
488 <LI> a <TT>gdcm::SeqEntry</TT>
490 <LI> Removal of useless accessors <TT>GetXxxByname</TT>, <TT>SetXxxByname</TT>
491 <LI> Renaming of accessors <TT>GetXxxByNumber</TT>, <TT>SetXxxByNumber</TT>
494 <LI> <TT>GetEntryByNumber
495
496 --> GetEntryValue</TT>
497 <LI> <TT>GetEntryLengthByNumber --> GetEntryLength</TT>
498 <LI> <TT>GetEntryOffsetByNumber --> GetEntryOffset</TT>
499 <LI> <TT>GetEntryVRByNumber
500 --> GetEntryVR</TT>
502 <LI> <TT>GetDocEntryByNumber
503 --> GetDocEntry</TT>
504 <LI> <TT>GetValEntryByNumber
505 --> GetValEntry</TT>
506 <LI> <TT>GetBinEntryByNumber
507 --> GetBinEntry</TT>
508 <LI> <TT>GetSeqEntryByNumber
509 --> GetSeqEntry</TT>
514 <!#######################################################################>
515 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
517 <A CLASS="anchor" NAME="NewsVersion0_6">
518 <B>Version 0.6 (June 8 2004)</B></A>
521 This version will be used by Insight Tool Kit
522 (<a href="http://www.itk.org">ITK</a> 2.0) at the beginning of 2005.<br>
523 It's not yet packaged ...<br><br>
524 <LI> <a href= "Doc0.6/html.user/index.html">User Documentation"</a>
525 <LI> <a href= "Doc0.6/html.developper/index.html">Developper Documentation"</a>
526 <LI> The new <TT>gdcmDocument</TT> class is a parent class of
527 <TT>gdcmHeader</TT> class and <TT>gdcmDicomDir</TT> class.
528 <LI> Massive modifications in the Class Diagram :
530 <LI> any dicom related file is a <TT>gdcmDocument</TT>
531 <LI> a <TT>gdcmDocument</TT> can be :
533 <LI> a <TT>gdcmHeader</TT>, if it contains pixel data
534 <LI> a <TT>gdcmDicomDir</TT>, if it contains only informations
535 on the files in a given directory
538 <LI> a <TT>gdcmDocument</TT> is_a <TT>gdcmElementSet</TT>,
539 composed of a set of <TT>gdcmEntry</TT> separated into :
541 <LI> <TT>gdcmValEntry</TT><br>
542 a specialization of <TT>gdcmValEntry</TT>, for 'non
543 <TT>std::string</TT> representable' values is
544 <TT>gdcmBinEntry</TT>
545 <LI> <TT>gdcmSeqEntry</TT> (VR = <TT>SQ</TT>, i.e Dicom Sequences)<br>
546 they are dealt as tree-like structures :<br>
547 - a <TT>gdcmSeqEntry</TT> is considered as a set
548 of <TT>gdcmSQItem</TT>,<br>
549 - a <TT>gdcmSQItem</TT> is_a <TT>gdcmElementSet</TT>, composed
550 of <TT>gdcmDocEntries</TT>, recursively <br>
553 <LI> Improvement of the jpeg sub-library: jpeg
554 compressed Dicom files (lossless and lossy)
555 might be read (check-it out)
558 <!#######################################################################>
559 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
561 <A CLASS="anchor" NAME="NewsVersion0_4">
562 <B>Version 0.4 (February 6 2004)</B></A>
566 <LI> <a href="Doc0.4/uml-gdcmV0.4.pdf">gdcm 0.4 UML Class Diagram</a>.
567 <LI> <a href= "Doc0.4/html.user/index.html">User Documentation"</a>
568 <LI> <a href= "Doc0.4/html.developper/index.html">Developper Documentation </a>
570 <LI> Introduction of a jpeg sub-library: some very simple jpeg-lossy
571 compressed Dicom files might be working (check-it out).
572 <LI> And also, fewer memory leaks, cleaned-up stl usage (should work
573 with gcc-3.x), python disutil installer (see file setup.py)
574 supporting both Swig and vtk wrapping.
575 <LI> Introduction of a RLE (Run-Time Encoding) library
576 <LI> Color images (RGB or Palette Color) are dealt with
577 <LI> Confusing names <TT>gdcmPatient</TT>, <TT>gdcmStudy</TT>,
578 <TT>gdcmSerie</TT>, <TT>gdcmPatient</TT> changed to
579 <TT>gdcmDicomDirPatient</TT>, <TT>gdcmDicomDirStudy</TT>,
580 <TT>gdcmDicomDirSerie</TT>, <TT>gdcmDicomDirPatient</TT>
584 <!#######################################################################>
585 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
587 <A CLASS="anchor" NAME="NewsVersion0_3">
588 <B>Version 0.3 (July 8 2003)</B></A>
591 <LI> <TT>gdcmFile</TT> class now enables acces to the data
592 i.e. the image[s] content. Previously only parsing of the
593 Dicom header was available through usage of <TT>gdcmHeader</TT>
595 <LI> a <A HREF="http://public.kitware.com/VTK/">VTK</A> plugin
596 of gdcm is now available through the <TT>vtkGdcmReader</TT>
597 vtk class (see it as a vtk wrapper of gdcm), which enables
599 <LI> Loading of a single image,
600 <LI> Loading of a stack of images from multiple Dicom files,
601 <LI> this class is wrapped for vtkPython (by using native vtk
604 <LI> Introduction of a jpeg sub-library: lossless-jpeg
605 compressed Dicom files work.
606 <LI> <TT>vtkgdcmViewer</TT> allows easy displaying of single/multiframe
607 GreyLevel/RGB/PaletteColor images
610 <!#######################################################################>
611 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
613 <A CLASS="anchor" NAME="NewsVersion0_1">
614 <B>Version 0.1 (April 1 2003)</B></A>
616 <!#######################################################################>
617 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
619 <A CLASS="anchor" name="NewsVersion0_1">
620 <B>Version 0.0 (March 14 2003)</B></A>
622 <HR size="1"><ADDRESS style="align: right;"></ADRESS>