@k656s have you heard from @gaoh about the status of this container?
Is there a new one, which is based on the MITK develop branch?

Similar to T27716: Extend "Checkliste Segmentierung – Manuelle Segmentierung / 2D Segmentierung" I updated the document and added content to explicitly tests different image types / segmentation types.
Additionally I tried to make both checklists more consistent.

In T27507#207494, @kalali wrote:

So Region Growing 3D seems to work and could probably be used for reference for other algorithms.

Any details?

Deleted branch bugfix/T26897-RemoveCustomFindGitModule.

Should be fixed now.

In T26897#212304, @kalali wrote:

I wonder how this is related to our findings from December last year.

Pushed new branch bugfix/T26897-RemoveCustomFindGitModule.

I wonder how this is related to our findings from December last year.

I noticed a few things that may be related or not but we should clean them anyway:

Deleted branch feature/T27852-CDashAddOptionToCleanDirs.

You can add the following options to your configuration script:

Pushed new branch feature/T27852-CDashAddOptionToCleanDirs.

Seems to be resolved by setting

"GIT_EXECUTABLE:FILEPATH=/usr/bin/git"

in MITKDashboardScript.cmake

Jerome Devy reported problems with the installation on 12th October 2020.

yes, openstack

May be completely unrelated but who knows: https://cmake.org/pipermail/cmake-developers/2015-November/027082.html

disadvantage would be dependency on another package facilitating ggplot2 dendrograms

current implementation is fine. However, we said it would be nice if all plots (if directly called by users and not within the report) would have the same syntax and could be layouted with ggplot2 syntax. current implementation is using basic R graphics.

turned off in v1.0, everything else postponed

I also agree!

People that are not from the statistics community might find them easier to read and interpret. I would be in favour of keeping them in the reports. We used the plots in one of our papers.

What is the issue with the current implementation?

This just occurred on my ubuntu dartclients. Any idea how to fix this in MITKDashboardScript.cmake?
https://cdash.mitk.org/index.php?project=MITK-Diffusion

Sounds good to me (the view just came up in T27563, so I thought I should open a task that it doesn't get forgotten about). It has low priority though at the moment and it makes sense to tag it with "next milestone".

Should we put this on "Next Milestone" since the chart example will probably not be included in any installer?

Deleted branch hotfix/T27849-MITKExtensionsInCDashScriptOnUnix.

Pushed new branch hotfix/T27849-MITKExtensionsInCDashScriptOnUnix.

https://github.com/Kitware/CDash/issues/514

Oh, I just noticed an "Add repository" button in CDash. There may be the possibility to actually report revisions of more than one repository. Let me check that... :-)

Done. @floca, if you do not agree, please reopen.

I looked into the CDash script and to basically "swap" the primary repository would induce many many new lines of code. Hence, I vote for "let's always keep MITK as primary repository that reports its revision but change the CDash settings to the MITK repository instead of the MITK extension's repository". Tl;dr: Make the revision links work in the web UI but they will always link to MITK, not an MITK extension.

The quick fix would be to change the repository base URL in the CDash project settings to MITK but I guess the preferred solution may be something like a setting in the MITK CDash script to decide if MITK should be the repository of interest or an MITK extension should be the repository of interest. Thinking about it, it probably must be a combination of CDash project settings and CDash script as we cannot change project settings from script but probably we can somehow achieve to report a revision from another repository than MITK in the update step.

I'm currently in develop branch (0d336d68).
What I meant to say is that, from what I see in QmitkMeasurementView, the crosshair navigation should be limited when placing a figure. However, the method QmitkMeasurementView::DisableCrosshairNavigation() fails to load the limited display interactor.

I landed the changes of D423. For the next steps, consider T27507#211912.

I landed the changes of D424. For the next steps, consider T27507#211912.