if the output is NULL, object[[by]] is not a factor, i.e. class(object[[by]]) is "character", in this case you need to use use unique() and probably your solution

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.

It is explicitly wanted by the spectral imaging time... and almost done....

Hi again,

In general yes, the behavior is correct if needed, but in this case it was caused by an incorrect/missing time point mapping between image and mask.

is this still an issue?

@s349i This should be also covered by your work, shouldn't it? If yes, please claim or merge with your working tasks.

What is here still open?

One difference that I saw: Two openssl-related files were added to the MITK-directory of the working version:

• libcrypto-1_1-x64.dll
• libssl-1_1-x64.dll

I met with Nikolas Stanczyk today and he showed me his working version of MITK, connecting to XNAT via the provided plugin. I also used my credentials and I was able to successfully login.
I copied his version to my laptop and here he was also able to login.
I just tested my credentials with this copy on my laptop and I was able to successfully login:

Thanks Emre!
Thats a weird change. I didn't find any mention in R changelog.
probably instead of

algorithms=factor(unique(object[[by]]))

it will be preferred

@gaoh could you join the discussion?
Also may be the worklist feature T29159 would be an additional way to circumvent it.?!?

@gaoh Would you be so kind and verify that the problem still exists? Thanks.

Congrats for tracing this down!

Finally, I could find the source of the bug. 😊 It is caused by changed output type of unique() function in R:Base from R-3 to R-4.

Is this the same (T29110, see description point 3) and specifically T29110#235991?
If so, I have a fix for the > layer 0 problem which can be tested and reviewed in D632.

What is the status here?

I expect a circle in the cross-hairs, akin to Shape: cross or vertex. But there is None. Is this expected behaviour?
@s434n is right. Vertex is almost invisible although exists.

Close this task. The successor for our current planned implementation is T28524.