[ITK-dev] help itk::GDCMImageIO / itk::ExposeMetaData

[Bradley Lowekamp]

Kent,

A long time ago, when I was working on IO streaming, I had modified the ImageSeries reader to populate the metadata dictionary on the GenerateOutputInformation phase of the pipeline. This ended up getting called 2 or 3 times, and it caused a significant performance penalty with the GDCM meta-data that the Slicer folks loudly complained and it was fixed [ likely here 1].

I have doubts about your assumption that there are not significant computation expenses with metadata IO. However I am not quite certain if my experience is relavent to this issue. 

just an FYI,
Brad


[1] https://github.com/InsightSoftwareConsortium/ITK/commit/e92d78ee3b26069d3aeb6aa9f6460a46f20ec2de

On Sep 16, 2014, at 1:15 PM, Williams, Norman K <norman-k-williams at uiowa.edu> wrote:

>  the time spent in writing and reading the MetaDataDictionary is not going to have a significant computational cost, since it only happens when you read or write a DICOM file.  It’s not something done in the inner loop of a big computation.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/insight-developers/attachments/20140916/4d6763f5/attachment.html>