The issue is the following
The expected behavior would be to perform the region growing segmentation directly in 4D. In other words, the result should be different for every time steps, assuming different volume data.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | None | T13999 Incorrect RegionGrowing behavior on 4D data | ||
| Resolved | None | T16133 Provide 4D support for 3D interpolation | ||
| Duplicate | None | T16105 Segmentation plugin crashes when creating a segmentation for a 3D+t image |
I managed to make the region growing work in 4D with minor code modification.
I would like to discuss the possibility to add the fourth dimension to the MITK_ACCESSBYITK_DIMENSIONS CMake variable. This is required in order to process 4D data with 4D algorithms.
Another way around it to use the AccessFixedDimensionByItk* macros and pass the current image dimension but I find this solution restrictive and somewhat ugly in terms of code.
What do you guys think?
I pushed my branch on Github [1] if you want to see/test the 4D region growing. All the tests pass so far.
[1]: https://github.com/fmorency/MITK/tree/bug-13999-IncorrectRegionGrowingBehaviorOn4DData
Since there is already a fix provided by felix we should try to include it in the upcoming release.
Pushed bug-13999-IncorrectRegionGrowingBehaviorOn4DData
with a partial merge.
Some the PluginView has been deleted in the Segmentation Redesign,
when trying to adapt the changes to the new file, we run into the problem that implicitly the segmentation interpolation is used whcih does not work with 4D data.