Down prioritized it, because survey indicated currently low relevance.

Down prioritized it, because survey indicated currently low relevance.

@floca I just tested it with my latest changes and the issue still persists. The connection to interpolation seems to be that the SegmentationInterpolationController is still holding a reference to the image and is notified about a modification. When changing the segmentation volume to the new segmentation eventually the ImageTimeSelector crashes when trying to clone an ImageDataItem that already seems to be null (this is 0x00000000). Here's a part of the call stack:

Oh, ok. Did not know that. I will postpone it then.

@kleina Just as a remark. I would postpone this task a bit, as we have enough other things to do and @kislinsk is currently working on interpolation and this might have also impact on this tasks.

I know that there is a problem with Windows / OpenGL using MITK remotely. I just had never seen this particular error-message given in the description. I will ask about the latest release and an updated driver, thanks!

• Does the problem also occure with the current release?
• It is a known problem that Windows (OpenGL problem) does not work (well) remote with MITK. The best way is installing the right drivers (see https://phabricator.mitk.org/T26427#224676)

I was not able to reproduce this bug on Windows with the v2021.02 release as well as the current develop branch

Is this an issue we need to address? Did anyone else experience this behavior?

I was able to reproduce the bug for all morphological operations (Dilation, Erosion, ...) and also in all orientations (axial, coronal, sagittal). Other segmentation utilities all work without problem.

Does it only crash with erosion or also with other utilities?

This issue should be postponed until T28523: Evaluate MITK segmentation survey (to now the new priority) is done.

This issue should be postponed until T28523: Evaluate MITK segmentation survey (to now the new priority) and T27437: Migrate MITK to use ITK 5.x (check for performance improvments due to refactored ITK) is done.

@floca I could only find two tasks mentioned here that are not closed, T27872 and T27684, but they are unrelated to the task description. Can this task be closed?

I am not sure what is exactly done here to reproduce. To get any help page I have to click on a plugin anyway. How would I provoke a blank page?
When I use F1 while the Standard Display is activated I get a blank page for the Standard Display. If that's what is meant than we need to reconsider how to display this specific help page: There is a description of the "four window view" inside src\Plugins\org.mitk.gui.qt.ext\documentation\UserManual\MITKUserManual.dox but we can not move it to the stdmultiwidgeteditor-plugin as it contains more information about the workbench, not only about the standard display.

@kleesiek Sorry. Just saw that it dropped of the radar. In the meantime the new release installer is out. Could you test it with the current workbench release? Thanks.

1. I want to use a plugin, how do I activate it?

@gaoh thanks for pointing there, I will close this one as a duplicate

T28207 describes how to test it without the wDB. When searching for DICOM query retrieve there are already different tasks open with all similar problems

Done - 1.2.4 is out: https://github.com/QIICR/dcmqi/releases/tag/v1.2.4

@fedorov That would be great. Thank you very much!

I am planning to make a patch release soon. Let me know if you want me to update you when that is done, so you can update the release used by MITK.

Hi there! 🙂

Hi there! 🙂