[Segmentation] 3D Threshold / UL Threshold does not use a timestep != 0 for static masks
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	kalali
	Jul 29 2020, 12:49 PM

Description

Currently the result of the 3D Threshold and 3D UL Threshold using a 4D image with a static mask (3D mask) is:

Plugin name	static t = 0	static t = 2
Theshold	performs segmentation on timestep 0	performs segmentation on timestep 0
UL Theshold	performs segmentation on timestep 0	performs segmentation on timestep 0

But the result of the 3D Threshold and 3D UL Threshold using a 4D image with a static mask (3D mask) should be:

Plugin name	static t = 0	static t = 2
Theshold	performs segmentation on timestep 0	performs segmentation on timestep 2
UL Theshold	performs segmentation on timestep 0	performs segmentation on timestep 2

Revisions and Commits

rMITK MITK
	Restricted Differential Revision	rMITK08619e4fc4b8 T27621/T27622 - Corrected threshold tools
	Restricted Differential Revision	rMITK5f96821de19f Fixed review remarks.
	Restricted Differential Revision	rMITKc03ca0616159 Handeled unused variables (gcc error)
	Restricted Differential Revision	rMITK4408a8ff26b0 Removed unnecessary call
	Restricted Differential Revision	rMITK703af31f270f Refactored threshold tools to remove redundant code
	Restricted Differential Revision	rMITK179b53dfa7bb Improved usablility of threshold tools
	Restricted Differential Revision	rMITKb9bfb2ec4e41 Corrected mitk::AutoSegmentationTool::GetTargetSegmentationNode() to use the…
	Restricted Differential Revision	rMITK13895dc2f6b7 first draft of threshold tool that behaves correctly time point aware now.
	Restricted Differential Revision	rMITK83f54f57a53c Add (event) support for current time point change to toolmanager

Related Objects
Search...

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	T27621 [Segmentation] 3D Threshold / UL Threshold does not use a timestep != 0 for static masks

Event Timeline

kalali triaged this task as High priority.Jul 29 2020, 12:49 PM

kalali created this task.

kalali moved this task from Backlog to Segmentation on the MITK (v2021.02) board.Jul 29 2020, 12:58 PM

• thomass mentioned this in T27615: [Segmentation] Threshold and UL threshold show unwanted behavior on static and dynamic segmentations.Jul 29 2020, 1:03 PM

kalali renamed this task from [Segmentation] 3D Threshold does not use a timestep != 0 for static masks to [Segmentation] 3D Threshold / UL Threshold does not use a timestep != 0 for static masks.Jul 29 2020, 1:49 PM

kalali updated the task description. (Show Details)

floca claimed this task.Jul 30 2020, 1:13 PM

floca added a revision: Restricted Differential Revision.Jul 31 2020, 1:19 PM

floca added a commit: rMITK83f54f57a53c: Add (event) support for current time point change to toolmanager.Aug 5 2020, 10:20 AM

floca added a commit: rMITK13895dc2f6b7: first draft of threshold tool that behaves correctly time point aware now..

floca added a commit: rMITKb9bfb2ec4e41: Corrected mitk::AutoSegmentationTool::GetTargetSegmentationNode() to use the….

floca added a commit: rMITK179b53dfa7bb: Improved usablility of threshold tools.

floca added a commit: rMITK703af31f270f: Refactored threshold tools to remove redundant code.

floca added a commit: rMITK4408a8ff26b0: Removed unnecessary call.

floca added a commit: rMITKc03ca0616159: Handeled unused variables (gcc error).

floca added a commit: rMITK5f96821de19f: Fixed review remarks..

floca added a commit: rMITK08619e4fc4b8: T27621/T27622 - Corrected threshold tools.