Change Details

In T28934 I describe a bug, where a missing Tag results in dcmqi results in an invalid saved segmentation. DCMQI writes an Error to the MITK log: > E: CodeValue (0008,0100) absent in CodeSequenceMacro (type 1) > E: Could not write item #0 in ProcedureCodeSequence: Invalid Value > FATAL ERROR: Writing of the SEG dataset failed! Error: Invalid Value. Please report the problem to the developers, ideally accompanied by a de-identified dataset allowing to reproduce the problem! But still in the MITK GUI, no exception is thrown, or error message is shown. So in this case in Kaapana the user terminates the MITK container (and therefore the logs) cannot be seen anymore, when realizing, that the created file is corrupted. So MITK should not create a corrupted dcm file and tell the user, that something went wrong in the GUI: Either throw an exception or print a message, that it did not work. Currently it is still showing: {F2498432}

In T28934 I describe a bug, where a missing Tag in dcmqi results in an invalid saved segmentation. DCMQI writes an Error to the MITK log: > E: CodeValue (0008,0100) absent in CodeSequenceMacro (type 1) > E: Could not write item #0 in ProcedureCodeSequence: Invalid Value > FATAL ERROR: Writing of the SEG dataset failed! Error: Invalid Value. Please report the problem to the developers, ideally accompanied by a de-identified dataset allowing to reproduce the problem! But still in the MITK GUI, neither an exception is thrown, nor an error message is shown. So in this case in Kaapana the user terminates the MITK container and therefore the logs cannot be seen anymore when realizing, that the created file is corrupted. So MITK should not create a corrupted dcm file and should tell the user, that something went wrong in the GUI: Either throw an exception or print a message, that it did not work. Currently it is still showing: {F2498432}

In T28934 I describe a bug, where a missing Tag results in dcmqi results in an invalid saved segmentation. DCMQI writes an Error to the MITK log: > E: CodeValue (0008,0100) absent in CodeSequenceMacro (type 1) > E: Could not write item #0 in ProcedureCodeSequence: Invalid Value > FATAL ERROR: Writing of the SEG dataset failed! Error: Invalid Value. Please report the problem to the developers, ideally accompanied by a de-identified dataset allowing to reproduce the problem! But still in the MITK GUI, no exception is thrown, or error messageneither an exception is shown.thrown, So in this case in Kaapana the user terminates the MITK container (and therefore the logs) cannot be seen anymore,nor an error message is shown. So in this case in Kaapana the user terminates the MITK container and therefore the logs cannot be seen anymore when realizing, that the created file is corrupted. So MITK should not create a corrupted dcm file and should tell the user, that something went wrong in the GUI: Either throw an exception or print a message, that it did not work. Currently it is still showing: {F2498432}