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-gdcmV1.2.pdf">gdcm UML Class Diagram</a> current version.
130 <LI> <a href= "DocCVS/html.user/index.html">User Documentation</a>
131 <LI> <a href= "DocCVS/html.developper/index.html">Developper
135 <LI> To <i>try to</i> make gdcm images PACS usable, user is now allowed to
136 gdcm what kind of image he wants to write, using : <br>
137 <TT>void FileHelper::SetContentType (ImageContentType c);</TT> <br>
138 Four different types are identify (probabely more will be added) :
141 1) user created ex nihilo his own image and wants to write it as a Dicom image.<br>
142 c : <TT>USER_OWN_IMAGE</TT>
144 2) user modified the pixels of an existing image, using mathematical operations.<br>
145 c : <TT>FILTERED_IMAGE</TT>
147 3) user created a new image, using existing images (eg MIP, MPR, cartography image)<br>
148 c : <TT>CREATED_IMAGE</TT>
150 4) user modified/added some tags *without processing* the pixels (anonymization, etc)<br>
151 c : <TT>UNMODIFIED_PIXELS_IMAGE</TT>
153 <LI> Stupid difference between <TT>gdcm::ValEntry</TT>
154 and <TT>gdcm::BinEntry</TT> removed. <br>
155 Only <TT>gdcm::DataEntry</TT> exist, now.
156 Should have been considered as a 'Bug Fix'.<br>
157 Actually, it's an API breaking modification ...
160 <TT>std::string const &DataEntry::GetString() const</TT><br>
161 returns as a string (when possible) the value of the DataEntry
163 <TT>void DataEntry::SetString(std::string const &value)</TT><br>
164 Sets the 'value' of a DataEntry, passed as a std::string
166 <TT>void DataEntry::SetBinArea( uint8_t *area, bool self ) </TT><br>
167 Sets the value (non string) of the current Dicom DataEntry
169 <TT>void DataEntry::CopyBinArea( uint8_t *area, uint32_t length )</TT><br>
170 Inserts the value (non string) into the current DataEntry
172 <TT>void DataEntry::SetValue(const uint32_t &id, const double
174 Inserts the elementary (non string) value into the current
175 (multivaluated) DataEntry, at the <TT>id></TT> position.
177 <TT>double DataEntry::GetValue(const uint32_t &id) const </TT><br>
178 returns, as a double one of the values (when entry is
179 multivaluated), identified by its index <TT>id</TT>.
182 <TT>DocEntrySet::GetEntryValue()</TT> replaced by
183 <TT>DocEntrySet::GetEntryString()</TT> <br>
184 <LI> SerieHelper : <br>
185 Add some methods, to split a 'SingleSerieUID' Fileset into
186 'Extra Coherent' FileSets. <br>
187 They return a std::map of 'Filesets' (actually : std::vector
189 The key is the 'Orientation', the 'Position'
190 or the value of a user choosen 'Tag' <br>
191 - <TT>XCoherentFileSetmap SplitOnOrientation(FileList *fileSet);
193 - <TT>XCoherentFileSetmap SplitOnPosition(FileList *fileSet);
195 - <TT>XCoherentFileSetmap SplitOnTagValue(FileList *fileSet,
196 uint16_t group, uint16_t element);
198 These methods must be called by user, depending on what he wants
199 to do, at application time.- *he* only knows what his Series
201 <LI> To avoid memory leaks and seg faults the user intended classes
202 use now a Reference Counter.<br>
204 <LI> <TT>new()</TT> and <TT>delete()</TT> are replaced by
205 <TT>New()</TT> and <TT>Delete()</TT>
206 <LI> <TT>Register()</TT> and <TT>Unregister()</TT> methods are
212 <LI> API breaking modifications (since previous version)
214 <LI> Stupid difference between <TT>gdcm::ValEntry</TT>
215 and <TT>gdcm::BinEntry</TT> removed. <br>
216 Only <TT>gdcm::DataEntry</TT> exist, now. <br>
223 <LI> Implicit VR - Big Endian (G.E Private) Transfert Syntax 16 Bits
224 images are now read correctly.
225 <LI> File::GetZOrigin() returns accurate result in any case.
232 <LI> Use of <TT>Implicit Value Representation</TT> writting mode may
233 causes troubles, when there are some <TT>SQ</TT> belonging to a
234 <TT>Shadow Group</TT>. <br>
235 Better you use <TT>Explicit Value Representation</TT> writting mode ...
236 <LI> Troubles on 'Big endian' processors (i.e. Apple/Motorola, SunSparc
237 ...) when writting 16 Bits images.
238 <LI> Troubles on 64-bits processors.
248 <!#######################################################################>
249 <A CLASS="anchor" NAME="NewsPreviousVersions">
250 <!#######################################################################>
252 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
254 <A CLASS="anchor" NAME="NewsVersion1_1">
255 <B>Version 1.1 (September 14 2005)</B></A>
260 <a href="Doc1.0/uml-gdcmV1.0.pdf">gdcm 1.1 UML Class Diagram</a> version.
261 <LI> <a href= "Doc1.0/html.user/index.html">User Documentation</a>
262 <LI> <a href= "Doc1.0/html.developper/index.html">Developper
267 <TT>gdcm::Dict:AddDict(std::string fullPathPrivateDictionaryFileName)</TT>
269 <TT>gdcm::Dict::RemoveDict(std::string fullPathPrivateDictionaryFileName)</TT>
271 to allow user to choose the 'Private Dictionary' he wants to work with.
273 One can dream about a better API;<br>
274 This one allow right now anybody to see very easyly if the use
275 of a given private dicom dictionary is of any help or not.
278 <TT>PrintFile</TT> has now a new command line argument manager option :<br>
279 <TT>dict=fullPathNamePrivateDictionaryFile</TT><br>
280 to allow user to see with no extra coding what differences
281 makes the use or not of a private Dicom Dictionary.<br>
282 e.g. : use it as follow <br>
283 <TT>PrintFile filein=myGEdicomFile.dcm
284 dict=/user/userName/gdcm/Dicts/GEMS-Advance.dic</TT>
287 (Not a great one ...)
288 Stupid method names : <br><TT>DicomDir::WriteDicomDir()</TT>
289 and <TT>DicomDir::AnonymizeDicomDir()</TT> <br>replaced by : <br>
290 <TT>DicomDir::Write()</TT>
291 and <TT>DicomDir::Anonymize()</TT>
294 void Document::AddForceLoadElement(uint16_t group, uint16_t elem);
296 allows user to tell <TT>gdcm::Document</TT> Loader he wants
297 to force the loading of a given set of <TT>DocEntries</TT>,
298 even if their length exceeds the current
299 <TT>MAX_SIZE_LOAD_ELEMENT_VALUE</TT>.
302 Many users expect from <TT>vtkGdcmReader</TT> it 'orders' the images
303 (that's the job of <TT>gdcm::SerieHelper</TT> ...)<br>
304 When user <b>knows</b> the files with same Serie UID
305 have same sizes, same 'pixel' type, same color convention, ...
306 the right way to proceed is as follow :
308 gdcm::SerieHelper *sh= new gdcm::SerieHelper();
309 // if user wants *not* to load some parts of the file headers
310 sh->SetLoadMode(loadMode);
312 // if user wants *not* to load some files
313 sh->AddRestriction(group, element, value, operator);
314 sh->AddRestriction( ...
315 sh->SetDirectory(directoryWithImages);
317 // if user *knows* how to order his files
318 sh->SetUserLessThanFunction(userSuppliedComparisonFunction);
320 // if user wants to sort reverse order
321 sh->SetSortOrderToReverse();
323 // here, we suppose only the first 'Single SerieUID' Fileset is of interest
324 // Just iterate using sh->NextSingleSerieUIDFileSet()
325 // if you want to get all of them
326 gdcm::FileList *l = sh->GetFirstSingleSerieUIDFileSet();
328 // if user is doesn't trust too much the files with same Serie UID
329 if ( !sh->IsCoherent(l) )
330 return; // not same sizes, or not same 'pixel type' -> stop
332 sh->OrderFileList(l); // sort the list
334 vtkGdcmReader *reader = vtkGdcmReader::New();
335 // if user wants to modify pixel order (Mirror, TopDown, ...)
336 // he has to supply the function that does the job
337 // (a *very* simple example is given in vtkgdcmSerieViewer.cxx)
338 reader->SetUserFunction (userSuppliedFunction);
340 // to pass a 'Single SerieUID' Fileset as produced by gdcm::SerieHelper
341 reader->SetCoherentFileList(l);
344 You can see a full example in <TT>vtk/vtkgdcmSerieViewer.cxx</TT><br>
347 <TT>vtkgdcmSerieViewer dirname=Dentist mirror</TT><br>
348 <TT>vtkgdcmSerieViewer dirname=Dentist reverse</TT><br>
349 <TT>vtkgdcmSerieViewer dirname=Dentist reverse topdown</TT><br>
353 <LI> <TT>vtkGdcmReader::SetUserFunction (userSuppliedFunction)</TT><br>
355 <TT>void userSuppliedFunction(uint8_t *imageData, File *f);</TT><br>
356 allows user to reorganize the pixels of each image just after reading
357 it (to mirror, or topdown the image, for instance)<br>
358 Note : <TT>uint8_t *</TT> doesn't mean it works only on 8 Bits images.
359 <br> It's for prototyping. Feel free to cast it.
362 SerieHelper::SetUserLessThanFunction(userSuppliedComparisonFunction)
363 </TT><br> with : <br>
364 <TT>bool userSuppliedComparisonFunction(File *, File *);</TT><br>
365 allows user -when he knows more about his files than gdcm does-
366 to give his own comparison function.
367 <LI> <TT>SerieHelper::SetSortOrderToReverse</TT> allows user to ask
368 to sort the Files reverse order.
369 <LI> <TT>SerieHelper::AddRestriction</TT> has now a new constructor<br>
370 <TT>AddRestriction(group, element, value, operator);</TT><br>
371 allows user to exclude some files from the sorting, according to
372 any comparison operator <br>
373 (<TT>GDCM_EQUAL</TT>, <TT>GDCM_DIFFERENT</TT>,
374 <TT>GDCM_GREATER</TT>, <TT>GDCM_GREATEROREQUAL</TT>,
375 <TT>GDCM_LESS</TT>, <TT>GDCM_LESSOREQUAL</TT>), not only on the
378 <LI> <TT>AnonymizeNoLoad</TT> used with <TT>dirin=inputDirectoryName</TT>
379 anonymizes all the files within the given Directory.
381 User may also choose extra elements he wants to rub out: <br>
382 <TT>rubout=listOfElementsToRubOut</TT><br>
383 with <tt>listOfElementsToRubOut : group1-elem1,group2-elem2,
384 ...</TT> (in hexa, no space within the list )
386 <LI> <TT>gdcm::SerieHelper()</TT> has a new method
387 <TT>void AddGdcmFile(File *header)</TT>, that allows aware user to
388 create a '<TT>FileList</TT>' (actually a
389 <TT>std::vector< File* > </TT>).<br>
390 The <TT>FileList</TT> created this way will be the
391 'first one' in the <TT>gdcm::FileHelper()</TT> (retrieve it with
392 <TT>FileList *GetFirstCoherentFileList()</TT> ).<br>
393 It may be sorted using <TT>OrderFileList</TT>.<br>
394 No 'coherence check' will be performed on this <TT>FileList</TT>
396 It may be passed to a <TT>vtkGdcmReader</TT>
397 (to avoid parsing twice the files)
399 <LI> <TT>vtkGdcmReader</TT> can now get the result of
400 <TT>gdcm::SerieHelper</TT> (to avoid parsing twice the files)<br>
401 Proceed as follow :<br>
403 gdcmSerieHelper *sh = new gdcmSerieHelper();
404 sh->SetDirectory(myImageDirectory, true);
405 gdcmFileList *l = s->GetFirstCoherentFileList();
408 vtkGdcmReader *gr = new vtkGdcmReader();
409 gr->SetCoherentFileList(l);
412 This works with a directory that contains only one '<TT>Serie</TT>'
413 (same <TT>Serie UID</TT> for all the images).<br>
414 If it contains more than one <TT>Serie</TT>, you'll have to loop
415 on the Series, using <TT>GetNextCoherentFileList()</TT>;<br>
416 It will be up to the user to delete the <TT>gdcm::File</TT>.
418 See <TT>vtkgdcmSerieViewer</TT> for an example.
420 <LI> Both <TT>vtkgdcmViewer</TT> and <TT>vtkgdcmViewer2</TT>
421 are available to allow easy displaying of single/multiframe
422 GreyLevel/RGB/PaletteColor images<br><br>
423 <LI> <TT>DICOMDIR</TT> anonymiser (<TT>Load</TT> and <TT>Noload</TT> mode)
425 <LI> Because the <TT>gdcm::DicomDir::Load()</TT> method may be used
426 either for loading an already made <TT>DICOMDIR</TT> file or for
427 parsing all the dicom files with a given root directory we
428 syntaxically separated the operations: <br>
429 For loading an already made <TT>DICOMDIR</TT> file, use : <br>
431 gdcm::DicomDir *d = new gdcm::DicomDir();
432 d->SetFileName(fileName);
436 For parsing all the dicom files within a given root directory, use :<br>
438 gdcm::DicomDir *d = new gdcm::DicomDir();
439 d->SetDirectoryName(dirName);
443 <b>Don't</b> use any longer old deprecated style: <br>
445 gdcm::DicomDir *d = new gdcm::DicomDir();<br>
446 d->SetParseDir(true); // </TT>or <TT>d->SetParseDir(false);<br>
447 d->Load( fileName );<br>
450 <LI> User is now allowed to tell <TT>gdcm::Document</TT> constructor
451 he doesn't want to deal with <TT>SeqEntry</TT>
452 (every time it's possible, i.e for 'true length' Sequences) <br>
453 and/or he doesn't want to deal with <TT>Shadow groups</TT>
454 (every time it's possible i.e. when element <TT>0x0000</TT>
455 exists for this Group) <br>
456 or he doesn't want to deal with <TT>SeqEntry</TT> that belong to a
457 <TT>Shadow group</TT> (every time it's possible
458 -'true length' Sequence-)<br>
461 gdcm::File *f = new gdcm::File();
462 f->SetLoadMode(NO_SEQ); | depending on what
463 f->SetLoadMode(NO_SHADOW); | you want *not*
464 f->SetLoadMode(NO_SEQ | NO_SHADOW);| to load from the
465 f->SetLoadMode(NO_SHADOWSEQ); | target file
466 f->SetFileName(fileName);
469 <b>Don't</b> use any longer old deprecated style: <br>
471 gdcm::File *f = new gdcm::File(fileName);</TT> <br>
473 <LI> User is now allowed to tell <TT>gdcm::DicomDir</TT> constructor
474 he doesn't want to deal with <TT>SeqEntry</TT>
475 (every time it's possible, i.e for 'true length' Sequences) <br>
476 and/or he doesn't want to deal with <TT>Shadow groups</TT>
477 (every time it's possible i.e. when element <TT>0x0000</TT>
478 exists for this Group) <br>
479 or he doesn't want to deal with <TT>SeqEntry</TT> that belong to a
480 <TT>Shadow group</TT> (every time it's possible
481 -'true length' Sequence-)<br>
482 when he parses all the Dicom files within a given directory.<br>
485 gdcm::DicomDir *f = new gdcm::DicomDir();
486 f->SetLoadMode(NO_SEQ); | depending on what
487 f->SetLoadMode(NO_SHADOW); | you want *not*
488 f->SetLoadMode(NO_SEQ | NO_SHADOW);| to load from the files
489 f->SetLoadMode(NO_SHADOWSEQ); | within the root directory
490 f->SetDirectoryName(rootDirectoryName);
493 <b>Don't</b> use any longer old deprecated style: <br>
495 gdcm::DicomDir *dcmdir = new gdcm::DicomDir(dirName, true);</TT><br>
501 <LI> No more trouble when the 'endianess' switches within Sequences.
502 <LI> No more trouble with 'no length Sequences' belonging to a
503 <TT>Shadow Group</TT> when they are 'Implicit VR'.
504 <LI> The difference between <TT>MONOCHROME1</TT> (low values = bright,
505 high values = dark) and <TT>MONOCHROME2</TT> (low values = dark,
506 high values = bright) is now taken into account.<br>
507 It's no longer up to the user to change the pixels value
508 <LI> Writing a 'True Dicom' image after reading an <TT>ACR-NEMA</TT> image
509 does not request any longer from the user to build up
510 'manually' the Meta Elements group (<TT>0x0002</TT>)
511 <LI> Old '24 Bits' <TT>ACR-NEMA</TT> are now correctly re-written
512 in <TT>DICOM V3</TT> mode.
513 <LI> Element <TT>0x0000</TT> of <TT>Shadow groups</TT> is always forced to be a
514 <TT>ValEntry</TT> and its <TT>VR</TT> is forced to <TT>UL</TT>
518 <LI> A.P.I. breaking modifications (since previous version : <TT>1.0</TT>)
520 <LI> NEVER more API breaking modifications !!!
533 <!#######################################################################>
534 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
536 <A CLASS="anchor" NAME="NewsVersion1_0">
537 <B>Version 1.0 (Feb 14 2005)</B></A>
543 <a href="Doc1.0/uml-gdcmV1.0.pdf">gdcm 1.0 UML Class Diagram</a> version.
544 <LI> <a href= "Doc1.0/html.user/index.html">User Documentation"</a>
545 <LI> <a href= "Doc1.0/html.developper/index.html">Developper
547 <LI> Final check of the jpeg sub-library: all 'classical' jpeg
548 compressed Dicom files can be read<br>
549 <LI>All the previously gdcm-breaker images are now readable<br>
550 <LI> A huge number of memory leaks removed
551 <LI> Improvement of write process
555 <LI> A.P.I. breaking modifications (since previous version : <TT>0.6</TT>)
557 <LI> Use of <TT> namespace</TT> : all the methods formerly named
558 <TT>className::gdcmXxx()</TT> are now named <TT>className::Xxx()</TT>
559 <br> End user will have to call them as <TT>gdcm::className::Xxx() </TT>
560 <LI> a <TT>gdcm::Document</TT> is now specialized in :
562 <LI> <TT>gdcm::DicomDir</TT>
563 <LI> <TT>gdcm::File</TT>
565 <LI> a <TT>gdcm::DicomElementSet</TT> is composed of a set of
566 <TT>gdcm::DicomDocEntry</TT>
567 <LI> a <TT>gdcm::DicomDocEntry</TT> can be :
569 <LI> a <TT>gdcm::ContentEntry</TT>, specialized in :
571 <LI> <TT>gdcm::ValEntry</TT>
572 <LI> <TT>gdcm::BinEntry</TT> (no longer a specialization of
573 <TT>gdcm::ValEntry</TT>)
575 <LI> a <TT>gdcm::SeqEntry</TT>
577 <LI> Removal of useless accessors <TT>GetXxxByname</TT>, <TT>SetXxxByname</TT>
578 <LI> Renaming of accessors <TT>GetXxxByNumber</TT>, <TT>SetXxxByNumber</TT>
581 <LI> <TT>GetEntryByNumber
582
583 --> GetEntryValue</TT>
584 <LI> <TT>GetEntryLengthByNumber --> GetEntryLength</TT>
585 <LI> <TT>GetEntryOffsetByNumber --> GetEntryOffset</TT>
586 <LI> <TT>GetEntryVRByNumber
587 --> GetEntryVR</TT>
589 <LI> <TT>GetDocEntryByNumber
590 --> GetDocEntry</TT>
591 <LI> <TT>GetValEntryByNumber
592 --> GetValEntry</TT>
593 <LI> <TT>GetBinEntryByNumber
594 --> GetBinEntry</TT>
595 <LI> <TT>GetSeqEntryByNumber
596 --> GetSeqEntry</TT>
601 <!#######################################################################>
602 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
604 <A CLASS="anchor" NAME="NewsVersion0_6">
605 <B>Version 0.6 (June 8 2004)</B></A>
608 This version will be used by Insight Tool Kit
609 (<a href="http://www.itk.org">ITK</a> 2.0) at the beginning of 2005.<br>
610 It's not yet packaged ...<br><br>
611 <LI> <a href= "Doc0.6/html.user/index.html">User Documentation"</a>
612 <LI> <a href= "Doc0.6/html.developper/index.html">Developper Documentation"</a>
613 <LI> The new <TT>gdcmDocument</TT> class is a parent class of
614 <TT>gdcmHeader</TT> class and <TT>gdcmDicomDir</TT> class.
615 <LI> Massive modifications in the Class Diagram :
617 <LI> any dicom related file is a <TT>gdcmDocument</TT>
618 <LI> a <TT>gdcmDocument</TT> can be :
620 <LI> a <TT>gdcmHeader</TT>, if it contains pixel data
621 <LI> a <TT>gdcmDicomDir</TT>, if it contains only informations
622 on the files in a given directory
625 <LI> a <TT>gdcmDocument</TT> is_a <TT>gdcmElementSet</TT>,
626 composed of a set of <TT>gdcmEntry</TT> separated into :
628 <LI> <TT>gdcmValEntry</TT><br>
629 a specialization of <TT>gdcmValEntry</TT>, for 'non
630 <TT>std::string</TT> representable' values is
631 <TT>gdcmBinEntry</TT>
632 <LI> <TT>gdcmSeqEntry</TT> (VR = <TT>SQ</TT>, i.e Dicom Sequences)<br>
633 they are dealt as tree-like structures :<br>
634 - a <TT>gdcmSeqEntry</TT> is considered as a set
635 of <TT>gdcmSQItem</TT>,<br>
636 - a <TT>gdcmSQItem</TT> is_a <TT>gdcmElementSet</TT>, composed
637 of <TT>gdcmDocEntries</TT>, recursively <br>
640 <LI> Improvement of the jpeg sub-library: jpeg
641 compressed Dicom files (lossless and lossy)
642 might be read (check-it out)
645 <!#######################################################################>
646 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
648 <A CLASS="anchor" NAME="NewsVersion0_4">
649 <B>Version 0.4 (February 6 2004)</B></A>
653 <LI> <a href="Doc0.4/uml-gdcmV0.4.pdf">gdcm 0.4 UML Class Diagram</a>.
654 <LI> <a href= "Doc0.4/html.user/index.html">User Documentation"</a>
655 <LI> <a href= "Doc0.4/html.developper/index.html">Developper Documentation </a>
657 <LI> Introduction of a jpeg sub-library: some very simple jpeg-lossy
658 compressed Dicom files might be working (check-it out).
659 <LI> And also, fewer memory leaks, cleaned-up stl usage (should work
660 with gcc-3.x), python disutil installer (see file setup.py)
661 supporting both Swig and vtk wrapping.
662 <LI> Introduction of a RLE (Run-Time Encoding) library
663 <LI> Color images (RGB or Palette Color) are dealt with
664 <LI> Confusing names <TT>gdcmPatient</TT>, <TT>gdcmStudy</TT>,
665 <TT>gdcmSerie</TT>, <TT>gdcmPatient</TT> changed to
666 <TT>gdcmDicomDirPatient</TT>, <TT>gdcmDicomDirStudy</TT>,
667 <TT>gdcmDicomDirSerie</TT>, <TT>gdcmDicomDirPatient</TT>
671 <!#######################################################################>
672 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
674 <A CLASS="anchor" NAME="NewsVersion0_3">
675 <B>Version 0.3 (July 8 2003)</B></A>
678 <LI> <TT>gdcmFile</TT> class now enables acces to the data
679 i.e. the image[s] content. Previously only parsing of the
680 Dicom header was available through usage of <TT>gdcmHeader</TT>
682 <LI> a <A HREF="http://public.kitware.com/VTK/">VTK</A> plugin
683 of gdcm is now available through the <TT>vtkGdcmReader</TT>
684 vtk class (see it as a vtk wrapper of gdcm), which enables
686 <LI> Loading of a single image,
687 <LI> Loading of a stack of images from multiple Dicom files,
688 <LI> this class is wrapped for vtkPython (by using native vtk
691 <LI> Introduction of a jpeg sub-library: lossless-jpeg
692 compressed Dicom files work.
693 <LI> <TT>vtkgdcmViewer</TT> allows easy displaying of single/multiframe
694 GreyLevel/RGB/PaletteColor images
697 <!#######################################################################>
698 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
700 <A CLASS="anchor" NAME="NewsVersion0_1">
701 <B>Version 0.1 (April 1 2003)</B></A>
703 <!#######################################################################>
704 <HR size="1"><ADDRESS style="align: right;"></ADDRESS>
706 <A CLASS="anchor" name="NewsVersion0_1">
707 <B>Version 0.0 (March 14 2003)</B></A>
709 <HR size="1"><ADDRESS style="align: right;"></ADRESS>