For the bigger MITK Workbench version of the 2023.10 release it is planned to include Pharmacokinetics (Perfusion, PET) and ModelFit.
Specifically, the following plugins will be included:

Pushed new branch to rMITK MITK: feature/T30222-MatchImageMiniApp_add_parameter_support.

I looked shortly into this, but couldn't find an easy way to solve it. The problem is that for the desired behavior, one needs to capture not only events of the utility widget itself, but also of all its child widgets.

Not clear when and how it happens. Need to narrow it down more.

Yes, that was it. Works now!

most likely it is due to wrong locales in the out stream operation on your OS. You have ',' in your file where '.' should be.

This is the sample NRRD file written by the above mentioned writer function. It can't be opened in Python or by

Exception occurred when reading file /tmp/mitk-sam-OBvksy/sam-in-QOdQsN/3111588501110146159.nrrd:
/home/user1/DKFZ/nnUNet_work/MITK_nnunet/build/ep/src/ITK/Modules/IO/NRRD/src/itkNrrdImageIO.cxx:292:
itk::ERROR: NrrdImageIO(0x561dd4b8c4b0): ReadImageInformation: Error reading /tmp/mitk-sam-OBvksy/sam-in-QOdQsN/3111588501110146159.nrrd:
[nrrd] nrrdLoad: trouble reading "/tmp/mitk-sam-OBvksy/sam-in-QOdQsN/3111588501110146159.nrrd"
[nrrd] nrrdRead: trouble
[nrrd] _nrrdRead: trouble reading NRRD file
[nrrd] _nrrdFormatNRRD_read: trouble parsing space origin info |(-185,04367065429688,-161,31900024414062)|
[nrrd] _nrrdReadNrrdParse_space_origin: couldn't parse origin "(-185,04367065429688,-161,31900024414062)"
[nrrd] _nrrdSpaceVectorParse: space dimension is 2, but seem to have 4 coefficients

Pushed new branch to rMITK MITK: feature/T30155-ROI.

Pushed new branch to rMITK MITK: feature/T30215-totalseg-v2-update.

Deleted branch from rMITK MITK: bugfix/T30213-PocoOpenSSL.

Pushed new branch to rMITK MITK: bugfix/T30213-PocoOpenSSL.

I think in doubt I would just move but not merge it for now. If we see that it is needed or wanted we can make the effort and merge it. It would be better than not offering this feature at all.

The dicom inspector has one additional dependency to module MITKDICOM. Therefore if we merge the inspector plugins also our normal inspector could only be build if DICOM module is activated. (Which it currently is per default).

In fact, this problem occurs not just for the progress bar, but the progress itself, e.g. also in the info box 1 is currently never reached even if the descriptive parameter calculation process is finished. The reason for this bug is that the progress is stored in a member variable which is updated after the progress event is invoked. Therefore, the progress variable is always lagging one update behind. This is fixed by changing the order of the called functions.
The fix is done for the descriptive parameter calculation, but also for the pixel and ROI-wise fitting.

Integrate into F1 help. Make MITK ModelFit Webpage deprecated for manual section with link to doxygen documentation.

It is a useful feature and should be part of the next release.
Open to dos:

• Checklist
• check dependencies of the view. If the view does not have more dependencies then our property inspector should be merged.