Deleted branch T24085-mitk-python-installer-fix.

Deleted branch T23343-enable-microservice-based-reading-for-dicom-editor.

Deleted branch T23756-cotire.

Deleted branch T24085-correctly-install-SimpleITK-to-bin.

Deleted branch T23342-MICCAI_2017_Tutorial.

Deleted branch T22830-fix-image-conversion-build-errors.

Deleted branch T23339-change-dicom-reader-default.

Deleted branch T22118-create-Qt-installer.

Deleted branch T22654-threshold-components-tool.

Deleted branch T22801-update-dicom2nrrd.

Deleted branch T22810-Add-tolerance-to-surfacetoimagefilter.

Deleted branch T20223-RGBAImageFix.

Deleted branch T19360-legacy-scene-surface-line-width-incompatible.

Deleted branch T19801-planar-figure-interactor-crash.

Pushed new branch bugfix/T27624-FixDoxygenErrors.

Thanks!

Deleted branch bugfix/T27670-InvalidLinkInStyleGuide.

Pushed new branch bugfix/T27670-InvalidLinkInStyleGuide.

Deleted branch bugfix/T27661-NewModuleDoc.

Pushed new branch bugfix/T27661-NewModuleDoc.

macOS MatchPoint errors that are actually just warnings should be fixed now as well. It's a bug in CMake/CTest and the workaround is to use launchers: https://gitlab.kitware.com/cmake/cmake/-/issues/20832

I finally found the source of the documentation errors by accident. It was a dot digraph with invalid flat edges between record shapes. I changed the shapes to boxes and it should work now.

I re-created the branch above, branching off from the latest develop branch.

Pushed new branch bugfix/T27608-DocumentationRefurbish-DeveloperManual.

Deleted branch bugfix/T27608-DocumentationRefurbish-DeveloperManual.

I think I fixed the OpenCV Ant issue by updating the volume snapshot for our Ubuntu 20.04 cloud instances to include the environment variable ANT_HOME=/usr/share/ant.

Pushed new branch bugfix/T25882-RewriteDashboardScript.

Deleted branch bugfix/T25882-RewriteDashboardScript.

Yes, they are in the workspace of the Nightlies but I hesitate to provide them externally as they have a bunch of problems. Besides the DICOM-loading problem that we currently have with the installers in general, the macOS MITK Workbench from the installer is not executable by clicking on the MitkWorkbench.app. One have to use the terminal, cd into the package and execute the actual MitkWorkbench executable.

The Photometric Interpretation tag (0028,0004) of the Philips US image is set to YBR_FULL_422 and my first guess is that we do not take this tag fully into account, leading to a misinterpetation as RGB values while reading the data.

In T27669#209003, @floca wrote:

@kislinsk As a linux noob please pardon my question. Can we directly debug the nightly bild by the CI on e.g. Jonas system? I would like to see some of the parts of volume generation process running to see whats happening. My be it helps us getting a lead. At least we now a setup directly on site that makes the problems.

We talked about this task in the group-5 meeting. It turned out that no more foreground pixels are added after the mouse button was released but that it is just a little slow on the test computer and the latest feedback contour wasn't yet calculated when the mouse button was released. So, not really a bug in my opinion. At least nothing new, since the algorithm of the tool did not change.

Oh... @thomass just told me that there is also T27698: [Segmentation] Segmentation toolbox is never enabled in multi-label segmentation view where it is already resolved... nvm.

Happens only the first time. When I delete all segmentations and then create another new segmentation, the tool widgets in both views are enabled. Might explain why I didn't notice it when doing D312, as I was sure that I tested this before.

• SegmentationInteractor is only used in ML Segmentation. I added the ML context.
• I also added the ML context to the second call of GetToolManager() QmitkSurfaceStampWidget, it was simply forgotten

• MITK_BUILD_OPTIONS for MITK cache vars
• Check why there are documentation errors "lost edge a b" but when I manually "make doc" on the client, it works
• OpenCV somehow seems to trigger Ant errors on Ubuntu only during the first build (problem in Nightlies)
• First time build of MatchPoint triggers many warnings as errors on macOS

Deleted branch bugfix/T27436-HideInterpWidgetsInMultilabelSegView.

Notes for the Region Growing 2D tool:

• The tool operates based on the current level window, so changing the level window to optimize the contrast for the ROI should be encouraged
• Moving the mouse up/down is different from left/right. One direction is for level window width, the other direction moves the level window

The "url" downloads do not work for me. Slack is telling me that "there is a glitch".

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Deleted branch hotfix/T25882-CDash-v2.6.

Deleted branch release/T27695-2020-Week-36.

This is part of this issue (actually the main reason). It is already working in my local version but I have to make a few adaptions to get a stable minimum working version for production.

Pushed new branch release/T27695-2020-Week-36.

I agree to @floca and I am quite sure this is related to installer vs. starting from build directory.

Layers don't have names. The plugin is only asking for label names which are important of course. For a new segmentation there are two dialogs: for the segmentation name, and for the fist label name + color. I think it evolved from the UI pattern of the old segmentation plugin and I agree that the label dialog should be omitted. A "New label <i>" could be added to the label widget instead and we should probably improve this widget so a double click on the name opens an in-place editor for the name string instead of requiring the user to right click -> Rename... -> Dialog. Color editor already works this way.

I cannot see any declaration of GetRenderingManager() in BaseRenderer (even before rMITK5e0e87c3)? In the second example I even cannot see anything related to RenderingManager? :-)