Using a segmentation interpolation on a static segmentation created from a 4D image the contour is not visible on a timestep t != 0 if the segmentation was created on t = 0. However, the segmentation is visible on all timesteps (which is fine since it's a static segmentation).
Also, the resulting interpolated segmentation is visible on all timesteps.
I also encountered a strange behavior sometimes, that a contour is visible on a timestep t != 0, if the interpolated slice was the selected slice on timestep t = 0 (yellow contour visible) and then the timestep was changed to t != 0. However, scrolling through the slices did not hide this contour and show other interpolation contours.
Also, this happens sometims only on t = 2, not on t = 1. Also, on t = 2 sometimes the manually segmented contour stays the same on all slices.
To reproduce:
- Load a 4D dataset (e.g. MITK-Data\3D+t-Heart)
- create a new static segmentation
- set interpolation to 2-Dimensional
Additionally, I encountered a crash, if a a segmentation is currently interpolated (yellow contour) on timestep t = 0 and while timestep t != 0 (only t = 2?) is selected, the user creates a new slice before or after the first or last segmented slice:
Exception thrown: read access violation. this was nullptr. in const mitk::AffineTransform3D *mitk::BaseGeometry::GetIndexToWorldTransform() const.
The same is basically true for 3-Dimensional interpolation.