- User Since
- Aug 1 2016, 12:10 PM (205 w, 9 h)
Fri, Jul 3
|Plugin name||dynamic timestep =0||dynamic timestep != 0||static t=0||static t =2|
|Threshold||performs segmentation on all timesteps||performs segmentation on all timesteps||performs segmentation on timestep 0||performs segmentation on timestep 0|
|UL threshold||performs segmentation on all timesteps||performs segmentation on all timesteps||performs segmentation on timestep 0||performs segmentation on timestep 0|
|Otsu||performs static 3D seg on the selected timestep performs static 3D seg on the selected timestep > it only matters which time point is selected not on which it was created|
|Fast Marching||it doesn't matter on which timesteps the seeds are selected, they all account for initial image / performs segmentation only on the timestep selected, others are blank|
|Watershed||segmentation cannot be produced with US4DCyl / LinearModel / performs static 3D seg on the selected timestep||performs segmentation on timestep 0||performs segmentation on timestep 2 / it only matters which time point is selected not on which it was created|
|Picking||Creates a 3D segmentation with picked region and deletes all other segmentations (in all timesteps)|
Tue, Jun 30
Thu, Jun 25
But the 3d segmentation has only 1 timestep with duration = sum of durations of all 4D image timesteps, right?
Fri, Jun 19
The error described above results from the function add seed that currently takes 3D images only. It can be solved with using a timeselector to crop the current time step and set a 3D seed.
However, the task is related to the discussion on time points versus time steps and should be revised accordingly.
When the workbench is started from scratch it works.
Tue, Jun 16
I used a master that was three weeks old, I will double check on the current develop
Wed, Jun 10
- Works for dynamic (4D) segmentations
- Could not be reproduced for static segmentations since the workbench crashes during the creation of a static segmentation (related to T27476)
- Works for timestep 0
- Independent from segmentation tool so might be a problem of the selection concept not the segmentation
Mon, Jun 8
@gaoh: Can you tell what you mean by dynamic mask?
I will leave the task open since the handling in the respective class might need further refactoring to fully understand the behavior (as also mentioned by @kalali in the D279 review).
I remove the MITK2020 tag for now since the mentioned bug is resolved by the fix in D279.
Task T26596 is mentioned but does not correlate with the Topic asaik...maybe transposed digits in the task number?
May 26 2020
Apr 23 2020
Apr 22 2020
Apr 15 2020
The reason seems to be that a BoundingShape as such is 3D with an index of size=3 that does not equal the index array of the 4D image. I will test the fix for other images to make sure.
Pushed new branch T27067-ImageCropperCorrect4D.
This was also communicated to Siemens and only occured when loading their early stage clinical prototype data. Can not be reproduced with the newer data. The task can be closed for now.
Mar 27 2020
Mar 12 2020
As stated before, we encountered more examples that raised the unknown exception, so I don’t agree to lower the priority on that.
Mar 3 2020
The latest Release installer
Mar 2 2020
Feb 28 2020
Feb 14 2020
Feb 13 2020
Feb 12 2020
Feb 7 2020
Pushed new branch T27076-ChangeDesignerBuildFlagToDefault.
Jan 23 2020
Jan 22 2020
Jan 20 2020
Jan 10 2020
Jan 9 2020
Jan 8 2020
Nov 28 2019
Nov 22 2019
Pushed new branch T26840-MitkHomepageReorganization-TopLevel.