In section 3.2.1 "Visualizing bootstrap results", two visualization methods are mentioned, but only one is contained in the report: "To investigate which tasks separate algorithms well (i.e., lead to a stable ranking), two visualization methods
are recommended."

Maybe a nice introduction project for a new student.

Deleted branch bugfix/T27030-MigrateToNSISv3.

Pushed new branch bugfix/T27030-MigrateToNSISv3.

This happens with NSIS 3.x. We use NSIS 2.x. However, CMake dropped NSIS 2.x support in version 3.17, so we should finally get rid of this error and also require NSIS 3.x.

This is not planned for the Kaapana release.

The plots can already be limited to the top x performing algorithms. This can be reused in that case. Then the question is how many legend items are we going to "guarantee" appearing nicely?

One strategy would be to add an optional argument in which the number of displayed teams can be specified. For challenges with 200 participants, even multiple columns might be confusing.

The 19 algorithms are shown correctly. The strategy for more algorithms is discussed in T27748.

The 19 algorithms are shown correctly.

It works with the vector. The generated jpeg and png files have a quite low resolution and are as such not really reusable (e.g. in a presentation slide). Can you increase the resolution?

The warning is raised because the label is defined when bootstrapping is used but also referenced when bootstrapping is not used.

I think the things you changed are all reasonable, the things I would add (I can not do it atm because I don't have access to the document)

Almost all suggestions from Lena can be realized, apart from listing the metrics in the meta data which we don't know.

Is it not possible to create a plot first on a canvas that contains everything and as a second step add the scaled plot to the report?

I agree :)

We discussed the open todos concerning Checklists (storage, format, language) and decided that this topic should be prioritized higher but not for the milestone of the new release / current documentation refactoring.
I think this would be a good option for the phase after the release but if you have a strong point to do it now, please state here.

just started to have a look.

I like the proposal!
"0 missing cases have been found in the data set. However, performance of not all algorithms has been observed for all cases. Therefor, missings have been inserted in the following cases:"

@thomass, @gaoh Can someone please proofread?

Yes, the workbench is starting without any issues.

Did you your "release ldd" Workbench started and worked properly at all? Seems like most of the SOs could not be loaded correctly. Not even MitkCore. I would assume that workbench does not even start?!?

I hope I did it right..

I updated the document and added content to explicitly test

• segmentation on a 3D image
• 3D segmentation (static) on a 4D image
• 4D segmentation (dynamic) on a 4D image

@schererj Is this needed for the kaapana release?

In T27718#209922, @neher wrote:

check content, e.g. if != 0 voxels exist etc

In T27569#209924, @nolden wrote:

Just checked GDCM 3.0.7 if by chance the issue was fixed there, unfortunately not.

Pushed new branch bugfix/T27701-PluginGenerator.

http://gdcm.sourceforge.net/wiki/index.php/Color_Space_Transformations

Just checked GDCM 3.0.7 if by chance the issue was fixed there, unfortunately not.

check content, e.g. if != 0 voxels exist etc

Good point! It only occurs after I have removed the image node. When I initially open the segmentation plugin, the new button still is deactivated as it should be.

Also, the "red warning" does not change back to "Please select an image" if an image is removed (which was automatically selected before).