Pushed new branch to rMITK MITK: feature/T27992-CmdLineAppsInWorkbenchReleaseConfig.

I asked in the general Slack channel for command-line apps in use. It boils down to the file converters in CoreCmdApps. Other mentions are too specific for the WorkbenchRelease configuration and are related to the Classification module. We should consider adding a phenotyping build configuration, though.

Files that cannot be read by a CSV reader should be deleted immediately to avoid that potentially malicious resources are hosted on this public server. A simple check for file extension is not enough. Arbitrary files can be uploaded by just adding the extension *.csv.

I looked through the checklist and updated it to be in line with the already updated checklists (see parent task T28108).
I copied the modified document to E130-Daten\Release\Checklisten\MITK Workbench Release.

The issue has already been reported here T26754 and here T22395, so I will merge the task here.

Screenshot from the MITK Github page:

Deleted branch from rMITK MITK: feature/T27460-Badges.

Pushed new branch to rMITK MITK: feature/T27460-Badges.

Ok, I modified T27498#208164 to update the missing views. I say, for the release we leave the utilities the way they are (your option 1. keep it as is: user has to select manually). We keep an eye on it if this leads to some confusion.
SemanticRelations is not relevant for the release so I'll put this in another task.

Deleted branch from rMITK MITK: bugfix/T28189-FixDoxygenWarnings.

Pushed new branch to rMITK MITK: bugfix/T28189-FixDoxygenWarnings.

I used the snapshot client configurations as baseline and created Jenkins jobs in MITK/Release. I also extended the Git hook to trigger these jobs. Hard to test, though, as I do not want to temporarily push test tags. Fingers crossed.

@kislinsk anyone from the MITK CI team who could take over?

In T28127#217604, @gaoh wrote:

@floca I might have found a dataset, where even the new number is not enough:
P:\Gao\mitk-testdata\

@floca I might have found a dataset, where even the new number is not enough:
edit:
E130-Personal:\Gao\mitk-testdata\

Hm, interesting... I say we but it under the category experience and close that chapter. If it reoccures we see how to handle it. Thanks for investigating it.

Something strange happened:
I wanted to test some GUI functionality for your open diff but somehow I was not able to load data anymore: Clicking on Open File did not open a window.
Then I removed the DKFZ AppData folder to have a fresh MITK workbench. Now clicking on Open File opened a window but while I was scrolling inside this window to find the desired data, the window stopped working (did not scroll anymore - whole application was frozen).
So I did a Windows restart and opened MITK again. Now I am able to load data again and Voila: The segmentation view now automatically selects the newly added data node (patient image selector).
...
...
Tbh, I have no clue what's going on.

@floca thanks for the report! I added a comment to the dcmqi issue you created.

I'm currently on the latest develop (rMITK15ecdf8d92aa). Only a small set of plugins enabled (datastorageviewertest, (ML)segmentation, imagenavigator).
I'm doing this in Debug mode.

In T27498#217438, @kalali wrote:

I just came across this again:
For me the following happens:

1. I open the MITK workbench
2. open the Segementation View
3. below the image selectors a warning Please select an image is shown
4. both image selectors show a red warning
5. I open an image e.g. US4DCyl.nrrd
6. the warning below the image selectors changes to Select or create a segmentation
7. both image selectors still show a red warning
8. the image is not automatically selected

In T27703#217487, @kalali wrote:

Is this solved?

As far as I have described above, yes.

1. The new selection concept automatically removes non-matching segmentation nodes if the reference image was changed. A warning is shown Select or create a segmentation (Tools disabled)
2. The new selection concept does not allow to select a non-matching segmentation node
3. Selecting a matching segmentation node that is invisible results in the warning: The selected segmentation is currently not visible! (Tools disabled)
4. Showing the invisible segmentation node results in the warning: Please perform a reinit on the segmentation image! (Tools disabled)
5. Performing a reinit on the matching segmentation node enables the tools (no warning shown)

We are now using a different approach but this should be verified with the new widgets.

Is this solved?

Need to recheck after T28118: Refactoring of SegTool2D is done.