Page MenuHomePhabricator

Morphological operators non operational.
Closed, ResolvedPublic

Description

Depending on the respective use-case, applying morphological operators to just created binary segmentations leads MITK to crash or to not apply any operations.

Event Timeline

Can be reproduced as followed:

  1. Open an image, e.g. pic3D.nrrd
  2. Create a new segmentation within the segmentation plug-in.

2a. Use the 2D-slice interpolation for manually creating a 3D segmentation.
3a. Apply the Dilation or Fill Hole Operator to the newly created segmentation -> Crash.

or

2b. Apply the Otsu segmentation tool creating e.g. 4 regions, select a region from the list and create the respective segmentation.
3b. Perform 3a. -> No changes to the original segmentation are observable.

Reason for the morphological operator on otsu segmentation fail is that within the produced otsu segmentation, in-region-voxels do not have value 1 (but 255). The segmentation produced from the respective preview image is a result of itk::BinaryThresholdImageFilter application. Output in-region-voxel value has been set to 1 now.

For the slice interpolation case, the crash occurs as the segmentation interpolation controller still observes changes on the segmentation after the segmentation view has been left. This can now be prevented by explicitly disabling the 2D slice interpolation ( according entries have been inserted in QmitkSlicesInterpolator::OnInterpolationMethodChanged() ). Nevertheless, automatically disabling slice interpolation on view change still has to be adressed.

New remote branch pushed: bug-16461-MorphologicalOperatorsNotFunctioning

New remote branch pushed: bug-16461-integrationBranch

[4aebeb]: Merge branch 'bug-16461-integrationBranch'

Merged commits:

2013-11-20 18:59:31 Tobias Norajitra [88123f]
Preview and segmentation output value for in-region-voxels set to 1. Added entries to QmitkSlicesInterpolator::OnInterpolationMethodChanged() in order to disable 2d slice interpolation in the proper cases.

This bug is relevant for the upcoming release

Current release is finished. Reseting target milestone...

Resetting release_fix flag for open bugs which are not yet triaged for the 2014.03 release.

The interpolation deactivation on view change is regarded secondary here. Apart from that, the issue is solved.