@floca Is this something worth looking into before the refactoring is done? If we stick with LabelSetImages and the basic backend of the utilities, I don't see a reason for this to be postponed.

In T28135#225112, @kalali wrote:

@floca Is this something worth looking into before the refactoring is done?

I would say: no.

If we stick with LabelSetImages

Do we? I would like to get them away as soon as possble. (to be discussed in the MITK meeting)

In T28135, @kalali wrote:

MultiLabel Segmentation View creates segmentation masks that are non-binary, rendering most of the operations useless.

I stumbled upon this right in the beginning of the Checklist MultiLabel segmentation – Utilities. I created two segmentation masks with the ML segmentation view and they can't be added to the provided selection widgets of the Boolean Operations. This is unexpected and simply because the binary-property is not set for a LabelSetImage.

I see two simple solutions but I'm not sure of the side-effects:

• allow "non-binary" LabelSetImages in the Boolean Operations
• set the "binary"-property for LabelSetImage

The first seem to make more sense to me (however, there will probably a problem 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"?

Maybe @s349i can also say something to this: Did you test the Utilities with segmentation masks created by the "MultiLabel Segmentation View"?

I face the same problem masks created with the "Multilabel Segmentation View" can't be added to the "ML Seg. Utilities" boolean operations, but the ones created in the "Segmentation View" can.

In general with {D744} being landed the multilabel utilities do not exist anymore so this task is obsolete.
We could discuss how to handle multiple labels for the single segmentation utilities, though, but I opened a new task for this: T29369: [Segmentation Utilities] Handle / select different labels independently.