Ah it seems I was mistaking, at least the transparent overlay works, the color mismatch remains.

Ah, when changing the Preference of Segmenation, the mask is changed... How can I create a "Multilabel Mask"?

Yes, it is exactly as you described: static -> all timesteps, dynamic -> toolbox to apply to all timesteps or not.

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

yes exactly, the problem with the scripted version, ist still, that it is necessary to provide credentials. That was fine, as long we were the only ones creating the containers.
The version of @nolden downloading the packages in ubuntu allows others to just build the container, without having to provide credentials at all.

Oh I forgot to mention: the segmentation is saved as dicom-seg.

We need a dataset to reporduce the problem, to setup a testsetup.

So I tested it with Orthanc (without CGET only):
With 2018.04.2 retrieve works. With the current develop branch MITK crashes with the same exception:

Have you checked, if the dataset (or the slices) are already in the PACs. In my case (I got the error, when sending data from airflow to the PACs), the files creating the 409 were already in DCM4CHE.

Oh sorry, I thought it was clear, because the title is wDB related:
I used the wDB. I did not test it with a different PACs system, but I can try and report back...

In T27573 we discussed the problem of data transfer from CTP to DCM4CHE.
So basically it is a kind of similar problem: A datatransfer between CTP and DCM4CHE fails.
The problem is then, CTP just keeps the data in the queue (here) or inserts in the quarantine folder (T27573).
Anyway, we do not get notified, that there is a problem.

So for the current develop:
With or without CGET activated. When trying to Retrieve a dataset after Query, I get an Exception:

The CTP thread responsible for sending the data to the PACs crashed:

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?

Is this the correct module? https://docs.mitk.org/2018.04/org_mitk_views_cmdlinemodules.html ? Or is there another command line tool?

@gaoh: Can you tell what you mean by dynamic mask?

File is correctly saved in the current master.

then build package target in MITK build.

@kislinsk what do you mean with this? Is it just the "normal" process, aka cmake and make in MITK-build. Or do I have to configure something additionally?
I tried the normal way and got also the "normal structure": with a bin, lib, Modules etc folder. Whereas when I download the release 18.04, the libraries are directly packed into the bin folder?

If the "base", the image, is in dcm, and not a nrrd file (which is the case in dcipher, when pulling the images from the PAC), the Segmentation can be saved as DICOM. The created file can be saved in a mounted folder and can then be directly imported via airflow into the pacs.
Directly sending data from MITK to the PACs is not recommended, because otherwise the metadata is not extracted and the segemtation cannot be triggered via kibana!

I reproduced it with the "Installer".

[63.469] Writing image: /home/hanno/mitk/seg.dcm
Input image size: [512, 512, 7]
CodeSequence Exception: missing value in code sequence
#63.470# ERROR: An error occurred during writing the DICOM Seg: JSON Exception: file could not be read.

I just tested it, it works!

The current way in the dicomweb-plugin is for GET, is to use with IHE (Invoke Image Display style).
The data is downloaded in a local temp folder (via SendWADO). And the data is then imported to the datanode via mitk::IOUtil::Load()
So basically, apart from listening to incoming IHE GET requests, it is only a DicomWeb client.
But this could be nice, to use MITK also a DicomWeb server. This Rest API could be used to build a wrapper around.
Also, it could be nice in the current implementation of loading the data to use this.

This issue is not wDB related, but MITK related:
Query with CGET activated and then Retrieve:
Retrieve does not work, MTIK directly shows:

Still valid, but still part of the checklist!

Still not working, but still part of the checklist!

This does still not work (Retrieve from wdB fails, when going throw the "Checkliste DICOM Browser".
I have to look into this.

still not working, but it is part of the checklist "ViewNavigator"

A two step build also works:

The log entries don't tell me a lot, basically I thing for every file it writes: ERROR: setting value to 0
Just in the end, before the termination the log entries change to:

Point 1 and 2 are working.
With point 3: not all the series are downloaded: I retrieved all 5 series of a patient, but only got 2 series. Separately retrieving of each series was fine.

yes I will try, I already tried Q/R with the current installer and the wdb and it worked.