If you open a certain test file and apply an otsu segmentation operation, the result is neither added as a data node to the datamanager nor rendered in the rendering window.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Invalid | None | T13038 For at least one confirmed file, the otsu segmentation result is not added to the data manager. | ||
| Resolved | None | T10925 Make MITK compatible with ITK 4.0 | ||
| Resolved | None | T11856 ITKv4 compatibility: itk::OStringStream does not exist anymore | ||
| Invalid | None | T14759 ITK4 build fails during MITK-superbuild |
Event Timeline
Comment Actions
Actually, two different problems occur.
First, due to the big size of the WholeBody.pic.gz and itk v3.20 using a static container for histogram computation, an exception is thrown. This bug already has been fixed for some subsequent version, and multiple threshold otsu filtering works using itk v4. Thus, the first issue relates to T10925.
Second, converting the 2D image to an itk 3D image using mitk::CastToItkImage leads to an exception. This was solved by checking the dimensionality first and converting to an mitk 3D image if neccessary.
Comment Actions
This bug could not be fixed for release 2013-06. Setting target milestone to next release
Comment Actions
The bug is solved in the current mitk master. The OtsuAction is deprecated (T16018) and the fix from branch bug-13038-noOtsuSegmentationResult is already included in the redesigned Otsu3DTool.