The task as such is resolved. Another task with open questions from D279 is created with T28466

Fixed the task policy :D Did you get acces to it ?

@eisenman the change in develop branch has not been uploaded to GitHub, is this not automatically synchronized?. So the user who reported the bug still has the same problem. It would be good to merge into master as well

In T27437#223356, @al-sabr wrote:

Can this also be matched with this other task I created?

https://phabricator.mitk.org/T28454

I only need help in one place if that part is cleared then I already refactored the Core to reflect the changes suitable for version 3.6.0 of CppMicroServices.

I will put this up for grabs as it does not make sense to start a new project now. Personally I will investigate further after the Conan evaluation report has been written.

One long term solution would also be to create an own Litmus Conan recipe and use this external Litmus package inside MatchPoint.

I was trying to test if I can forward the ITK_USE_FILE variable inside the ExternalProject call to Litmus, as we did in the change for the CMAKE_PREFIX_PATH. I realized that neither the CMAKE_PREFIX_PATH nor the ITK_USE_FILE is correctly forwarded and accessible inside Litmus CMake configuration.

now test case in test-report.R

I started looking into this and some changes need to be made in order to get some errors out of the way:

• Conan-center recipes are built without CMake find / config files, as mentioned here: In short: Conan creates own find / config files so they are removed from the original package.

Do you have a minimum example to reproduce this? Would be great to have that in the test checklists as well.

Pushed new branch to rMITK MITK: bugfix/T28437-RegionGrowing3DSeedPoint0.

very simple fix in rankingHeatmap.challenge
@eisenman can this be merged into master branch?

could you make an arc diff. Then it is easier to review and comment in code. Thanks.

Could be solved by @kislinsk suggestion to change rendering mode to LOOKUPTABLE_COLOR to not envoke the levelwindow to overwrite the range

I set the priority to high because we defined that having appropriate data at a reachable location is one of the most pressing issues when it comes to manual GUI tests.

Can this also be matched with this other task I created?

Changes are pushed into the new branch T28353-cmake_faq branch.

Pushed new branch to rMITK MITK: feature/T28354-cmake_faq.

In T27437#223241, @al-sabr wrote:

Is this task finished or if not when is it planned?

Pushed new branch to rMITK MITK: feature/T27437-ITK-v5.1.

Thanks

Your argument makes sense to me. I did not have a specific order in mind when implementing it, so I do not have any counterargument here.

Is this task finished or if not when is it planned?

Forgot something and didn't request review correctly. I will open this one agian.