Okay, this didn't change anything but won't hurt. Meanwhile I noticed that the exit code of the tests is 0xc0000135 (STATUS_DLL_NOT_FOUND). So probably it's more in the direction of something Qt related is missing in the CTest environment.

Pushed new branch to rMITK MITK: bugfix/T30336-FixFailingTestsOnWindowsCI.

recheck if the problems are still there if my interpolation changes are merged in.

Deleted branch from rMITK MITK: bugfix/T30321-UpgradeHDF5.

Pushed new branch to rMITK MITK: bugfix/T30321-UpgradeHDF5.

I don't understand why it didn't show up earlier, but now also HDF5 does not compile on Ubuntu 23.10 and needs an upgrade. Might be a bit more involved, as we are using a rather old version and there have been quite some API changes meanwhile.

Pushed new branch to rMITK MITK: bugfix/T30316-FixGLEWWarningsOnLinux.

Pushed new branch to rMITK MITK: bugfix/T30334-FixPlaneGeometryDataToSurfaceFilter.

Live wire tool (and Lasso) is already reworked.

This fitting task was applied not to many cases, therefore AVID batch processing was not required and fitting was done in MITK using the formula parser.

SegmentAnyBone is SAM with an extra attention pathway as well, pretrained on MRI dataset.
They have trained the visual transformer vit_t type model and released new pretrained weights. From code perspective, they have modified down SAM code to include attention map and packs with it in the repo.
Salient points:

Is solved by the pixel value view.

Deleted branch from rMITK MITK: bugfix/T30321-FixVTK.

Pushed new branch to rMITK MITK: bugfix/T30321-FixVTK.

VTK 9.3 has a build issue in debug mode with Visual Studio. It's a known issue but it is not yet fixed upstream.

The difference between my build tree version and the installed version is that the former is using the wayland or wayland-egl backend, while the latter is using the xcb backend. Forcing the build tree version to use xcb results in the same GLEW warnings, which is good, so I can now try to get rid of it.

Pushed new branch to rMITK MITK: bugfix/T30321-Ubuntu_23.10_Compatibility.

While compiling VTK 9.3.0, I noticed the following warning which may be interesting:

Has been clarified

Conclusion: In general it makes sense, but we would want to get rid of the "locked state" of the perspective. Needs further research if the locked state can be removed easily or be made more clearly visible, e.g. by a UI element.

• To configure the MITK superbuild, I had to install libegl1-mesa-dev.
• To run the Qt online installer, I had to install libxcb-xinerama0.

The attempt of Qt to look for the wayland platform plugin can be disabled by adding export QT_QPA_PLATFORM=xcb to CMake/RunInstalledApp.sh, which is preferrable since we do not distribute the wayland platform plugin anyway.

Deleted branch from rMITK MITK: release/T30315-2024-Week-05.

Pushed new branch to rMITK MITK: release/T30315-2024-Week-05.

Pushed new branch to rMITK MITK: feature/T30171-python-wrapping-new.

Deleted branch from rMITK MITK: bugfix/T30311-SkipOpenCVPythonDetection.

Pushed new branch to rMITK MITK: bugfix/T30311-SkipOpenCVPythonDetection.

Deleted branch from rMITK MITK: bugfix/T30308-HandleFlippedAxes.

Pushed new branch to rMITK MITK: bugfix/T30308-HandleFlippedAxes.

@fedorov I added you to "warn" 😉 you, that will join the effort. Great idea!

Deleted branch from rMITK MITK: bugfix/T30305-HandleNegativeSpacingInBoundingShapeToROIConversion.

Pushed new branch to rMITK MITK: bugfix/T30305-HandleNegativeSpacingInBoundingShapeToROIConversion.

Assessing the whole negative pixel spacing situation in MITK and in general (s.a. DICOM Correction Item: Pixel Spacing may not be negative), I conclude that we shouldn't support negative pixel spacing in ROIs, as it introduces a whole domain of obscure edge cases. Also note that while MITK geometries keep their spacing values absolute (checked by asserts), the transform matrix still contains negative values in its main diagonal, leading to all the visual and positional effects/mismaches that can be seen with ROIs generated from images/bounding shapes.

Deleted branch from rMITK MITK: bugfix/T30304-CTKQtDesignerPlugins.

Pushed new branch to rMITK MITK: bugfix/T30304-CTKQtDesignerPlugins.

Deleted branch from rMITK MITK: bugfix/T30299-Maintenance.

All pressing issues are now resolved &/or solutions are available. Hence, closing the task.

Pushed new branch to rMITK MITK: bugfix/T30299-Maintenance.

In the current ModelFit Inspector version, the current time point is not marked at all. When moving through the time steps in the Image Navigator all data points are displayed at the same color, the current time point is not highlighted in another color. We should discuss if we want this behaviour back and check if there is a bug due to which this functionality is not present anymore.

Deleted branch from rMITK MITK: release/T30295-2023-Week-49.

Pushed new branch to rMITK MITK: release/T30295-2023-Week-49.

@kompan Could you check if this is still a problem/can be replicated, as you look into the fit inspector view anyways. If it cannot be reproduce, we know at least that we may close it for good.

This could be potentially solved with T30293 if we also provide a writer (at least a very simple one that does the old style, besides that change.