[Paraview-developers] ParaView & Mangled Mesa (also Ice-T)
Berk Geveci
berk.geveci at gmail.com
Wed Oct 5 15:46:51 EDT 2005
I can think of 2 use cases:
1. ParaView has to be compiled twice, one for client (hardware
OpenGL), one for server (Mesa). From a ParaView user:
" In the meantime, I have to build two versions of ParaView for each
of our platforms, one with OSMesa for offscreen rendering and one
without Mesa for onscreen rendering. A fix for mangled mesa would
greatly simplify this process."
2. It is not possible to run paraview (mpirun -np N paraview) and have
offscreen on all nodes but first.
Neither of these use cases are important to me as a user. I have
something like 5 versions of paraview built anyway :-) As for use case
2, one can simply run client/server.
-Berk
On 10/5/05, Wylie, Brian <bnwylie at sandia.gov> wrote:
> Can someone elaborate on the exact use case for this?
>
> I'm not sure exactly what problem this bug is suppose to address?
>
> If you want off-screen rendering why not just compile with Mesa. Is
> there a use case where you want to 'switch' between onscreen and
> off-screen?
>
> My vote is skip this until we get some more information.
>
> Brian Wylie - Org 9227
> Sandia National Laboratories
> MS 0822 - Building 880/A1-J
> (505)844-2238 FAX(505)845-0833
> ____ _ __
> / __ \____ _________ | | / (_)__ _ __
> / /_/ / __ `/ ___/ __ `/ | / / / _ \ | /| / /
> / ____/ /_/ / / / /_/ /| |/ / / __/ |/ |/ /
> /_/ \__,_/_/ \__,_/ |___/_/\___/|__/|__/
>
> Unleash the Beast
>
>
> > -----Original Message-----
> > From:
> > paraview-developers-bounces+bnwylie=sandia.gov at paraview.org
> > [mailto:paraview-developers-bounces+bnwylie=sandia.gov at paravie
> w.org] On Behalf Of Berk Geveci
> > Sent: Wednesday, October 05, 2005 1:08 PM
> > To: Moreland, Kenneth
> > Cc: ParaView Developers
> > Subject: Re: [Paraview-developers] ParaView & Mangled Mesa
> > (also Ice-T)
> >
> > Ouch. Any suggestions? Do we go down the path of adding
> > mangled mesa support to IceT? Otherwise, we have to give up
> > on mangled mesa alltogether (which would make my life sooo
> > much easier :-) ). We would still have an offscreen rendering
> > solution. Except, the same executable wouldn't be able to
> > switch between the two.
> >
> > Moreland, Kenneth wrote:
> > > It sounds like the problem may be even worse than that. The IceT
> > > libraries themselves make direct OpenGL calls. So even if all VTK
> > > classes used mangled mesa correctly, IceT would still be using the
> > > unmangled OpenGL.
> > >
> > > -Ken
> > >
> > >
> > >>-----Original Message-----
> > >>From:
> > >>paraview-developers-bounces+kmorel=sandia.gov at paraview.org
> > >>[mailto:paraview-developers-bounces+kmorel=sandia.gov at paraview
> > >
> > > .org] On Behalf Of Berk Geveci
> > >
> > >>Sent: Wednesday, October 05, 2005 12:38 PM
> > >>To: ParaView Developers
> > >>Subject: [Paraview-developers] ParaView & Mangled Mesa (also Ice-T)
> > >>
> > >>
> > >>I was tracking down bug #1784. After fixing a problem with
> > the command
> > >>line arguments, I still couldn't get it to work.
> > >>Digging into the code further, I found that the problem is the fact
> > >>that paraview creates a vtkIceTRenderer on the server.
> > vtkIceTRenderer
> > >>is a sub-class of vtkOpenGLRenderer and does not support
> > mangled mesa.
> > >>The only way I can think of fixing this problem is to create a
> > >>vtkMesaIceTRenderer (a al vtkMesaRenderer) and delegate the
> > >>instantiation of IceT renderer to a factory. Any comments?
> > Volunteers?
> > >>
> > >>-Berk
> > >>
> > >>_______________________________________________
> > >>Paraview-developers mailing list
> > >>Paraview-developers at paraview.org
> > >>http://public.kitware.com/mailman/listinfo/paraview-developers
> > >>
> > >>
> > >
> > >
> > >
> >
> > _______________________________________________
> > Paraview-developers mailing list
> > Paraview-developers at paraview.org
> > http://public.kitware.com/mailman/listinfo/paraview-developers
> >
> >
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
More information about the Paraview-developers
mailing list