@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.

(Didn't see latest comments from yesterday evening, was typing the following while only the initial comments of Stefan were visible in my browser)

Wow, that looks nice!
No, that's not what I have seen on my desktop, or a laptop or a Windows virtual machine, that used to work well with the older MITK version (2016.03.0).
I will check on a recording solution (which one did you use?) and do the same on my side...

By the way, the test system was on Windows 7!

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?

Hi,
measurements on my side
mitk v2018.04.2 (zip downloaded from webside) with pic3d.nrrd (106.478KB), a fresh generated binary dataset and with Segmentation Add Tool (NVIDIA Quadro K5000, Full HD resolution, 60Hz refresh rate, three displays connected, Intel Xeon E5-2687w 3,4GHz (2 processors, 32cores in total), 64 GB RAM (I admit, a few years old, but still better than any standard PC ;) )
->measured with fraps
2d widgets: 20 Hz, going down over time
3D widgets: 60Hz, stable over time as no segmentation interaction is going on.

Pushed new branch T25941-Improve_mapper_view_user_manuel.

@kislinsk Thanks for the hint.

It can be integrated and used in a plugin when the frmgrab.dll and frmgrab.lib files were in the same folder (\Epiphan\epiphan_sdk-3.30.3.0007\epiphan\frmgrab\lib\win\x64)

Would be good to leave the baseRenderer as an argument so that you can set the visibility of a specific node in a predefined base renderer (e.g. by using the RenderWindowManager). This is useful when using the new MultiWidget(Editor).

Pushed new branch T19683-ShowOnlySelectedNodesCrosshairVisibility.

I have concerns with the latest commit. See comments there. You can come by and ask if you have any questions.

The fix is not good and has several problems. See comment above. If it is not clear how to handle it properly, just drop by an I can explaine.

No longer relevant

Solution: GetStatisticsForTimeStep method now returns an empty StatisticsObject if no mask is provided for this time step. Thus, histogram and table are empty for those time steps.
Discussion: 1. 4D image + 3D segmentation

2. 4D image (5 time steps) + 4D segmentation (1 time step)

@hentsch Is the one time step segmentation applied to all time steps? What is the expected behavior?

There is a setup option for .run_test, just set that to False

Pushed new branch T26029-4DImageAnd4DSegmentation.

@kislinsk Stefan, you said you reworked this pragma for MITK? Does it implie any changes for 3rd party projects?

In rMITK0d470ff3225f4982b7e2f6281b862948de2c55a7#137546, @kislinsk wrote:

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.

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.

Pushed new branch T26060-MITK-PhotoacousticsBFToolIPPAI.