[Paraview] [Non-DoD Source] Building Paraview with OSMESA

Wed Sep 14 14:28:02 EDT 2016

Chris - Yeah, so I’m also not sure how Catalyst might be firing this up.
Here’s an example OS_Mesa/cmake command used on one of our generic RHEL6
systems.   With this build, we throw the “—use-offscreen-rendering” flag
when we fire up the pvserver.    I think that the critical flags are
“osmesa=ON, mesa=OFF, qt=OFF” …..   Can you use your current build in a
traditional client-server configuration to verify that the OS_Mesa is built
correctly?      That might make it easier to narrow down to a build issue or
a Catalyst issue.   Just a thought.

cmake 
-DCMAKE_INSTALL_PREFIX:PATH=${HOME}/pv/${paraview_version}${build_extension}
\
-Ddownload_location=`pwd`/../Downloads \
-DParaView_FROM_GIT=OFF \
-DParaView_URL=`pwd`/../Downloads/ParaView-v${paraview_version}-source.tar.g
z \
-DCMAKE_BUILD_TYPE=Release \
-DENABLE_boost=ON \
-DBoost_NO_BOOST_CMAKE:BOOL=ON \
-DENABLE_visitbridge:BOOL=ON \
-DENABLE_cgns=ON \
-DENABLE_ffmpeg=ON \
-DENABLE_hdf5=ON \
-DENABLE_matplotlib=ON \
-DENABLE_osmesa=ON \
-DENABLE_mesa=OFF \
-DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2 \
-DENABLE_mpi=ON \
-DUSE_SYSTEM_mpi=ON \
-DENABLE_numpy=ON \
-DENABLE_paraview=ON \
-DENABLE_python=ON \
-DENABLE_qt=OFF \
-DENABLE_silo=ON \
-DENABLE_szip=ON \
-Dqt_DISABLE_WEBKIT=ON \
-DMPI_CXX_LIBRARIES:STRING="-L${MPI_HOME}/lib -lmpi_cxx -ldl" \
-DMPI_C_LIBRARIES:STRING="-L${MPI_HOME}/lib -lmpi -ldl" \
-DMPI_LIBRARY:FILEPATH="-L${MPI_HOME}/lib -lmpi_cxx -ldl" \
../Source
________________________________
Rick Angelini
USArmy Research Laboratory
CISD/HPC Architectures Team
Phone:  410-278-6266

From:  Christopher Neal <chrisneal at snumerics.com> on behalf of Christopher
Neal <chrisneal at snumerics.com>
Date:  Wednesday, September 14, 2016 at 1:44 PM
To:  Rick Angelini <Richard.C.Angelini.CIV at mail.mil>, Benson Muite via
ParaView <paraview at paraview.org>
Subject:  Re: [Non-DoD Source] [Paraview] Building Paraview with OSMESA

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 copying and pasting the address to a Web
browser. 

Thanks Rick!

I’m running OpenSuse 13.2 64bit. I’m not explicitly starting a pvserver,
because I’m running one of the C++ Catalyst examples, which is located at
ParaView/Examples/Catalyst/CxxFullExample. That is mainly what is confusing
me. I’m not sure if I built ParaView with osMesa incorrectly, or if that
Catalyst example is somehow just telling ParaView ‘Hey, don’t use the
offscreen rendering stuff, just go ahead and keep rendering to the screen.”

I’m thinking that I should be able to test the offscreen rendering
capability independently of that Catalyst example by generating a Python
trace of a pipeline that creates an image output, and the running it with a
command like:
pvserver –use-offscreen-rendering TestScript.py

From: "Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)"
<richard.c.angelini.civ at mail.mil>
Date: Wednesday, September 14, 2016 at 1:24 PM
To: Christopher Neal <chrisneal at snumerics.com>, Benson Muite via ParaView
<paraview at paraview.org>
Subject: Re: [Non-DoD Source] [Paraview] Building Paraview with OSMESA

Stupid question – when you start up the pvserver process, are you passing it
the “—use-offscreen-rendering” flag?

mpirun –np 8 pvserver —use-offscreen-rendering …….

What’s your build platform?  I have lots and lots of build scripts I can
share!   

________________________________

Rick Angelini

USArmy Research Laboratory

CISD/HPC Architectures Team

Phone:  410-278-6266

From: ParaView <paraview-bounces at paraview.org <
Caution-mailto:paraview-bounces at paraview.org > > on behalf of Christopher
Neal <chrisneal at snumerics.com < Caution-mailto:chrisneal at snumerics.com > >
Date: Wednesday, September 14, 2016 at 12:44 PM
To: Benson Muite via ParaView <paraview at paraview.org <
Caution-mailto:paraview at paraview.org > >
Subject: [Non-DoD Source] [Paraview] Building Paraview with OSMESA

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 copying and pasting the address to a Web
browser. 

Hi All,

I’ve been trying to compile a version of ParaView that uses osMesa. I’ve
tried to follow the process that is explained on the wiki
(Caution-Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D
< Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D >  <
Caution-Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D <
Caution-http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D >  >  ),
but I haven’t been able to get ParaView to render offscreen. I don’t have
build errors, but when I run something that saves a screenshot I still see a
window pop up on my screen. Would anyone be willing to share their
configuration script/command that they use for compiling ParaView with
osMESA?  

Also – If I have a python script that creates a screenshot of some geometry,
do I need to edit it in any way before running it with a version of ParaView
that uses osMesa? Or is all of that handled behind the scenes?

Thank you,
Chris N

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160914/e5337c28/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5108 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160914/e5337c28/attachment.bin>