<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Title content=""><meta name=Keywords content=""><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body bgcolor=white lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt'>Thanks Rick!<br><br>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.”<br><br>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:<br>pvserver –use-offscreen-rendering TestScript.py<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='color:black'>From: </span></b><span style='color:black'>"Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)" <richard.c.angelini.civ@mail.mil><br><b>Date: </b>Wednesday, September 14, 2016 at 1:24 PM<br><b>To: </b>Christopher Neal <chrisneal@snumerics.com>, Benson Muite via ParaView <paraview@paraview.org><br><b>Subject: </b>Re: [Non-DoD Source] [Paraview] Building Paraview with OSMESA<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Times New Roman"'><o:p> </o:p></span></p></div><div><div><div><div><div><p class=MsoNormal><span style='color:black'>Stupid question – when you start up the pvserver process, are you passing it the “—use-offscreen-rendering” flag? <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>mpirun –np 8 pvserver —use-offscreen-rendering …….<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>What’s your build platform? I have lots and lots of build scripts I can share! <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial Unicode MS";color:black'>________________________________</span><span style='color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial Unicode MS";color:black'>Rick Angelini<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial Unicode MS";color:black'>USArmy Research Laboratory<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial Unicode MS";color:black'>CISD/HPC Architectures Team<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Arial Unicode MS";color:black'>Phone: 410-278-6266<o:p></o:p></span></p></div></div></div></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>From: </span></b><span style='font-size:11.0pt;color:black'>ParaView <<a href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a>> on behalf of Christopher Neal <<a href="mailto:chrisneal@snumerics.com">chrisneal@snumerics.com</a>><br><b>Date: </b>Wednesday, September 14, 2016 at 12:44 PM<br><b>To: </b>Benson Muite via ParaView <<a href="mailto:paraview@paraview.org">paraview@paraview.org</a>><br><b>Subject: </b>[Non-DoD Source] [Paraview] Building Paraview with OSMESA<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:black'>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. <o:p></o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='color:black'><hr size=2 width="100%" align=center></span></div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Hi All,</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>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-<a href="http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D">http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D</a> < Caution-<a href="http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D">http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D</a> > ), 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? <br><br>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?<br><br><br>Thank you,</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Chris N</span><span style='color:black'><o:p></o:p></span></p></div></div></div></div></div></body></html>