<html 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="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)"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{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=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>Thanks for the insight guys,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'><br>So if someone is running a Catalyst instrumented code that is compiled on a supercomputer with thousands of back-end nodes, can they link to a ParaView build or a Catalyst Edition and expect the code to work? Do back-end nodes have X servers available to them?<br><br>Thank you,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>Chris Neal<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='font-family:Calibri;color:black'>From: </span></b><span style='font-family:Calibri;color:black'>Chuck Atkins <chuck.atkins@kitware.com><br><b>Date: </b>Friday, August 19, 2016 at 2:47 PM<br><b>To: </b>Christopher Neal <chrisneal@snumerics.com><br><b>Cc: </b>ParaView <paraview@paraview.org><br><b>Subject: </b>Re: [Paraview] Does running Catalyst require osmesa?<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><div><p class=MsoNormal>Hi Chris,<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>Catalyst uses the exact same rendering infrastructure as the rest of ParaView so you if you can render with pvpython and pvserver then you can render with Catalyst in the same configuration. If you don't use OSMesa and instead use "regular" GL then you'll just need to have an X server available and it's associated plumbing set up for Catalyst to be able to render. The nice part about OSMesa builds are that you don't need to deal with X at all, but then you don't have access to the GPU so your render performance is significantly reduced. That may be fine though if your pipeline is heavily compute-bound instead of render-bound, as is often the case. If you want to bypass the X server but still use your GPU, another option is to enable EGL (warning, still bit experimental). Currently, it only works on NVidia GPUs with a very current driver but you get the libGL benefit of GPU accelerated rendering with the libOSMesa benefit of not dealing with an X server.<o:p></o:p></p></div><p class=MsoNormal>Either way, all three configurations for ParaView will work with Catalyst: libGL (gpu w/ X, default), libOSMesa (cpu w/o X), and EGL (gpu w/o X).<o:p></o:p></p><div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><div><div><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>----------<br>Chuck Atkins<br>Staff R&D Engineer, Scientific Computing<br>Kitware, Inc.<o:p></o:p></p></div></div></div></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Fri, Aug 19, 2016 at 2:16 PM, Christopher Neal <<a href="mailto:chrisneal@snumerics.com" target="_blank">chrisneal@snumerics.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt'>Hi,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt'>I’m playing around with different builds of ParaView(all with catalyst enabled). I’m not using a Catalyst edition because of some build issues that I was having with cmake. One thing that I wanted to understand is: If I compile a version of ParaView with Catalyst enabled, but GUI disabled, will I still be able to run a Catalyst example that outputs images?<br><br>Or would I need to figure out how to compile ParaView with OSMESA?<br><br>Thank you,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt'>Chris Neal</span><o:p></o:p></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br><br>Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br><br>Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br><br>Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" target="_blank">http://markmail.org/search/?q=ParaView</a><br><br>Follow this link to subscribe/unsubscribe:<br><a href="http://public.kitware.com/mailman/listinfo/paraview" target="_blank">http://public.kitware.com/mailman/listinfo/paraview</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>