HI Peter, MITK (2018-04-4) the the current milestone. I nearly missed this task as you put it in the already archived milestone MITK (2018-04). The safest way to raise awareness is to just set the task priority to Needs Triage and stick with the MITK tag. ❤

I think it is not the best idea to get rid of ICU as it has its purpose regarding Unicode handling. If building or finding ICU interferes with an installation of Anaconda, there are probably other ways of telling DCMTK through CMake to behave as expected.

Thank you for the feedback! 👍

HDF5 1.10.5 does not work at least with ITK 4.13, so upgrading HDF5 would probably result in an upgrade cascade that is not appropriate for a minor release. Hence I removed the 2018-04-4 milestone tag.

Closing these tasks because of inactivity and completely changed way of building MITK.

Closing these tasks because of inactivity and completely changed way of building MITK.

Closing these tasks because of inactivity and completely changed way of building MITK.

Was never merged into master, what shall we do, @franza ?

Close as resolved because of last activity was three years ago.

Pushed new branch T26356-MisalignedRenderWindowFrames.

Frame is encapsuled by vtkMitkRectangleProp class.

Thank you! 👍

Pushed new branch T24860-LevelWindowInitLocation.

Okay, so not the 2018.04 branch.

I'm totally in for Boost 1.69+. The interesting question for me is, does this issue affect the 2018.04 branch as well or only the master branch?

I guess we could reasonably choose the selected/active 2d window but that might be sometimes different to the users working plane as it is simply defined by the window that was clicked the last time.

@kausch What's the status on this task?

Pushed new branch T26252-BoostInstallError.

I really tried but I was not able to reproduce this issue. For example, I created a segmentation and clicked multiple times on "Create smoothed polygon model" and "Create polygon model". Worked every time. I then created another segmentation in the same scene and did the same there with the same results.

To get an overview of MITK subprojects:

Pushed new branch T25882-CDash-v2.6.

Things I found so far:

I also checked on my notebook from 2011 with a GeForce 540M and I have similar framerates compared to @maleike. I also checked all the different GPU load indicators with GPU-Z and messing around in the 2d views does not trigger such an old GPU to even yawn. CPU is also not sweating so I guess it could be something related to memory access or transfer.

@maleike NV210? According to google this GPU was released in 2003. I'm surprised that you can see anything at all as OpenGL 3.x was released between 2008 and 2010. As you guys have quite powerful CPUs and lots of RAM I guess you have rather recent workstations except the GPUs. Is there a specific reason to stick with such old GPUs? No offense here, it's just noticable. You get a HUGE performance boost even with a silent low-end GTX 1050 without extra power supply for around 140 €.

@wegner It's the Nvidia screen recording which comes right with the driver resp. GeForce Experience application and utilizes the GPU directy to record the screen content. Not sure if it works with a 2012 GPU, though.

My bet is on the "new" OpenGL 3.x rendering backend of VTK as we didn't change anything else in this area of MITK in the past years. Especially non-mainstream GPUs from around 2011-2012 are the ones which tend to somehow work but not in a satisfactory way regarding OpenGL 3.x. Unfortunately Nvidia doesn't continue to provide current drivers for GPUs this old as far as I know which would be usually my first advise to check.

Thanks for measuring! I downloaded the latest zip installer and roughly did what I think you did as well. Recorded at 1080p @ 60 Hz, encoded in 720p (same H/W as mentioned in my last post). I think this is completely different from your experience, right?

Please do not merge these MITK_INFOs in the REST moduels into the master. Currently, they can be considered noise. We can discuss a few more MITK_INFOs but then with more actual information.

No, I think in 2018.04 we even do not have SimpleITK anymore. So, closing as Invalid eventhough it was valid back then.

Do (2).

We all agree on the proposed solutions. We want to collect all segmentation related tasks in a a Segmentation project/tag.

Status quo:

• binary and segmentation is set for legacy segmentation images that were created with our segmentation tools. binary is always set even the legacy segmentation was not created in MITK.
• Both properties are also set for the current segmentation image type which isn't necessary in theory because the image type would be enough.

Also regard discussion of T25963 for helper for segmentations.