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 <[email protected]> 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.
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Kitware offers ITK Training Courses, for more information visit: http://kitware.com/products/protraining.php Please keep messages on-topic and check the ITK FAQ at: http://www.itk.org/Wiki/ITK_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/insight-developers
