Can T14333: Improve mitk::UIDGenerator be closed?

After rethinking the problem, I have come to the conclusion that there is a simplier straight forward solution that does not need to wait for ITK v5 and maybe new features.

• 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)

1. Works for timestep 0
2. Independent from segmentation tool so might be a problem of the selection concept not the segmentation

2. The spacing of the record makes that sometimes plots are shown in the following page, the formatting and the spacing should be revised.

Pushed new branch T27472-FiberStatistics.

@floca OK, then I will work on the Pharmacokinetics Plugins.

@kompan I have some fixes for the model fit inspector view already in my stash that where done while working on other stuff. So if you do the task, best focus on the generation plugins. Thanks.

@kompan You forgot to claim the task. ;) Thanks for taking care.

@gaoh: Can you tell what you mean by dynamic mask?

@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.

In T27439#203765, @thomass wrote:

Task T26596 is mentioned but does not correlate with the Topic asaik...maybe transposed digits in the task number?

Task T26596 is mentioned but does not correlate with the Topic asaik...maybe transposed digits in the task number?

TODOs:

• Testing of generic CEST reader
• Add some sanity checks (e.g. does offset values equal the loaded image time steps)
• Introduce 2 new CEST mime types (one high priorty that only triggers if cest_meta.json is there (because then we assume we should load like this), on norm priority mime type that only is responsible for dicoms if no cest_meta.json is there)

Discussion result: Stefan will have a look if he might find an easy solution ;) Otherwise skipp it.

Discussion result: We deem it premature optimization and the unmanaged raw pointer should be removed. Get the geometry from base data and cast it where needed. If the cust does not work. Throw an exception, because it is an exceptional state.

Status: Workbench with WorkbenchRelease configuration excluding ACVD/Remeshing starts on Windows. Does not solve T26981: [Segmentation] Multiple Segmentations under one parent node aren't displayed. :/

Pushed new branch feature/T27461-VTK9.

As discussed we bump the priority as it has serious impact onthe UX.

@sharonYu Thanks for the data. That helped to identify the problem.

VTK 9 changed core components like vtkCellArray that require a thorough adaption of existing code (including external projects like ACVD).

@floca : thanks. Not the whole trick but helped a lot. I will follow up with more geometry questions later ;)

The zip file below is the DCE-MR image.

I put a _non-shareable_ dataset in /ad/fs/E132-Projekte/Share/MarcoToMitkTeam .

@kislinsk May be you have further ideas. If you could tell how to property configure the vtk part of the mapper to "just do nothing", I would test it in conjunction with observation 4.
In this case this task would be highly correlated with T25098, as it means to ensure that all data only renders, if the current time step is in their time bound.