When loading Secondary Capture (SC) DICOM images, mitk::DicomSeriesReader will in many instances look for some tags that are not required for SC images.
Problematic tags are things like slice position, slice orientation, pixel spacing. All this information is actually NOT relevant if it is missing. For Secondary capture it should be safe to invent data for missing tags so that MITK can at least render such images (which sometimes contain scan protocol data or 3D reconstruction results).
Patch for this problem was already present, is now at
http://mitk.org/git/?p=MITK.git;a=commitdiff;h=0283e705b2d2f44baa8fa890470ebd0d5df537fc
From mail of Matt Clarkson:
In answer to your question on secondary capture, i think it would be
more wrong to load an image with wrong orientation, spacing and slice
thickness.Also, having looked at the 3D SPECT images.... these seem to have tag
0008,0060 (modality)=OT so the suggested code here:
https://github.com/maleike/MITK/commit/d1ab612fc78f93963062c97d7c4d4ac70e5b0876#L0L583would treat these SPECT images incorrectly.
So, as it stands, I think we still need a different solution for SPECT
and SecondaryCapture, and do not currently agree with this code:
https://github.com/maleike/MITK/commit/d1ab612fc78f93963062c97d7c4d4ac70e5b0876#L0L583
Maybe we can find a solution where an application can load such data but at least inform a user that distances might be broken. I'll think about this some more.