+ - Add the methods
+ gdcm::Dict:AddDict(std::string fullPathPrivateDictionaryFileName)
+
and
+ gdcm::Dict::RemoveDict(std::string fullPathPrivateDictionaryFileName)
+
+ to allow user to choose the 'Private Dictionary' he wants to work with.
+
+ One can dream about a better API;
+ This one allow right now anybody to see very easyly if the use
+ of a given private dicom dictionary is of any help or not.
+
+ -
+ PrintFile has now a new command line argument manager option :
+ dict=fullPathNamePrivateDictionaryFile
+ to allow user to see with no extra coding what differences
+ makes the use or not of a private Dicom Dictionary.
+ e.g. : use it as follow
+ PrintFile filein=myGEdicomFile.dcm
+ dict=/user/userName/gdcm/Dicts/GEMS-Advance.dic
+
+ -
+ (Not a great one ...)
+ Stupid method names :
DicomDir::WriteDicomDir()
+ and DicomDir::AnonymizeDicomDir()
replaced by :
+ DicomDir::Write()
+ and DicomDir::Anonymize()
+
+ -
+ void Document::AddForceLoadElement(uint16_t group, uint16_t elem);
+
+ allows user to tell gdcm::Document Loader he wants
+ to force the loading of a given set of DocEntries,
+ even if their length exceeds the current
+ MAX_SIZE_LOAD_ELEMENT_VALUE.
+
+ -
+ Many users expect from vtkGdcmReader it 'orders' the images
+ (that's the job of gdcm::SerieHelper ...)
+ When user knows the files with same Serie UID
+ have same sizes, same 'pixel' type, same color convention, ...
+ the right way to proceed is as follow :
+
+ gdcm::SerieHelper *sh= new gdcm::SerieHelper();
+ // if user wants *not* to load some parts of the file headers
+ sh->SetLoadMode(loadMode);
+
+ // if user wants *not* to load some files
+ sh->AddRestriction(group, element, value, operator);
+ sh->AddRestriction( ...
+ sh->SetDirectory(directoryWithImages);
+
+ // if user *knows* how to order his files
+ sh->SetUserLessThanFunction(userSuppliedComparisonFunction);
+ // or/and
+ // if user wants to sort reverse order
+ sh->SetSortOrderToReverse();
+
+ // here, we suppose only the first 'Single SerieUID' Fileset is of interest
+ // Just iterate using sh->NextSingleSerieUIDFileSet()
+ // if you want to get all of them
+ gdcm::FileList *l = sh->GetFirstSingleSerieUIDFileSet();
+
+ // if user is doesn't trust too much the files with same Serie UID
+ if ( !sh->IsCoherent(l) )
+ return; // not same sizes, or not same 'pixel type' -> stop
+
+ sh->OrderFileList(l); // sort the list
+
+ vtkGdcmReader *reader = vtkGdcmReader::New();
+ // if user wants to modify pixel order (Mirror, TopDown, ...)
+ // he has to supply the function that does the job
+ // (a *very* simple example is given in vtkgdcmSerieViewer.cxx)
+ reader->SetUserFunction (userSuppliedFunction);
+
+ // to pass a 'Single SerieUID' Fileset as produced by gdcm::SerieHelper
+ reader->SetCoherentFileList(l);
+ reader->Update();
+
+ You can see a full example in vtk/vtkgdcmSerieViewer.cxx
+ e.g.
+
+ vtkgdcmSerieViewer dirname=Dentist mirror
+ vtkgdcmSerieViewer dirname=Dentist reverse
+ vtkgdcmSerieViewer dirname=Dentist reverse topdown
+
+
+
+ - vtkGdcmReader::SetUserFunction (userSuppliedFunction)
+ with :
+ void userSuppliedFunction(uint8_t *imageData, File *f);
+ allows user to reorganize the pixels of each image just after reading
+ it (to mirror, or topdown the image, for instance)
+ Note : uint8_t * doesn't mean it works only on 8 Bits images.
+
It's for prototyping. Feel free to cast it.
+
+ -
+ SerieHelper::SetUserLessThanFunction(userSuppliedComparisonFunction)
+
with :
+ bool userSuppliedComparisonFunction(File *, File *);
+ allows user -when he knows more about his files than gdcm does-
+ to give his own comparison function.
+ - SerieHelper::SetSortOrderToReverse allows user to ask
+ to sort the Files reverse order.
+
- SerieHelper::AddRestriction has now a new constructor
+ AddRestriction(group, element, value, operator);
+ allows user to exclude some files from the sorting, according to
+ any comparison operator
+ (GDCM_EQUAL, GDCM_DIFFERENT,
+ GDCM_GREATER, GDCM_GREATEROREQUAL,
+ GDCM_LESS, GDCM_LESSOREQUAL), not only on the
+ equality.
+
- AnonymizeNoLoad used with dirin=inputDirectoryName
anonymizes all the files within the given Directory.
@@ -166,9 +358,9 @@ Any contribution is welcome.
See vtkgdcmSerieViewer for an example.
- - Both vtkgdcmViewer and vtkgdcmViewer2
- are available to allow easy displaying of single/multiframe
- GreyLevel/RGB/PaletteColor images
+ - Both vtkgdcmViewer and vtkgdcmViewer2
+ are available to allow easy displaying of single/multiframe
+ GreyLevel/RGB/PaletteColor images
- DICOMDIR anonymiser (Load and Noload mode)
- Because the gdcm::DicomDir::Load() method may be used
@@ -197,15 +389,17 @@ Any contribution is welcome.
- 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)
or he doesn't
- want to deal with SeqEntry that belong to a Shadow group (every time it's
- possible)
- use :
-
- gdcm::File *f = new gdcm::File();
+ he doesn't want to deal with SeqEntry
+ (every time it's possible, i.e for 'true length' Sequences)
+ and/or he doesn't want to deal with Shadow groups
+ (every time it's possible i.e. when element 0x0000
+ exists for this Group)
+ or he doesn't want to deal with SeqEntry that belong to a
+ Shadow group (every time it's possible
+ -'true length' Sequence-)
+ use :
+
+ gdcm::File *f = new gdcm::File();
f->SetLoadMode(NO_SEQ); | depending on what
f->SetLoadMode(NO_SHADOW); | you want *not*
f->SetLoadMode(NO_SEQ | NO_SHADOW);| to load from the
@@ -218,23 +412,24 @@ Any contribution is welcome.
gdcm::File *f = new gdcm::File(fileName);
- User is now allowed to tell gdcm::DicomDir constructor
- he doesn't want to deal with SeqEntry
- 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)
or he doesn't
- want to deal with SeqEntry that belong to a Shadow group (every time it's
- possible)
when he parses all the Dicom files within a given
- directory
- use :
-
- gdcm::DicomDir *f = new gdcm::DicomDir();
+ he doesn't want to deal with SeqEntry
+ (every time it's possible, i.e for 'true length' Sequences)
+ and/or he doesn't want to deal with Shadow groups
+ (every time it's possible i.e. when element 0x0000
+ exists for this Group)
+ or he doesn't want to deal with SeqEntry that belong to a
+ Shadow group (every time it's possible
+ -'true length' Sequence-)
+ when he parses all the Dicom files within a given directory.
+ use :
+
+ gdcm::DicomDir *f = new gdcm::DicomDir();
f->SetLoadMode(NO_SEQ); | depending on what
f->SetLoadMode(NO_SHADOW); | you want *not*
f->SetLoadMode(NO_SEQ | NO_SHADOW);| to load from the files
f->SetLoadMode(NO_SHADOWSEQ); | within the root directory
- f->SetDirectoryName(rootDirectoryName);
- f->Load( );
+ f->SetDirectoryName(rootDirectoryName);
+ f->Load( );
Don't use any longer old deprecated style:
@@ -244,13 +439,16 @@ Any contribution is welcome.
- Bug fixes
+ - No more trouble when the 'endianess' switches within Sequences.
+
- No more trouble with 'no length Sequences' belonging to a
+ Shadow Group when they are 'Implicit VR'.
- 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)
+ 'manually' the Meta Elements group (0x0002)
- 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
@@ -261,15 +459,12 @@ Any contribution is welcome.
- A.P.I. breaking modifications (since previous version : 1.0)
- NEVER more API breaking modifications !!!
-
+
- 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 ...
+