This is an MITK bug. Daniel Maleike put together a demo that demonstrates
this performance weakness in the branch

personal/maleike/render-perf-demo

I, too, am interested in ways to address this issue.

Taylor


On Fri, Aug 8, 2014 at 9:36 AM, Clarkson, Matt <[email protected]> wrote:

> Hi there,
>
> I would like to render a plane of live image data, and visualise it in a
> 3D window at a given position in space.
>
> I looked through the code, and saw that in the MITK Display, the Axial,
> Sagittal, Coronal slices are mapped to a plane, which ultimately gets
> rendered using mitkGeometry2DDataVtkMapper2D and
> mitkGeometry2DDataVtkMapper3D.  So, I tried creating a 2D image
> (ultrasound/video/whatever), using a 2D MITK Render Window to visualise it,
> and then it also appears in the 3D world.
>
> Then I tried moving it about by changing the geometry on the image.
> Then I tried updating the image.
>
> However, when profiling code I realised that the rendering performance is
> quite slow. The slowest part is rapidly updating the OpenGL Texture Map
> containing the image data.
>
> Is there a better or more recommended way to achieve the same effect?
>
> Thanks
>
> Matt
>
>
>
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> mitk-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mitk-users
>
------------------------------------------------------------------------------
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to