Both the 3-d region growing and 3-d picking tools were mentioned in the known issues section of the last release notes, because they do not yet support dynamic images/segmentations. The 3-d region growing tool is still deactivated for dynamic images (see T28499: Refactor/rewrite RegionGrowing3D tool) but the 3-d picking tool is not and crashes with an "image dimension (4) is not in (2)(3)" message.
Description
Description
Revisions and Commits
Revisions and Commits
| rMITK MITK | |||
| Restricted Differential Revision | rMITKe55a5d2f43c7 T28756 Fixed crash in PickingTool | ||
| Restricted Differential Revision | rMITK067d90b1ce54 Fixed crash in PickingTool | ||
Related Objects
Related Objects
- Mentioned In
- T28802: 2021 Week 45 (Early November)
- Mentioned Here
- T28499: Refactor/rewrite RegionGrowing3D tool
Event Timeline
Comment Actions
Found the problem. It is not a error in the picking tool.
It is in
void mitk::LabelSetImage::ClearBuffer()
Because AccessByItk (which is used there) by default only supports 2D and 3D. -> Exception when trying to reset dynamic LabelSetImages.
So far I see the following solutions:
- Add 4D as a CMake default (but would impact a lot of code...)
- Add in clear buffer a check if instance is 4D and if so explizitly call it for 4D (in other cases use AccessByItk as we did so far.
@kislinsk Do you see an other option? Which one would you choose?
Comment Actions
(1) is not a reasonable option, so (2) it is in my opinion. I didn't check the code but an alternative could be the typical iteration through time steps in case of dynamic data and call the templated function with 3 dimensions.