Dec 9 2022
Nov 30 2022
Nov 25 2022
Discussion result: nice to have wären auch die Informationen des "first pass" (-> welche reader configuratoin, findet wieviele volumes und welche Dateien werden verwendet) schön.
Oct 10 2022
Sep 21 2022
To make our live a bit easier. I would say it is a data problem ;).
oh so I forgot to send it: But this is, what my browser had cashed: "Yes, so I recently tested it, with the current release."
But also, if I remember correctly, this was due to the Phantom dataset we have as the default dataset:
I removed a few slices at the end, and now it is working.
Sep 15 2022
Aug 11 2022
Jul 22 2022
ok, but then the GPU problem is also feasible! If it is for a pre-known time-limited usage, like in an interactive session, I don't see a problem assigning a GPU to the container.
If you have a bunch of data, then the airflow workflow is the way to go.
To point 1, in Kubernetes you can mount any path/volume to the desired mounting point. So I could just mount the directory in the MITK container in e.g. /models
Jul 18 2022
Jul 11 2022
Jun 15 2022
Jun 1 2022
May 17 2022
yes, that will help. Also, this worklist will be quite helpful, allowing a new form of "batch-processing".
May 16 2022
Yes, so I changed it already, and I am using the seriesUID as name for the images. Additionally, I had to add the layer property: Because by introducing the image name property, somehow the layer is also set (to a high number, probably). When I create a new SEG without setting the layer of the image to 0, the SEG is only put on top, when opening the data manager.
May 13 2022
@gaoh Would you be so kind and verify that the problem still exists? Thanks.