As far as I understand the plugin's purpose it is basically an export of an image as CSV file? And the request is to add it to MITK instead of eMITK? Is there some additional functionality involved or could we just add it as another MIME type for images instead of a dedicated plugin?

Deleted branch from rMITK MITK: feature/T30177-ContourModelSetToSegmentationApp.

Deleted branch from rMITK MITK: feature/T30176-FindTask.

The app is now called MitkContoursToImage. By default it outputs classic binary images for each contour set in the input. Use the --format/-f flag (defaults to binary) to change the output format to label or multilabel. The former outputs single-label segmentations for each contour set in the input and the latter outputs a single multi-label segmentation with labels for each contour set. Note that each label will be in its own layer/group to allow for overlapping labels.

Pushed new branch to rMITK MITK: feature/T30177-ContourModelSetToSegmentationApp.

Multiple reasons depending on the reference data. Mainly related to non-conforming images or at least images that are recognized as such by us or our third-party deps. Other reasons include 4-d images as you already mentioned. We talked about it a few days ago and this part of MITK and our third-party deps needs a little bit of love and affection as it seems.

Pushed new branch to rMITK MITK: feature/T30176-FindTask.

I just did the Pic3D/brain test mentioned above and it works with v2023.04.

@gaoh Since we released MITK v2023.04.2 yesterday specifically addressing a DICOM-SEG issue I kind of got an overview of the overall situation in MITK regarding saving DICOM-SEGs.

We could set up a test case to check if it is still an issue in the context of segmentation task lists. A segmentation task list with two tasks, one task referencing Pic3D.nrrd, the other task referencing the tilted brain.nrrd image. If this is working with the latest release it should be a proof that is not an issue anymore.

Thanks for the report. We recently removed this functionality from MITK so I would like to close this task as Wontfix if you are fine with the workaround you mentioned?

Deleted branch from rMITK MITK: bugfix/T29649-ClassificationModuleCleanUp.

The tag v2023.04.2 was created on the branch hotfix/T30163-v2023.04.2, which should not be deleted.

Pushed new branch to rMITK MITK: bugfix/T29649-ClassificationModuleCleanUp.

You seem to mix a few things here.

Pushed new branch to rMITK MITK: hotfix/T30163-v2023.04.2.

I can reproduce the crash.

It is technically possible but it would require about a person month to complete, so we decided for now we do not want start implementation as it is as important as other tasks that we have to accomplish.

Deleted branch from rMITK MITK: bugfix/T30159-DisableITKPathLengthCheckOnWindows.

Pushed new branch to rMITK MITK: bugfix/T30159-DisableITKPathLengthCheckOnWindows.

@floca Is this something we are already aware of (saving as .dcm crashes)?

1. Done
2. If the geometry is to be defined right in the file itself, I vote against a ReferenceGeometry type of "Geometry" but rather actually a "Geometry" JSON object. So it is either having a reference to something else that defines the geometry or specifying the geometry right in the file without any redirections.
3. Done, also added "Type" to "Frames", which is "Box" for, well... boxes.

Thanks for the feedback. 🙏

Qt 5.15 is built against OpenSSL 1.1.1, however, Ubuntu 22.04 provides only the incompatible OpenSSL 3, which is why the calls cannot be resolved. The Qt 5 apt packages (resp. system Qt 5) is probably patched to work with OpenSSL 3, though, which is why it works on build machines that use system Qt 5 instead of the Qt5 online installer. System libs are not packed into installers, though, so it only works in the build tree and installers will be broken on other systems.