• Works for dynamic (4D) segmentations but creates the same segmentation for all timesteps
• Could not be reproduced for static segmentations since the workbench crashes during the creation of a static segmentation (related to T27476)

Please check if problem still persists as soon as T27490 is merged into develop or directly with D329 (is open for review by the way ;)

In T25825#203881, @thomass wrote:

• Works for dynamic (4D) segmentations but creates the same segmentation for all timesteps
• Could not be reproduced for static segmentations since the workbench crashes during the creation of a static segmentation (related to T27476)

I am now able to create a static segmentation on a 4D image. Watershed creates the same segmentation for all timesteps (because the 3D segmentation is valid for each timestep).

But the 3d segmentation has only 1 timestep with duration = sum of durations of all 4D image timesteps, right?

Yes. I think this is more related to your other discussion in T26974: "What to do with a 3D segmentation of a 4D image."

In T25825#204469, @thomass wrote:

But the 3d segmentation has only 1 timestep with duration = sum of durations of all 4D image timesteps, right?

On should really seperate between bugfixes (e,g, crashes like the here mentioned) and the discussion "what does it mean to make a 3D segmentation on a 4D image" (which is more like a feature discussion).

So I would propose to focuse here on the crash and have anoter task with RequestForDiscussion on the other topic.