There are two separate issues:

No I did not check that and currently I don't know why it worked before.

Will look into it today.

Cool. Thanks for the explanation. Did you also look into the identifiers in v2018.04.2? I wonder wether some identifiers were changed since then or the code that generates the link to the help page.

@kislinsk What's the status? We discussed this and the mentioned task last Friday and decided to disable the autocrop-freature for multi-label via data manager context menu if there is no easy solution.

Just as a remark: I am getting the exact same error, if I want to load a dcm image from a folder that contains more than one image. Those images originate from a cadaver study which means that before acquisiton most of the patient input data is left blank (study,series etc). If I put the files into separate folders, they are loaded correctly.

@floca: This would be the most urgent from the tasks, as I did't find a work around so far.

• data is taken as is (see also comment to T27568)
• I'd say the probably correct description would be 2D-Realtime B-Mode where images are made at a constant frame rate (20 fps in the case of the Canon video). If you consider moving the transducer over the body it not necessarily results in a 3D image, more 2D+t - if you keep the transducer at a fixed spot and e.g. only tilt the tranducer, it is more 3D like.
• I am not aware that there are sensors in the transducer that would give us its position and orientation in space
• Is e.g. a "Play" button for the z-dimension a possible solution?

Thanks for the remarks and solution options.

@floca: Can you please post a download link for the Mac installer / binary of the most recent version?

Rework of the GIF containes some API breaking changes in the GIF class interface.

Update: the root of many cases of this problem are the same as discussed in T27568: US 2D image cannot be read: invalid tilt information. In the mean while some cases (as OT-MONO2-8-colon) work now (due to fixes of T27321 and T27322) others (like CR-MONO1-10-chest-*) still do not work. The reasons and solutions are the same as described in T27568.

Spawned concrete tasks for each problem.

@kleesiek: I cannot reproduce the problem with our current develop/master branch. Does it also fail for you in the recent versions?

@kleesiek Is it realy temporal resolved (what would be the resolution?) or is it a b scan an therefore more like a volume? Did you anonymize the data somehow, that might thrown away to much geometry information or so?

Should discuss in the MITK meeting about the solutions.

As this task containes multiple issues/tasks, I have splitt it in sub tasks. This meta task will be closed as the work will be done in the sub tasks.

TLDR: Basically one needs to check if the plugin-id is the same as the page-identifier inside the *.dox-file. Looking at the Registration-plugins it is clear why these are not working.

I found out that this is a basic problem of changing of parent nodes. It can also be reproduced in a much more simpler way:

1. Open Pic3D
2. Open US4DCyl
3. Make one image the child node of the other image
4. Crash

Pushed new branch T27567-GlyphIssue.

Pushed new branch feature/T27564-integrate-deeplearning-segmentation.

Added FS-E IT since this is coming from DKFZ radiology

Document how you can use your own intropart. Changlog and dev docu (where?)

In T27043#206242, @kompan wrote:

@floca There is still an issue in the UI: When using the mitkSingleNodeSelectionWidget for the mask selection instead of the QmiktDataStorageComboBox, the mask selection field in the UI becomes larger than the time series selection field (see D348). It only gets reduced in size when further options, i.e. a model are selected. At least on first attempt, I couldn't get both to have the same size. Maybe you have an idea how to fix this and make it look pretty again?

Pushed new branch T25826-RadiomicsUpdate-V3.

thanks for the thorough check.

I think I can remember it differently in earlier version

I checked installer 2016 / 2018 and some 2017 BlackSwan Demos and couldn't find a scenario where the Welcome Screen was the active tab, but anyways.