OK, will look into it. If you could feedback insights regarding the master, it would be great. Thanks.

not yet in the master.

Pushed new branch T27078-Crashes_with_empty_double_ellipse.

It seems to happen in a function ConvertHistogramToMap() that does not exist any more in the current master. We should observe if the propblem still exists, if the new code is used.

At least we got a crash dump as first hint:

This crash was a subset. Currently we would have had always crashes if something went wrong with the calculation (like planar figure with no arear).

Was able to successfully connect an OpenStack Ubuntu 18.04 to Jenkins via SSH. Currently writing a cloud-config file to provision the instances for MITK.

@kislinsk Could you describe the current status?

I know. I was just talking about removing the code from our DICOMReader, that gernerates these deprecated properties. The rest could stay as is, so scene files should should not be feel an impact. And we also have the mapping code in place.

FYI: When changing/removing properties there's always the chance that old mitk scene files are suddenly incompatible as properties are stored in them. If that's an issue, property aliases may be a solution for a legacy mapping between property names.

I would close it because we have the DICOM property view for that. This view shows the DICOM properties with also the human readable name of the tag. In addition it shows the value slice and time resolved.

@thomass Is this still relevant? If yes, what do you mean with sub groups. I don't know this term from DICOM?

Pushed new branch T27118-Package.

Pushed new branch T27091-Matchpoint_moving_and_target_masks_are_not_set.

@kompan Please make tasks that are of general nature and have an impact on the public MITK MITK tasks with a FS-E IT Strategy tag and not a FS-E IT task.

I will try to build with the current master. I will post here my findings.