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

Yes, let's deactivate them for now (again), and discuss it in the next MITK meeting.

Also, the checklist states "Er ist disabled"

What exactly? I copied the checklists to my local machine and I'm working on T27716: Extend "Checkliste Segmentierung – Manuelle Segmentierung / 2D Segmentierung".

@jsolislemus Sorry for the long delay, I kind of missed your comment and related discussions happened in T27669

the first sentence refers to the fact that no missings have been found in the data set. would rephrasing to "0 missing cases entered in the data set have been found" help? the next sentence is about cases which have been inserted by the sanity check. Would adding "However, ..." in between help?
If you have any other suggestions, I would be happy to include them

@schererj we just discussed this in the MITK meeting. Could you try something? It would be interesting to compare the outputs of

Damn I have forgotten to copy the checklist to a reachable share. @kalali Is it already done now or obsolete?

All tools have to check for the following usage scenario:

• All this with an image which time geometry does not start at 0 ms (e.g. MITK-Data/3D+t-ITKIO-TestData/LinearModel_4D_arbitrary_time_geometry.nrrd)

Since we have this task now I suggest to deactivate them "somewhere globally" and discuss later how to proceed. My guess would be it is quite some effort. Having tests for the generator, packging and the extension mechanism is very important I think, but I'm not sure what the current tests cover and if it's worth to fix.

I started with the checklists I from E130-Daten\Release\Checklisten\MITK Workbench Release.