Pushed new branch T26060-AddBandpass.

There seems to be another exception thrown when willing the table view. The statistics table is not filled. The idea is now not to change the GetStatisticsForTimeStep functionality but handle the exception in the level above (like we started before with the try-catch)

@hentsch / @kislinsk : Shouldn't we already set QmitkPlotDialog/QmitkPlotWidget/QtHistogram to deprecated then. To give us sooner then later the posibilite to realy remove the code from the codebase. If I see it correctly, that would also gives us the possibility to reomive Qwt as a third party package from MITK. What do you think?

@kislinsk Do you have any opinion regarding this issue ?

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.

Pushed new branch T26311-temporaryFix.

Hi,
after updating my graphics card driver to the newest available (430.39) the issue still exists. I will check on VTK side next and see if it is related to it.
Thanks,
Ingmar

Keep in mind:

Reopened to revert the latest changed due to errors.

In T26237#180471, @kislinsk wrote:

@maleike NV210? According to google this GPU was released in 2003.

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