It really depends. I totally agree that it is not necessary for routine jobs, however it comes in really handy for controlling the data on remote locations were executing MITK is not possible/forbidden. That's why it had been build in.

I think I fixed the OpenCV Ant issue by updating the volume snapshot for our Ubuntu 20.04 cloud instances to include the environment variable ANT_HOME=/usr/share/ant.

@eisenman I dont understand this task, could you give an example?

solved in T27338

networks should be replaced by some ggplot2 implementation, see
https://journal.r-project.org/archive/2017/RJ-2017-023/RJ-2017-023.pdf

lists of ggplot objects can now be handled like single ggplot objects, e.g. boxbplot(...) + xlab(...) will apply xlab() to every ggplot object

comes from significanceMap.data.frame

now as.challenge() as well as report contain extended information on missings and automatically inserted test cases.
@eisenman this changes the tests for as.challenge. Could you please 1. check whether the messages are well phrased and then 2. adapt tests, then 3. close task. Thanks!

I have checked with a prototyp to just move also the core of the generator to an own thread. It helps to make the UI more responsive. BUT it is not enough because the UI (workbench) thread and all other threads must kept seperated, using Qt mechanisms, we need to use a lot of signal/slot and this seems to keep the UI thread (event loop) very bussy.

Pushed new branch bugfix/T25882-RewriteDashboardScript.

Deleted branch bugfix/T25882-RewriteDashboardScript.

@goetzm Does the GIF mini app realy need the screenshot feature within the app (there is also a CLScreenshot app)?
Reason for the question is, that this feature is the only reason why Qt becomes dragged into the app and it bloats the container/deployment. Just wanted to now if we can the keep the configuration as slim as possible.

@schererj Do you mean the XML result export?

Yes, they are in the workspace of the Nightlies but I hesitate to provide them externally as they have a bunch of problems. Besides the DICOM-loading problem that we currently have with the installers in general, the macOS MITK Workbench from the installer is not executable by clicking on the MitkWorkbench.app. One have to use the terminal, cd into the package and execute the actual MitkWorkbench executable.

now
e.g. if FUN="mean" (i.e. a character) or if FUN=mean (i.e. a function)
the column name will be "value_mean"

If looked a bit closer. The time information is encoded in Tags of the MultiFrame and the CINE module.

Remark regarding option 4:

@kleesiek thanks for the reminder after summer break.

@kislinsk can we currently produce MacOS Installer via CI? This would be the easiest way to provide a current installer for jens to test.

In T27570#206547, @kleesiek wrote:

• 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

Yes you are right. I thought to much in the lines of CAMIs work.

@eisenman error message might have changed, please check tests

@eisenman seems to come from "Blob plot similar to the one shown in Section \ref{blobByTask}" in visualizationAcrossTasks.Rmd. Could you please take care of it, you are more familiar with the restructured report

Closed with changes of D398 as discussed: Remark for developers.

I couldn't identify any differences between the latest develop branch and my installed MITK v2018.04.2.

Do you know when it worked the last time? What do you want to rewrite - I don't see any reference to the 3D window.

The Photometric Interpretation tag (0028,0004) of the Philips US image is set to YBR_FULL_422 and my first guess is that we do not take this tag fully into account, leading to a misinterpetation as RGB values while reading the data.

In T27669#209003, @floca wrote:

@kislinsk As a linux noob please pardon my question. Can we directly debug the nightly bild by the CI on e.g. Jonas system? I would like to see some of the parts of volume generation process running to see whats happening. My be it helps us getting a lead. At least we now a setup directly on site that makes the problems.

Closed as all sub tasks relevent for MITK2020 are checked and corrected.

Another addition for the documentation:

It is rooted in an known unfixed error in itk: https://discourse.itk.org/t/crash-in-watershedimagefilter/2428

Any update on this issue?

@kislinsk @kalali I have in mind that you recently had a look at the ClippingPlane. Since the clipping plane does not show the expected behavior, does it make sense to rewrite the documentation for it? I have in mind you even considered to declare it deprecated.