We need to fix CTK as well.

Pushed new branch T26721-Qt-5.13.

Note: on another computer (running Ubuntu + 1080ti's with nvidia 430.50 drivers), MITK with newInstance also falls backs to a non core profile but the second instance does start successfully.
I'm thinking that maybe my system is missing a library or that it is related to the MESA drivers for intel's UHD?

At least on Windows the Qt 5.13.1 CMake scripts do not work when trying to find Qt5UiTools as the script isn't able to find the release and debug library paths of Qt5Core. I had to manually set the corresponding CMake variables in the MITK-superbuild, the CTK-superbuild, the CTK-build, and the MITK-build.

Pushed new branch T26728-macOS-10.15.

Pushed new branch T26727-Change-stdmultiwidget-dependent-files.

@isensee

1. Does it work if you select two normal images (not segmentations)?
2. Does the seg fault also happens if you use the Registration Evaluator plugin with the image and the segmentation?
3. Could you provied example data, please?

Also if checking validity, consider T24766.

Pushed new branch T26698-PerfusionCurveDescription_data_not_selectable.

This is still inconsistent, see screenshots:

Pushed new branch T26563-FreezeButtonCrash.

Option for browser rewrite T25582

Do this on first startup of browser/implement module check in browser?

Do this for browser rewrite T25582

We have discussed, how to proceed with corrupted images (see above).

Could you please set the status to resolved if the branch is merged?

I looked into all DICOM images that make this problems and are located in the DICOMReader/ directory.

More information on Siemens Mosaic Images, see: https://nipy.org/nibabel/dicom/spm_dicom.html

Example data is located in E230-Daten/MITK.

Possible fix is a reordering of includes in mitkPythonService.h , I could not find out exactly what's wrong.

On computer A our own built (and packaged) work well.

Pushed new branch T26696-IVIM-GUI.

@kalali Resolved?

In T26269#186984, @kraeuter wrote:

The widget still can't tell if the selected mask fits the selected image, which can cause errors.

May be I missed the point. But it is de facto possible.
You can already define a filter predicate and you can specify a filter/check lambda. Both ways would allow to control if the geometries fit or not. These techiques should be used. If you have any questions, please ask.

I wouldn't value the node name of statistic nodes that high, as it has questionable importance/value.

1. It is an open discussion if the statistic nodes should be visible at all in the data managers/storage inspectors. I currently tend to declare them as helpernodes that are not visible any ways.
2. The name is not needed for the statistics view. For relations we use the relation rules.
3. Name properties of nodes must not be "stable"; e.g. the name of an image node could change and then it would not fit any more to the image name encoded in the statistic node name.

The statistic nodes aren't named properly.
All statistic nodes are named after the last thread started, in a small selection they are all named the same.

The widget still can't tell if the selected mask fits the selected image, which can cause errors.

Pushed new branch T26694-AddMultiThreading.

this should do it

Pushed new branch T26690-fixPAgccWarningsInCommandLineToolToo.

Pushed new branch T26690-fixPAgccWarnings.

Pushed new branch T26689-MakeAnnotationRadiusConfigurable.

Pushed new branch T26658-Transducers_smallFix.