Change Details

The Canon images (stills; see sample data in super task T27554) cannot be read. The error message given is. "Invalid tag values when constructing tilt information from origin1 '', origin2 '', and orientation ''. Reason for the error in case of the example data: - The directory containes 2 files/images. - Both files have the same patient ID, study and series instance UID etc., so MITK IO assumes to be part of the same volume - As Both images have cover the same space in world geometry, MITK reader that support 3D+t are choosen as they assume that they can read it only one volume (other readers need obviously two volumes). - 3D+t reader faile in loading process as no meaning full tilt can be deduced (see error message above). Remark: It is unclear if the anonymization scheme or the data stored by the vendor itself let to the problem of same UIDs etc. May be the anonymization strategies should be checked as it leaves the data illformed. Possible mitigation strategies or solutions: # see remark above, should be checked (but not a MITK side solution). # Seperate the image in different directories before loading. # Select as reader "MITK DICOM Reader v2 (manual)" and choose any non 3D+t configuration # Offer a reader that only chooses from 3D configuations automatically # Rework reader infrastructure to also check the tilt validity when searching for optimal solution. Comments regarding solutions: 2: is already possible. 3: see 2 4: Another reader could swamp the selection even more. Adding it as option (e.g. "only static" to the "MITK DICOM Redar v2 (auto)" would cause the workbench to not automatically execute the reader any more as he has options. On the other hand the workbench does not execute DICOMs automatically anyway because we have already 4 different options available... 5: Problematic as we move even more computational stuff in the pure reader selection, which can slow the loading process down even further. Especially because it curently would be thrown away and done twice; 1st for the selection and then 2nd for the real reading.

The Canon images (stills; see sample data in super task T27554) cannot be read. The error message given is. "Invalid tag values when constructing tilt information from origin1 '', origin2 '', and orientation ''. Reason for the error in case of the example data: - The directory containes 2 files/images. - Both files have the same patient ID, study and series instance UID etc., so MITK IO assumes to be part of the same volume - As Both images have cover the same space in world geometry, MITK reader that support 3D+t are choosen as they assume that they can read it only one volume (other readers need obviously two volumes). - 3D+t reader faile in loading process as no meaning full tilt can be deduced (see error message above). Remark: It is unclear if the anonymization scheme or the data stored by the vendor itself let to the problem of same UIDs etc. May be the anonymization strategies should be checked as it leaves the data illformed. Possible mitigation strategies or solutions: # see remark above, should be checked (but not a MITK side solution). # Seperate the image in different directories before loading. # Select as reader "MITK DICOM Reader v2 (manual)" and choose any non 3D+t configuration # Offer a reader that only chooses from 3D configuations automatically # Rework reader infrastructure to also check the tilt validity when searching for optimal solution. # Rework reader infrastructure to make tilt invalidity also to a reason to seperate blocks. Comments regarding solutions: 2: is already possible. 3: see 2 4: Another reader could swamp the selection even more. Adding it as option (e.g. "only static" to the "MITK DICOM Redar v2 (auto)" would cause the workbench to not automatically execute the reader any more as he has options. On the other hand the workbench does not execute DICOMs automatically anyway because we have already 4 different options available... 5: Problematic as we move even more computational stuff in the pure reader selection, which can slow the loading process down even further. Especially because it curently would be thrown away and done twice; 1st for the selection and then 2nd for the real reading.

The Canon images (stills; see sample data in super task T27554) cannot be read. The error message given is. "Invalid tag values when constructing tilt information from origin1 '', origin2 '', and orientation ''. Reason for the error in case of the example data: - The directory containes 2 files/images. - Both files have the same patient ID, study and series instance UID etc., so MITK IO assumes to be part of the same volume - As Both images have cover the same space in world geometry, MITK reader that support 3D+t are choosen as they assume that they can read it only one volume (other readers need obviously two volumes). - 3D+t reader faile in loading process as no meaning full tilt can be deduced (see error message above). Remark: It is unclear if the anonymization scheme or the data stored by the vendor itself let to the problem of same UIDs etc. May be the anonymization strategies should be checked as it leaves the data illformed. Possible mitigation strategies or solutions: # see remark above, should be checked (but not a MITK side solution). # Seperate the image in different directories before loading. # Select as reader "MITK DICOM Reader v2 (manual)" and choose any non 3D+t configuration # Offer a reader that only chooses from 3D configuations automatically # Rework reader infrastructure to also check the tilt validity when searching for optimal solution. # Rework reader infrastructure to make tilt invalidity also to a reason to seperate blocks. Comments regarding solutions: 2: is already possible. 3: see 2 4: Another reader could swamp the selection even more. Adding it as option (e.g. "only static" to the "MITK DICOM Redar v2 (auto)" would cause the workbench to not automatically execute the reader any more as he has options. On the other hand the workbench does not execute DICOMs automatically anyway because we have already 4 different options available... 5: Problematic as we move even more computational stuff in the pure reader selection, which can slow the loading process down even further. Especially because it curently would be thrown away and done twice; 1st for the selection and then 2nd for the real reading.