At least for me the crash hasn't occured for a long time (I believe since around the 2023.12 release) despite working using the ModelFitInspectorView very often. So the bug might have been resolved along with another fix "accidendally". I will close the task for now, however, should the error re-appear, the task can be re-opened.

When SetAutoSelectNewNodes is set to true, the function should be emitting "CurrentSelectionChanged" which is connected to "OnImageNodeSelectionChanged". In case the views are open initially and have no Selected Time Series set and a dataset afterwards is loaded into the Data Manager, the dataset will be autoselected and "CurrentSelectionChanged" is emitted as expected. All good here.
However, when the dataset is loaded first into the Data Manager whilst the views are closed and then the views are opened, the "CurrentSelectionChanged" signal does not get emitted and hence the "OnImageNodeSelectionChanged" is not called and and the m_selectedImage is null. In this case the "Start Modelling" button stays inactive.

I could narrow the occurence of the inactive "Start modelling" button down some more:

• Windows Edition: Windows 11 Home
• MITK Blocked /Scanned: When starting the MitkWorkbench.bat file the Windows system does not let it run intially. A window appears "Windowps protects your PC- Microsoft Defender SmartScreen prevented an ungecognised app from starting- Running this app might put your PC at risk." Then the option "Run anyway" was selected.
• Installation location: in C drive ( Desktop)
• Exact terminal output: Command window with a large amount of text appears when the software runs; otherwise, only the first paragraph ("C:\Users\....\bin\MitkWokbench.exe") appears in the command screen.

This task is closed since the ModelFit/Perfusion views will be part of MITK v2024.06 and it is planned that they will be part of the official releases from MITK v2024.06 onwards.

In the MitkNodePredicateGeometry to precision is set to 1e-6. So this is at least one of the issues why the old masks are not found. It could be an option to relax the precision, but since the rotation matrix might have a large effect even for small inaccuracies, it needs to be thoroughly tested first how big the effect is if. e.g 1e-4 is accepted.
For now, the new segmentation masks are provided as test data instead of the old masks.

I compared the geometry of the dynamic image, the old mask (which could not be found anymore) and a new mask (is found), using the Details info box in MITK. I found small differences in the geometries between the old mask and the dynamic image, but not between the new mask and the dynamic image. Namely:
Spacing:
dynamic image: [1.0156, 1.0156, 5.99998]
old mask: [1.0156, 1.0156, 5.99997]
new mask: [1.0156, 1.0156, 5.99998]

It is not straighforward which name to use, since what is displayed in the Image Navigator depends on if the dynamic image has been globally or locally initiated. Therefore, for now we keep the name "Time" in the Image Navigator. What is shown is therefore not obvious for the user and should be documented clearly in the F1 help. It needs to be checked if this is the case.
A solution could be to provide a separate slider in the ModelFit Inspector View.

Since this issue was pointed out by a user recently (and I also found it confusing before reading this task description), I would like to re-open this task for discussion.

It seems to be an issue with this specific dataset. I made new set of segmentations (Prostate label and AIF label) and stored them each as DICOM segmentation. And now I find that the segmentation nodes are found as expected. It needs to be determined if the old data set is somehow corrupted or if it is a backwards compatibility issue (the masks were initially created in 2019).