Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

I will go through the source tree and as a rule of thumb I will just add nullptr checks if the render window part is only used for rendering updates and add the OPEN strategy if more is done with the reference and there is not already a nullptr check.

I tested it in debug mode and the fix is pretty simple. The crashes occurs in lines like GetRenderWindowPart()->RequestUpdate() when GetRenderWindowPart() returns a nullptr. I guess there are quite a few unchecked lines like this in MITK.

When I reproduced the issue with MatchPoint, it didn't happen when the documentation was in the background (i.e. the documentation is not the active editor). I guess this is a good starting point for debugging.

We are going to rewrite the 2-d LabelSetImage mapper and write a 3-d LabelSetImage mapper this year, where this will be addressed. We should at least clean up the duality of the contour properties (binary vs. labelset.contour). We should probably allow to show the contour without any filling and we should clean up the coupling between contours and active label.

I didn't really look into this but it reminds me of something I stumbled over a few weeks ago. There's a bug in C++ 14 regex regarding temporary strings: https://cplusplus.github.io/LWG/issue2329

Thanks for reporting. We recently rewrote the Python integration in MITK. Its status is at ~80% and it will get merged as soon as we figured out the packaging for Python in MITK (branch feature/T27923-python-dev). The QtPython module was removed as we do not longer depend on CTK/PythonQt for the Python integration.

I gave @schererj and @gaoh rights to start the Kaapana MITK build jobs and to read the configurations: https://ci.mitk.org/job/MITK/job/Kaapana/

• FileConverter: Covered by regular release (see MITK Volume below)
• Phenotyping: https://www.mitk.org/download/kaapana/phenotyping/
• Radiomics: Covered by Phenotyping
• FlowBench: https://www.mitk.org/download/kaapana/flowbench/
• MITK Volume: https://www.mitk.org/download/kaapana/workbench/

Okay, nice. Last question: You currently have both a PhenotypingRelease and a ClassificationCmdApps configuration. The apps of the latter one are also included in the former configuration. Is it fine to just go for PhenotypingRelease then at the cost of a little larger tarball as also the workbench application is included? @schererj

Okay. Currently running the first test with the PhenotypingRelease configuration and tag set to v2021.02. So the file name will be automatically versioned and will appear at https://www.mitk.org/download/kaapana/phenotyping/ once the build succeeds.

To all: Do you want to version files or do you want to simply override existing old installers when generating new ones (which happens with custom set revisions descriptions as done in a few docker files above)?

I noticed that the only plugins enabled in the "MitkVolume" configuration are the segmentation plugins. Do you explicitly want to have this "slim" version or is the official WorkbenchRelease configuration more sufficient?

Nvidia AIAA WorkbenchRelease binaries are building or were already deployed.

Deleted branch from rMPT MITK-ProjectTemplate: release/T28000-v2021.02.

Pushed new branch to rMPT MITK-ProjectTemplate: release/T28000-v2021.02.

Deleted branch from rMPT MITK-ProjectTemplate: release/T28000-v2021.01.

Deleted branch from rMITK MITK: bugfix/T28000-BumpDevelVersion.

Pushed new branch to rMITK MITK: bugfix/T28000-BumpDevelVersion.

Deleted branch from rMITK MITK: bugfix/T28000-BumpDevelVersion.

Deleted branch from rMITK MITK: release/T28000-v2021.02.

Pushed new branch to rMITK MITK: bugfix/T28000-BumpDevelVersion.

Pushed new branch to rMITK MITK: release/T28000-v2021.02.