My suggestion would be to fix this with this separate differential because the error also makes the nightly builds fail and we don't need to wait for your large differential to be accepted.

This has also been adressed in D568 since the problem turned up there in the CI builds. Should we still solve it in D582 separately or just wait until D568 can be landed?

A new PhD student who is starting in February will work on MITK Diffusion again. He will also look into this.

Yes, I compared both versions of our application; based on MITK 2018.04 and 2021.02. I understand that's it's not a perfect comparison, as there are several other changes between those versions, but it's the best I can do right now.

Hi Nil. Thank you for testing! Did you directly compare the dataset performance with the old shader version? Just to make sure it's actually an issue with the clipping planes.

Hi Peter, thank you for the quick fix. I finally took the time to test... 2 months later :)

I think related to this task: it seems there is some more inconsistency depending on the shown region. When two images with different geometries are loaded and shown simultaneously after a global reset, planarfigures created on one of the images can extend into the whole shown region, outside the boundaries of the selected reference image (even after a reset on that specific image).
It seems in this case the boundaries for the planarfigure are set incorrectly on creation.

I can't reproduce the problem mentioned for the mapper plugin on v2021.10 . The moving / target information appears in the properties, just as in a registration created via the Algorithm Control plugin.
Can somebody reproduce this (or a related) problem? Otherwise I guess the task was already solved somewhere else and can be closed

We did the draft together, but it was not implemented into Hyppopy yet.

https://phabricator.mitk.org/source/kaapana/history/feature%252FT28913-myeloma-kaapana/

@gaoh @floca I subscribed you so that you known where to find it, if the question comes up. At the moment there is no open todo on this front.

I am removing myself as an assignee. I just reported this.

This task is still open and still on the workboard. I am removing myself as an assignee, what I did was basically reporting and a bit of investigation as written above.

@kahl I assigned you. If I understand correctly, this is what you did for the new add tool and the new base class.

@kahl Again, I assigned you, this is in the context of the new add tool.

There is already a pull request for CTK that fixes this issue. I commented on it. Nothing to do from our side I guess.

@kahl I hope it is ok, that I assigned you, since you are working on this anyways.