Wed, May 11
Deleted branch from rMITK MITK: bugfix/T27711-rename-image-selection-label.
Nov 17 2021
Nov 10 2021
Nov 9 2021
Deleted branch from rMITK MITK: release/T28802-MITK-v2021.10.
Deleted branch from rMITK MITK: release/T28802-2021-Week-45.
Nov 3 2021
I lower the priority since the exception is caught and it results in an error message instead of a crash. It's also an academic edge case, since it hardly makes any sense in a real world scenario to convert an actual image with more than 65000 different pixel values into a segmentation. Converting binary images or segmentation-like images works as expected.
Nov 2 2021
The problem is fixed by the diff. One can argue that the current solution for the histogramm widget (hide if timestep has no statistic) is not ideal from the UX perspective (very flickery).
But I think that is another problem. The question should be, why are no statistics container produced for empty masks? wouldn't make it more sense to produce a also for such time step a statistic, even if it is very trival as no pixel are evaluated.
Oct 30 2021
The description of the actual but swallowed exception is "Prohibited image access: the requested image part is already in use and cannot be requested recursively!" thrown indirectly from line 315 in mitkLabelSetImage.cpp: AccessFixedDimensionByItk_n(), which eventually calls ImageToItkImage() in mitkImageToItk.h:132. There, the Update() call of the ImageToItk class throws the exception mentioned above,
Oct 29 2021
Was also meantioned several times be testers this week.
Is this related / the same (because the second label is automatically selected and then the second layer has no second label)? T28131: [MultiLabel Segmentation] 3D Threshold tool does not work with multiple labels / layers
In the same line of reasoning (see discussion above). We could also remove the label name dialoge, when you add a new layer, couldn't we. In the current tests there was a remark, that when adding a new layer, you first are queried if you realy want to make a new layer and then you are asked for the label name...
Just a ping because it was triggered by a checklist for the upcoming release.
Oct 28 2021
@isensee What exactly does not work?
- Are you not able to load the data / ML nodes in the utilities selection widgets? That is a known bug and is addressed here: T28135
- Are you not able to work with multiple labels at all? This is also a known problem, since the MultiLabel Utilities View was never correctly implemented for working with multiple labels.
Maybe @s349i can also say something to this: Did you test the Utilities with segmentation masks created by the "MultiLabel Segmentation View"?
Oct 27 2021
Deleted branch from rMITK MITK: bugfix/T28771-FixNegInfInSerializedGeometryProps.
Oct 25 2021
Oct 22 2021
Oct 21 2021
May be I do not understand the problem right. But the described behavior sounds correct to me. Flood fill should stop on another (not the label you clicked on (including background) label boundary. The only thing you could discuss is wether it is important if another label is locked or not.