Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-07 Thread Utkarsh Ayachit
n Su <simon.m.su....@mail.mil>, > ParaView <paraview@paraview.org> > Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader > (UNCLASSIFIED) > >> Utkarsh - I was able to get a clean build with this OSMesa patch - but it >> looks like the OSMesa pvserver is

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-07 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
yac...@kitware.com> Date: Tuesday, June 7, 2016 at 11:30 AM To: Rick Angelini <richard.c.angelini@mail.mil> Cc: "Hennessey, Joseph G CTR USARMY RDECOM ARL (US)" <joseph.g.hennessey2@mail.mil>, Simon Su <simon.m.su@mail.mil>, ParaView <paraview@paraview.org> Sub

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-07 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
2@mail.mil>, Simon Su <simon.m.su@mail.mil>, ParaView <paraview@paraview.org> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED) > Utkarsh - I was able to get a clean build with this OSMesa patch - but it > looks like the OSMesa pvserver is not

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-07 Thread Utkarsh Ayachit
> Utkarsh - I was able to get a clean build with this OSMesa patch - but it > looks like the OSMesa pvserver is not compatible with the production 5.0.1 > client?? That's not the case. It should be compatible, so long are you're building 5.0.1 on the server side too. >

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-07 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
G. Hennessey Ph.D., Lockheed Martin >> Army Research Lab >> DOD Supercomputing Resource Center >> >> >> -Original Message- >> From: Utkarsh Ayachit [Caution-mailto:utkarsh.ayac...@kitware.com] >> Sent: Thursday, June 02, 2016 4:19 PM >> T

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-06 Thread Utkarsh Ayachit
t; Army Research Lab >> DOD Supercomputing Resource Center >> >> >> -Original Message- >> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com] >> Sent: Thursday, June 02, 2016 4:19 PM >> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US) >>

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-06 Thread Utkarsh Ayachit
ennessey, Joseph G CTR USARMY RDECOM ARL (US) > <joseph.g.hennessey2@mail.mil> > Cc: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) > <richard.c.angelini@mail.mil>; Su, Simon M CIV USARMY RDECOM ARL (US) > <simon.m.su@mail.mil>; ParaView <

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-06 Thread Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
Su, Simon M CIV USARMY RDECOM ARL (US) <simon.m.su@mail.mil>; ParaView <paraview@paraview.org> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, a

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-03 Thread Utkarsh Ayachit
> Would it be sufficient to change the cmake flags OSMESA_INCLUDE_DIR and > OSMESA_LIBRARY in CMakeCache file to point to the external build of Mesa > 11.x.x? Pretty much (and setting a few other vars to empty including OPENGL_gl_LIBRARY etc, see the arguments to add_extra_cmake_args() call in

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-03 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
.@mail.mil>, ParaView <paraview@paraview.org> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-02 Thread Utkarsh Ayachit
> And I have tried replacing the library > lib/paraview-5.0/libOSMesa.so.7 > with both libOSMesa.so from 11.1.2 and 11.2.2 > and they are both still giving the same error Simply swapping the libraries won't work. Mesa 11.2 [1] added new API OSMesaCreateContextAttribs() which is needed to create

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-02 Thread Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
c: ParaView <paraview@paraview.org> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED) All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copy

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader (UNCLASSIFIED)

2016-06-02 Thread Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
) CIV USARMY RDECOM ARL (US) Sent: Thursday, June 02, 2016 1:45 PM To: Utkarsh Ayachit <utkarsh.ayac...@kitware.com> Cc: ParaView <paraview@paraview.org> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader All active links contained in this email were disabled. P

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-06-02 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
i, Richard C (Rick) CIV USARMY RDECOM ARL (US) > <richard.c.angelini@mail.mil> > Cc: Chuck Atkins <chuck.atk...@kitware.com>; ParaView > <paraview@paraview.org> > Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader > > Ah okay. Give me a few days to sort it o

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-06-02 Thread Utkarsh Ayachit
ard.c.angelini@mail.mil> > Cc: Chuck Atkins <chuck.atk...@kitware.com>; ParaView <paraview@paraview.org> > Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader > > Ah okay. Give me a few days to sort it out. The end goal is indeed to have > superbuild b

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-06-02 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
) <richard.c.angelini@mail.mil> Cc: Chuck Atkins <chuck.atk...@kitware.com>; ParaView <paraview@paraview.org> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader Ah okay. Give me a few days to sort it out. The end goal is indeed to have superbuild build the right versio

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-06-02 Thread Utkarsh Ayachit
angelini@mail.mil> > Cc: Chuck Atkins <chuck.atk...@kitware.com>, ParaView > <paraview@paraview.org> > Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader > > All active links contained in this email were disabled. Please verify the > identity of th

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-06-02 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
-Original Message- From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com> Date: Thursday, June 2, 2016 at 8:37 AM To: Rick Angelini <richard.c.angelini@mail.mil> Cc: Chuck Atkins <chuck.atk...@kitware.com>, ParaView <paraview@paraview.org> Subject: Re: [Paraview] [Non-DoD

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-06-02 Thread Utkarsh Ayachit
> So there is much more to be done than adding > -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 > -DVTK_RENDERING_BACKEND:STRING="OpenGL2" > to the cmake flags? As far as ParaView is concerned, no there's not much more to it. However if your OpenGL implementation doesn't support OpenGL 3.2 (released

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-06-02 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
--Original Message- From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com> Date: Wednesday, June 1, 2016 at 4:28 PM To: Rick Angelini <richard.c.angelini@mail.mil>, Chuck Atkins <chuck.atk...@kitware.com> Cc: ParaView <paraview@paraview.org> Subject: Re: [Paraview] [Non-D

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-06-01 Thread Utkarsh Ayachit
elini > <richard.c.angelini@mail.mil> > Date: Wednesday, June 1, 2016 at 3:59 PM > To: Utkarsh Ayachit <utkarsh.ayac...@kitware.com> > Cc: ParaView <paraview@paraview.org> > Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader > > All active lin

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-06-01 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
esday, June 1, 2016 at 3:59 PM To: Utkarsh Ayachit <utkarsh.ayac...@kitware.com> Cc: ParaView <paraview@paraview.org> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader All active links contained in this email were disabled. Please verify the identity of the sender, an

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-05-31 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
Utkarsh - thanks for info.Recompiling the server-side with OpenGL2 resolved the problem! Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -Original Message- From: Utkarsh Ayachit

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-05-27 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
Utkarsh - thanks for the info. I believe that you’re right that the build didn’t go as intended. Rick Angelini USArmy Research Laboratory CISD/HPC Architectures Team Phone: 410-278-6266 -Original Message- From: Utkarsh Ayachit

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-05-27 Thread Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
Yep - we built the HPC-side with “OpenGL2” … so does that mean that the pre-built Mac/Linux binaries were both built with OpenGL?Is there some way to check to see which OpenGL the client was built with? Rick Angelini USArmy Research Laboratory CISD/HPC

Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

2016-05-27 Thread Utkarsh Ayachit
> Yep - we built the HPC-side with “OpenGL2” … so does that mean that the > pre-built Mac/Linux binaries were both built with OpenGL?Is there some > way to check to see which OpenGL the client was built with? The binaries distributed by paraview.org are indeed OpenGL2. The title bar for