Deleted branch from rMITK MITK: release/T28420-2021-Week-12.

Pushed new branch to rMITK MITK: release/T28420-2021-Week-12.

Deleted branch from rMITK MITK: bugfix/T28413-PatchOpenJPEGInITKForMSVC16.9.

Pushed new branch to rMITK MITK: bugfix/T28413-PatchOpenJPEGInITKForMSVC16.9.

Checked again, no idea how to fix it. The Browser seems to remove the mime type of the object... so either i remove the file check completely or we find a way of how the browser can be enabled to deal with mime types:

Is this ticket then realy priority "wishlist"? (Stefan put it there because it was not triaged at all) A solution (what ever it maybe) seems to be more relevant to Kaapana then just wishlist.

Discussion from Tech meeting (Hanno, Klaus, Marco)

The topic came up in the Kaapana tech meeting again, because the current situation is causing problems there.

I was able to reproduce the error. I will take a look

after tests of the system, the problem might be at the airflow part, this has to be tested

@j038k Hi I you look for the problem, keep in mind that the rounding error can occure when it serialized into the file (if it is in text mode). E.g. some code that saves nrrd only does it with standard precission which is in some cases 8 characters (including the dot, sign etc. this can then be not enough and you loose decimal places).

@floca André is on vacation. The original mask in nifty was produced by nnUNet, but we are using some of our Python scripts to split segmented tissues to different labels and to convert it into .nrrd format. Maybe there could be a rounding error during loading and saving the image header, we have to look at it.

@kleina Even though the problem is now fix by being less pedantic, I realy would identify the reason for the fidelty loss in the mask geometry. So the information which tool produced the mask is still welcome. Especially if it one of our tools/nets so that we can fix it.

@kleina Do they use multi label segmentation view or the old one?

On a first glance, the interpolation seems to affect the result.

1. Create the segmentation with interpolation -> save it -> reload segmentation -> erosion = no crash
2. Create the segmentation with interpolation -> erosion = crash

check with microk8s - kata microk8s current system

The issue can indeed be solved by a mitk::RenderingManager::GetInstance()->RequestUpdateAll(); in QmitkLabelsetWidget function OnVisibleButtonClicked() but there seems to be something wrong with the lock logic when "Lock All" "Unlock All" is clicked

Kata-supported platforms are given below.

Yes, as soon as there is a new tag that includes your necessary changes, just change the tag and click on build.