Thank you, I wanted to post the discussion result here as well. I will fix this.

The "url" downloads do not work for me. Slack is telling me that "there is a glitch".

I would suggest that at least the plugin feedback in the GoogleDocs and the toplevel-> main page /MITKUserManual should be corrected before the Release. The rest should be corrected soon after.

@kislinsk: should we further investigate this or have a known issue section in the documentation?

In T27669#209010, @thomass wrote:

The log information in the console which Jonas reported doesn't turn up. So the console doesn't show any new information after the reader is selected.
I will ask about the HDD / IO.

The log information in the console which Jonas reported doesn't turn up. So the console doesn't show any new information after the reader is selected.
I will ask about the HDD / IO.

In T27669#209008, @thomass wrote:

she doesn't even get to the logging point. It doesn't show anything, it just stops (She closed the workbench after 10 Minutes).

What do you mean with logging point?

I am not sure if that is related but today one of my cooperation partners reported that she couldn't open an 4D image in MITK (Latest develop installer).
On my laptop it just works fine. On her laptop, however, she doesn't even get to the logging point. It doesn't show anything, it just stops (She closed the workbench after 10 Minutes).
I asked her whether it was an ancient laptop, but no ;)

Discussion result:
As you cannot hook into the Qt connect mechanism, I see no "simple" chance to automatically manage that under the hood. The most pragmatic solution is to simply add a remark to the class (QmitkSingleNodeSelectionWidget) and method (SetAutoSelectNewNodes()) that on should activate this feature *after* connecting the events to ensure already the first autoselect has an effect.

In T27669#208901, @schererj wrote:

It is pretty weird since it even:

suggests 1 3D blocks

Is fixed. but please don't ask when it happened ;).

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Hi there! 🙂

Deleted branch hotfix/T25882-CDash-v2.6.

Deleted branch release/T27695-2020-Week-36.

This is part of this issue (actually the main reason). It is already working in my local version but I have to make a few adaptions to get a stable minimum working version for production.

Pushed new branch release/T27695-2020-Week-36.

@kislinsk Currently the Dashboard, does not show the error or failed tests if you click on the Number in the table. Is this part of this issues or another one?

Fixed with D382.

I agree to @floca and I am quite sure this is related to installer vs. starting from build directory.

It is pretty weird since it even:

Remark: It could be releated to T26451 and caused by the same underlying problem.

Yes I'm using the normal desktop workbench - no Docker involved :)

should be solved with T27294

report() gains new argument fig.format to specify figure output formats in case of clean=FALSE.
can be vector, e.g. fig.format=c('jpeg','png', 'pdf'), then 3 files are stored for each figure

In T27669#208866, @gaoh wrote:

As I understand @schererj he is not using a MITK container but the binaries from the MITK-nightly build.

I have checked it with the todays nightly build of MITK from CI. So this does work.
@schererj Could you give some details on what binaries you have used?

actually it was

@eisenman worked at least for one test data set. I guess this can be closed

In T27669#208859, @floca wrote:

I have checked it with the current develop head under linux (Ubuntu 18) as well. I cannot reproduce the descibed error. Everything is loaded into one volume.

@gaoh May it is an outdated MITK container?

new function dendrogram(), also handles more informative titles ( T27411 ).
also updated in report

I have checked it with the current develop head under linux (Ubuntu 18) as well. I cannot reproduce the descibed error. Everything is loaded into one volume.

@eisenman could affect tests. please close when finished

@eisenman could affect tests. please close when finished

@eisenman please close when finished

if at least one quarter of cases have a duplicate, the error message is extended by "Or are you considering a multi-task challenge and forgot to specify argument 'by'? "
Otherwise the error message is now further improved, e.g. if it is a single task, the error message doesn't mention "in task dummyTask any more".
Example error message:

In T27094#208813, @thomass wrote:

2. That is rather a bug, because in Phenotyping there is a reference that shouldn't be there, maybe we can remove that.