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>.<br>
107 (Well... Maybe it's up to the application to deal with it, not to
109 <LI> Allow manual adjunction / automatic recognition (pfff!...)
110 of the private <TT>Dicom Dictionary</TT>
111 to be used to parse <TT>Shadow groups</TT> against.
112 <LI> User friendly way of anonymizing image when Patient's name is
113 carved in the Pixels :-(
116 <!#######################################################################>
117 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
119 <A CLASS="anchor" NAME="NewsCurrentVersion">
120 <B>Current Version (CVS)</B></A>
125 <LI> <A HREF="News.html#missing">Missing Features</a>
129 <a href="uml-gdcm.pdf">gdcm UML Class Diagram</a> current version.
130 <LI> <a href= "Doc1.2/html.user/index.html">User Documentation</a>
131 <LI> <a href= "Doc1.2/html.developper/index.html">Developper
135 <LI> Stupid difference between <TT>gdcm::ValEntry</TT>
136 and <TT>gdcm::BinEntry</TT> removed. <br>
137 Only <TT>gdcm::DataEntry</TT> exist, now.
138 Should have been considered as a 'Bug Fix'.<br>
139 Actually, it's an API breaking modification ...
140 <LI> SerieHelper : <br>
141 Add some methods, to split a 'SingleSerieUID' Fileset into
142 'Extra Coherent' FileSets. <br>
143 They return a std::map of 'Filesets' (actually : std::vector
145 The key is the 'Orientation', the 'Position'
146 or the value of a user choosen 'Tag' <br>
147 - <TT>XCoherentFileSetmap SplitOnOrientation(FileList *fileSet);
149 - <TT>XCoherentFileSetmap SplitOnPosition(FileList *fileSet);
151 - <TT>XCoherentFileSetmap SplitOnTagValue(FileList *fileSet,
152 uint16_t group, uint16_t element);
154 These methods must be called by user, depending on what he wants
155 to do, at application time.- *he* only knows what his Series
157 <LI> To avoid memory leaks and seg faults the user intended classes
158 use now a Reference Counter.<br>
160 <LI> <TT>new()</TT> and <TT>delete()</TT> are replaced by
161 <TT>New()</TT> and <TT>Delete()</TT>
162 <LI> <TT>Register()</TT> and <TT>Unregister()</TT> methods are
168 <LI> API breaking modifications (since previous version)
170 <LI> Stupid difference between <TT>gdcm::ValEntry</TT>
171 and <TT>gdcm::BinEntry</TT> removed. <br>
172 Only <TT>gdcm::DataEntry</TT> exist, now. <br>
179 <LI> Implicit VR - Big Endian (G.E Private) Transfert Syntax 16 Bits
180 images are now read correctly.
181 <LI> File::GetZOrigin() returns accurate result in any case.
188 <LI> Use of <TT>Implicit Value Representation</TT> writting mode may
189 causes troubles, when there are some <TT>SQ</TT> belonging to a
190 <TT>Shadow Group</TT>. <br>
191 Better you use <TT>Explicit Value Representation</TT> writting mode ...
192 <LI> Troubles on 'Big endian' processors (i.e. Apple/Motorola, SunSparc
193 ...) when writting 16 Bits images.
194 <LI> Troubles on 64-bits processors.
204 <!#######################################################################>
205 <A CLASS="anchor" NAME="NewsPreviousVersions">
206 <!#######################################################################>
208 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
210 <A CLASS="anchor" NAME="NewsVersion1_1">
211 <B>Version 1.1 (September 14 2005)</B></A>
216 <a href="Doc1.0/uml-gdcmV1.0.pdf">gdcm 1.1 UML Class Diagram</a> version.
217 <LI> <a href= "Doc1.0/html.user/index.html">User Documentation</a>
218 <LI> <a href= "Doc1.0/html.developper/index.html">Developper
223 <TT>gdcm::Dict:AddDict(std::string fullPathPrivateDictionaryFileName)</TT>
225 <TT>gdcm::Dict::RemoveDict(std::string fullPathPrivateDictionaryFileName)</TT>
227 to allow user to choose the 'Private Dictionary' he wants to work with.
229 One can dream about a better API;<br>
230 This one allow right now anybody to see very easyly if the use
231 of a given private dicom dictionary is of any help or not.
234 <TT>PrintFile</TT> has now a new command line argument manager option :<br>
235 <TT>dict=fullPathNamePrivateDictionaryFile</TT><br>
236 to allow user to see with no extra coding what differences
237 makes the use or not of a private Dicom Dictionary.<br>
238 e.g. : use it as follow <br>
239 <TT>PrintFile filein=myGEdicomFile.dcm
240 dict=/user/userName/gdcm/Dicts/GEMS-Advance.dic</TT>
243 (Not a great one ...)
244 Stupid method names : <br><TT>DicomDir::WriteDicomDir()</TT>
245 and <TT>DicomDir::AnonymizeDicomDir()</TT> <br>replaced by : <br>
246 <TT>DicomDir::Write()</TT>
247 and <TT>DicomDir::Anonymize()</TT>
250 void Document::AddForceLoadElement(uint16_t group, uint16_t elem);
252 allows user to tell <TT>gdcm::Document</TT> Loader he wants
253 to force the loading of a given set of <TT>DocEntries</TT>,
254 even if their length exceeds the current
255 <TT>MAX_SIZE_LOAD_ELEMENT_VALUE</TT>.
258 Many users expect from <TT>vtkGdcmReader</TT> it 'orders' the images
259 (that's the job of <TT>gdcm::SerieHelper</TT> ...)<br>
260 When user <b>knows</b> the files with same Serie UID
261 have same sizes, same 'pixel' type, same color convention, ...
262 the right way to proceed is as follow :
264 gdcm::SerieHelper *sh= new gdcm::SerieHelper();
265 // if user wants *not* to load some parts of the file headers
266 sh->SetLoadMode(loadMode);
268 // if user wants *not* to load some files
269 sh->AddRestriction(group, element, value, operator);
270 sh->AddRestriction( ...
271 sh->SetDirectory(directoryWithImages);
273 // if user *knows* how to order his files
274 sh->SetUserLessThanFunction(userSuppliedComparisonFunction);
276 // if user wants to sort reverse order
277 sh->SetSortOrderToReverse();
279 // here, we suppose only the first 'Single SerieUID' Fileset is of interest
280 // Just iterate using sh->NextSingleSerieUIDFileSet()
281 // if you want to get all of them
282 gdcm::FileList *l = sh->GetFirstSingleSerieUIDFileSet();
284 // if user is doesn't trust too much the files with same Serie UID
285 if ( !sh->IsCoherent(l) )
286 return; // not same sizes, or not same 'pixel type' -> stop
288 sh->OrderFileList(l); // sort the list
290 vtkGdcmReader *reader = vtkGdcmReader::New();
291 // if user wants to modify pixel order (Mirror, TopDown, ...)
292 // he has to supply the function that does the job
293 // (a *very* simple example is given in vtkgdcmSerieViewer.cxx)
294 reader->SetUserFunction (userSuppliedFunction);
296 // to pass a 'Single SerieUID' Fileset as produced by gdcm::SerieHelper
297 reader->SetCoherentFileList(l);
300 You can see a full example in <TT>vtk/vtkgdcmSerieViewer.cxx</TT><br>
303 <TT>vtkgdcmSerieViewer dirname=Dentist mirror</TT><br>
304 <TT>vtkgdcmSerieViewer dirname=Dentist reverse</TT><br>
305 <TT>vtkgdcmSerieViewer dirname=Dentist reverse topdown</TT><br>
309 <LI> <TT>vtkGdcmReader::SetUserFunction (userSuppliedFunction)</TT><br>
311 <TT>void userSuppliedFunction(uint8_t *imageData, File *f);</TT><br>
312 allows user to reorganize the pixels of each image just after reading
313 it (to mirror, or topdown the image, for instance)<br>
314 Note : <TT>uint8_t *</TT> doesn't mean it works only on 8 Bits images.
315 <br> It's for prototyping. Feel free to cast it.
318 SerieHelper::SetUserLessThanFunction(userSuppliedComparisonFunction)
319 </TT><br> with : <br>
320 <TT>bool userSuppliedComparisonFunction(File *, File *);</TT><br>
321 allows user -when he knows more about his files than gdcm does-
322 to give his own comparison function.
323 <LI> <TT>SerieHelper::SetSortOrderToReverse</TT> allows user to ask
324 to sort the Files reverse order.
325 <LI> <TT>SerieHelper::AddRestriction</TT> has now a new constructor<br>
326 <TT>AddRestriction(group, element, value, operator);</TT><br>
327 allows user to exclude some files from the sorting, according to
328 any comparison operator <br>
329 (<TT>GDCM_EQUAL</TT>, <TT>GDCM_DIFFERENT</TT>,
330 <TT>GDCM_GREATER</TT>, <TT>GDCM_GREATEROREQUAL</TT>,
331 <TT>GDCM_LESS</TT>, <TT>GDCM_LESSOREQUAL</TT>), not only on the
334 <LI> <TT>AnonymizeNoLoad</TT> used with <TT>dirin=inputDirectoryName</TT>
335 anonymizes all the files within the given Directory.
337 User may also choose extra elements he wants to rub out: <br>
338 <TT>rubout=listOfElementsToRubOut</TT><br>
339 with <tt>listOfElementsToRubOut : group1-elem1,group2-elem2,
340 ...</TT> (in hexa, no space within the list )
342 <LI> <TT>gdcm::SerieHelper()</TT> has a new method
343 <TT>void AddGdcmFile(File *header)</TT>, that allows aware user to
344 create a '<TT>FileList</TT>' (actually a
345 <TT>std::vector< File* > </TT>).<br>
346 The <TT>FileList</TT> created this way will be the
347 'first one' in the <TT>gdcm::FileHelper()</TT> (retrieve it with
348 <TT>FileList *GetFirstCoherentFileList()</TT> ).<br>
349 It may be sorted using <TT>OrderFileList</TT>.<br>
350 No 'coherence check' will be performed on this <TT>FileList</TT>
352 It may be passed to a <TT>vtkGdcmReader</TT>
353 (to avoid parsing twice the files)
355 <LI> <TT>vtkGdcmReader</TT> can now get the result of
356 <TT>gdcm::SerieHelper</TT> (to avoid parsing twice the files)<br>
357 Proceed as follow :<br>
359 gdcmSerieHelper *sh = new gdcmSerieHelper();
360 sh->SetDirectory(myImageDirectory, true);
361 gdcmFileList *l = s->GetFirstCoherentFileList();
364 vtkGdcmReader *gr = new vtkGdcmReader();
365 gr->SetCoherentFileList(l);
368 This works with a directory that contains only one '<TT>Serie</TT>'
369 (same <TT>Serie UID</TT> for all the images).<br>
370 If it contains more than one <TT>Serie</TT>, you'll have to loop
371 on the Series, using <TT>GetNextCoherentFileList()</TT>;<br>
372 It will be up to the user to delete the <TT>gdcm::File</TT>.
374 See <TT>vtkgdcmSerieViewer</TT> for an example.
376 <LI> Both <TT>vtkgdcmViewer</TT> and <TT>vtkgdcmViewer2</TT>
377 are available to allow easy displaying of single/multiframe
378 GreyLevel/RGB/PaletteColor images<br><br>
379 <LI> <TT>DICOMDIR</TT> anonymiser (<TT>Load</TT> and <TT>Noload</TT> mode)
381 <LI> Because the <TT>gdcm::DicomDir::Load()</TT> method may be used
382 either for loading an already made <TT>DICOMDIR</TT> file or for
383 parsing all the dicom files with a given root directory we
384 syntaxically separated the operations: <br>
385 For loading an already made <TT>DICOMDIR</TT> file, use : <br>
387 gdcm::DicomDir *d = new gdcm::DicomDir();
388 d->SetFileName(fileName);
392 For parsing all the dicom files within a given root directory, use :<br>
394 gdcm::DicomDir *d = new gdcm::DicomDir();
395 d->SetDirectoryName(dirName);
399 <b>Don't</b> use any longer old deprecated style: <br>
401 gdcm::DicomDir *d = new gdcm::DicomDir();<br>
402 d->SetParseDir(true); // </TT>or <TT>d->SetParseDir(false);<br>
403 d->Load( fileName );<br>
406 <LI> User is now allowed to tell <TT>gdcm::Document</TT> constructor
407 he doesn't want to deal with <TT>SeqEntry</TT>
408 (every time it's possible, i.e for 'true length' Sequences) <br>
409 and/or he doesn't want to deal with <TT>Shadow groups</TT>
410 (every time it's possible i.e. when element <TT>0x0000</TT>
411 exists for this Group) <br>
412 or he doesn't want to deal with <TT>SeqEntry</TT> that belong to a
413 <TT>Shadow group</TT> (every time it's possible
414 -'true length' Sequence-)<br>
417 gdcm::File *f = new gdcm::File();
418 f->SetLoadMode(NO_SEQ); | depending on what
419 f->SetLoadMode(NO_SHADOW); | you want *not*
420 f->SetLoadMode(NO_SEQ | NO_SHADOW);| to load from the
421 f->SetLoadMode(NO_SHADOWSEQ); | target file
422 f->SetFileName(fileName);
425 <b>Don't</b> use any longer old deprecated style: <br>
427 gdcm::File *f = new gdcm::File(fileName);</TT> <br>
429 <LI> User is now allowed to tell <TT>gdcm::DicomDir</TT> constructor
430 he doesn't want to deal with <TT>SeqEntry</TT>
431 (every time it's possible, i.e for 'true length' Sequences) <br>
432 and/or he doesn't want to deal with <TT>Shadow groups</TT>
433 (every time it's possible i.e. when element <TT>0x0000</TT>
434 exists for this Group) <br>
435 or he doesn't want to deal with <TT>SeqEntry</TT> that belong to a
436 <TT>Shadow group</TT> (every time it's possible
437 -'true length' Sequence-)<br>
438 when he parses all the Dicom files within a given directory.<br>
441 gdcm::DicomDir *f = new gdcm::DicomDir();
442 f->SetLoadMode(NO_SEQ); | depending on what
443 f->SetLoadMode(NO_SHADOW); | you want *not*
444 f->SetLoadMode(NO_SEQ | NO_SHADOW);| to load from the files
445 f->SetLoadMode(NO_SHADOWSEQ); | within the root directory
446 f->SetDirectoryName(rootDirectoryName);
449 <b>Don't</b> use any longer old deprecated style: <br>
451 gdcm::DicomDir *dcmdir = new gdcm::DicomDir(dirName, true);</TT><br>
457 <LI> No more trouble when the 'endianess' switches within Sequences.
458 <LI> No more trouble with 'no length Sequences' belonging to a
459 <TT>Shadow Group</TT> when they are 'Implicit VR'.
460 <LI> The difference between <TT>MONOCHROME1</TT> (low values = bright,
461 high values = dark) and <TT>MONOCHROME2</TT> (low values = dark,
462 high values = bright) is now taken into account.<br>
463 It's no longer up to the user to change the pixels value
464 <LI> Writing a 'True Dicom' image after reading an <TT>ACR-NEMA</TT> image
465 does not request any longer from the user to build up
466 'manually' the Meta Elements group (<TT>0x0002</TT>)
467 <LI> Old '24 Bits' <TT>ACR-NEMA</TT> are now correctly re-written
468 in <TT>DICOM V3</TT> mode.
469 <LI> Element <TT>0x0000</TT> of <TT>Shadow groups</TT> is always forced to be a
470 <TT>ValEntry</TT> and its <TT>VR</TT> is forced to <TT>UL</TT>
474 <LI> A.P.I. breaking modifications (since previous version : <TT>1.0</TT>)
476 <LI> NEVER more API breaking modifications !!!
489 <!#######################################################################>
490 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
492 <A CLASS="anchor" NAME="NewsVersion1_0">
493 <B>Version 1.0 (Feb 14 2005)</B></A>
499 <a href="Doc1.0/uml-gdcmV1.0.pdf">gdcm 1.0 UML Class Diagram</a> version.
500 <LI> <a href= "Doc1.0/html.user/index.html">User Documentation"</a>
501 <LI> <a href= "Doc1.0/html.developper/index.html">Developper
503 <LI> Final check of the jpeg sub-library: all 'classical' jpeg
504 compressed Dicom files can be read<br>
505 <LI>All the previously gdcm-breaker images are now readable<br>
506 <LI> A huge number of memory leaks removed
507 <LI> Improvement of write process
511 <LI> A.P.I. breaking modifications (since previous version : <TT>0.6</TT>)
513 <LI> Use of <TT> namespace</TT> : all the methods formerly named
514 <TT>className::gdcmXxx()</TT> are now named <TT>className::Xxx()</TT>
515 <br> End user will have to call them as <TT>gdcm::className::Xxx() </TT>
516 <LI> a <TT>gdcm::Document</TT> is now specialized in :
518 <LI> <TT>gdcm::DicomDir</TT>
519 <LI> <TT>gdcm::File</TT>
521 <LI> a <TT>gdcm::DicomElementSet</TT> is composed of a set of
522 <TT>gdcm::DicomDocEntry</TT>
523 <LI> a <TT>gdcm::DicomDocEntry</TT> can be :
525 <LI> a <TT>gdcm::ContentEntry</TT>, specialized in :
527 <LI> <TT>gdcm::ValEntry</TT>
528 <LI> <TT>gdcm::BinEntry</TT> (no longer a specialization of
529 <TT>gdcm::ValEntry</TT>)
531 <LI> a <TT>gdcm::SeqEntry</TT>
533 <LI> Removal of useless accessors <TT>GetXxxByname</TT>, <TT>SetXxxByname</TT>
534 <LI> Renaming of accessors <TT>GetXxxByNumber</TT>, <TT>SetXxxByNumber</TT>
537 <LI> <TT>GetEntryByNumber
538
539 --> GetEntryValue</TT>
540 <LI> <TT>GetEntryLengthByNumber --> GetEntryLength</TT>
541 <LI> <TT>GetEntryOffsetByNumber --> GetEntryOffset</TT>
542 <LI> <TT>GetEntryVRByNumber
543 --> GetEntryVR</TT>
545 <LI> <TT>GetDocEntryByNumber
546 --> GetDocEntry</TT>
547 <LI> <TT>GetValEntryByNumber
548 --> GetValEntry</TT>
549 <LI> <TT>GetBinEntryByNumber
550 --> GetBinEntry</TT>
551 <LI> <TT>GetSeqEntryByNumber
552 --> GetSeqEntry</TT>
557 <!#######################################################################>
558 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
560 <A CLASS="anchor" NAME="NewsVersion0_6">
561 <B>Version 0.6 (June 8 2004)</B></A>
564 This version will be used by Insight Tool Kit
565 (<a href="http://www.itk.org">ITK</a> 2.0) at the beginning of 2005.<br>
566 It's not yet packaged ...<br><br>
567 <LI> <a href= "Doc0.6/html.user/index.html">User Documentation"</a>
568 <LI> <a href= "Doc0.6/html.developper/index.html">Developper Documentation"</a>
569 <LI> The new <TT>gdcmDocument</TT> class is a parent class of
570 <TT>gdcmHeader</TT> class and <TT>gdcmDicomDir</TT> class.
571 <LI> Massive modifications in the Class Diagram :
573 <LI> any dicom related file is a <TT>gdcmDocument</TT>
574 <LI> a <TT>gdcmDocument</TT> can be :
576 <LI> a <TT>gdcmHeader</TT>, if it contains pixel data
577 <LI> a <TT>gdcmDicomDir</TT>, if it contains only informations
578 on the files in a given directory
581 <LI> a <TT>gdcmDocument</TT> is_a <TT>gdcmElementSet</TT>,
582 composed of a set of <TT>gdcmEntry</TT> separated into :
584 <LI> <TT>gdcmValEntry</TT><br>
585 a specialization of <TT>gdcmValEntry</TT>, for 'non
586 <TT>std::string</TT> representable' values is
587 <TT>gdcmBinEntry</TT>
588 <LI> <TT>gdcmSeqEntry</TT> (VR = <TT>SQ</TT>, i.e Dicom Sequences)<br>
589 they are dealt as tree-like structures :<br>
590 - a <TT>gdcmSeqEntry</TT> is considered as a set
591 of <TT>gdcmSQItem</TT>,<br>
592 - a <TT>gdcmSQItem</TT> is_a <TT>gdcmElementSet</TT>, composed
593 of <TT>gdcmDocEntries</TT>, recursively <br>
596 <LI> Improvement of the jpeg sub-library: jpeg
597 compressed Dicom files (lossless and lossy)
598 might be read (check-it out)
601 <!#######################################################################>
602 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
604 <A CLASS="anchor" NAME="NewsVersion0_4">
605 <B>Version 0.4 (February 6 2004)</B></A>
609 <LI> <a href="Doc0.4/uml-gdcmV0.4.pdf">gdcm 0.4 UML Class Diagram</a>.
610 <LI> <a href= "Doc0.4/html.user/index.html">User Documentation"</a>
611 <LI> <a href= "Doc0.4/html.developper/index.html">Developper Documentation </a>
613 <LI> Introduction of a jpeg sub-library: some very simple jpeg-lossy
614 compressed Dicom files might be working (check-it out).
615 <LI> And also, fewer memory leaks, cleaned-up stl usage (should work
616 with gcc-3.x), python disutil installer (see file setup.py)
617 supporting both Swig and vtk wrapping.
618 <LI> Introduction of a RLE (Run-Time Encoding) library
619 <LI> Color images (RGB or Palette Color) are dealt with
620 <LI> Confusing names <TT>gdcmPatient</TT>, <TT>gdcmStudy</TT>,
621 <TT>gdcmSerie</TT>, <TT>gdcmPatient</TT> changed to
622 <TT>gdcmDicomDirPatient</TT>, <TT>gdcmDicomDirStudy</TT>,
623 <TT>gdcmDicomDirSerie</TT>, <TT>gdcmDicomDirPatient</TT>
627 <!#######################################################################>
628 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
630 <A CLASS="anchor" NAME="NewsVersion0_3">
631 <B>Version 0.3 (July 8 2003)</B></A>
634 <LI> <TT>gdcmFile</TT> class now enables acces to the data
635 i.e. the image[s] content. Previously only parsing of the
636 Dicom header was available through usage of <TT>gdcmHeader</TT>
638 <LI> a <A HREF="http://public.kitware.com/VTK/">VTK</A> plugin
639 of gdcm is now available through the <TT>vtkGdcmReader</TT>
640 vtk class (see it as a vtk wrapper of gdcm), which enables
642 <LI> Loading of a single image,
643 <LI> Loading of a stack of images from multiple Dicom files,
644 <LI> this class is wrapped for vtkPython (by using native vtk
647 <LI> Introduction of a jpeg sub-library: lossless-jpeg
648 compressed Dicom files work.
649 <LI> <TT>vtkgdcmViewer</TT> allows easy displaying of single/multiframe
650 GreyLevel/RGB/PaletteColor images
653 <!#######################################################################>
654 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
656 <A CLASS="anchor" NAME="NewsVersion0_1">
657 <B>Version 0.1 (April 1 2003)</B></A>
659 <!#######################################################################>
660 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
662 <A CLASS="anchor" name="NewsVersion0_1">
663 <B>Version 0.0 (March 14 2003)</B></A>
665 <HR size="1"><ADDRESS style="align: right;"></ADRESS>