| Plugin name | dynamic timestep =0 | dynamic timestep != 0 | static t=0 | static t =2 |
| Watershed | ??? 4 | ??? 4 | ||
| rMITK MITK | |||
| Restricted Differential Revision | rMITKd1cb157710f9 Workarround for T27703 to avoid problematic threshold values that | ||
| Restricted Differential Revision | rMITK22644d61abfd Fixed T27641 - Refactored watershed tool for correct handling of dynamic… | ||
| Restricted Differential Revision | rMITK3250199d314b Improve robustness of base class if derived classes cannot produce an ML… | ||
| Restricted Differential Revision | rMITKf8f833cb5916 Changed default settings for Watershed tool | ||
| Restricted Differential Revision | rMITK7a61414d4497 Improved UI sizes | ||
| Restricted Differential Revision | rMITK9df1d1b36b3a Ensured that preview nodes cannot be selected as segmentation input. | ||
| Restricted Differential Revision | rMITK2e6b9c514b32 Reworked watershed tool. | ||
| Restricted Differential Revision | rMITK4fb6097092e9 Refactor Otsu tool and GUI to use AutoMLSegmentationWithPreviewTool and… | ||
| Restricted Differential Revision | rMITK0793a56eac3d Added SimpleLabelSetListWidget | ||
| Restricted Differential Revision | rMITK490026873248 Added AutoMLSegmentationWithPreviewTool | ||
| Restricted Differential Revision | rMITKb22b6a152b41 Removed wrong tooltip hint | ||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | floca | T28118 Refactoring of SegTool2D | ||
| Resolved | floca | T27507 Check the current behavior of the segmentation tools according static and dynamic 4D segmentation | ||
| Resolved | floca | T27641 [Segmentation] Watershed does always generate a 3D static seg. Even if dynamic segmentation was generated. |
Test image: 3D+t Heart
If you perform a dynamic segmentation using the Watershed tool, it creates a new segmentation no matter if you created a dynamic segmentation before.
The dynamic segmentation stays 4D (which is correct) but the new '_Watershed' segmentation is 3D (bug).
The result is stored in that new segmentation not the dynamic one.
To not blow up the data manager with this, the _Watershed should not be created but instead the dynamic segmentation should be used. In the dynamic case, a 4D segmentation should be the result of the Watershed tool.