DICOMGDCMScanner does not work correctly
Closed, WontfixPublic
Actions

Assigned To

None

Authored By

	floca
	May 12 2017, 2:56 PM

Description

It seems like the DICOMGDCMTagScanner is not working correctly (DICOMDatasetFinding::path is not set, leading to wrong property names).
Thus all current DICOMReader classes in default configuration does not work. If you use DICOMDCMTKTagScanner with the reader (like in the reader services) everythin works fine.

This was also a problem for the error reported in T22840.

Related Objects

Mentioned In: rMITK23709ebd15f0: "Workarround" to fix the problem documented in T22841.
rMITKeb0d3198df6a: "Workarround" to fix the problem documented in T22841.
rMITK26e5b0fb9781: "Workarround" to fix the problem documented in T22841.
Mentioned Here: T22840: RTDose is not correctly loaded and visualized

Event Timeline

floca created this task.May 12 2017, 2:56 PM

floca mentioned this in rMITK26e5b0fb9781: "Workarround" to fix the problem documented in T22841..May 12 2017, 3:00 PM

floca mentioned this in rMITKeb0d3198df6a: "Workarround" to fix the problem documented in T22841..May 12 2017, 3:34 PM

kislinsk triaged this task as Normal priority.May 30 2017, 8:17 AM

floca mentioned this in rMITK23709ebd15f0: "Workarround" to fix the problem documented in T22841..Oct 6 2017, 1:20 PM

Hi there! 🙂

This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. 🚑

Best wishes,
The MITK devs

floca reopened this task as Open.May 26 2020, 11:50 AM

kislinsk removed kislinsk as the assignee of this task.May 26 2020, 12:05 PM

kislinsk removed a subscriber: kislinsk.