<div dir="ltr"><div>Hi Mark,</div><div><br></div><div>With Catalyst you only connect the running simulation to a pvserver if you're using ParaView Live to do a connection from the GUI to the simulation. <br></div><div><br></div><div>If you're running Catalyst in "batch" the in situ operations are done in the same process space as the simulation and no pvserver process is needed. <br></div><div><br></div><div>Best,</div><div>Andy<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jun 1, 2018 at 11:16 AM Mark Olesen <<a href="mailto:Mark.Olesen@esi-group.com" target="_blank">Mark.Olesen@esi-group.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Andy,<br>
<br>
Welcome back from hols!<br>
<br>
This actually missed the question.<br>
<br>
I assume that we get whatever pvserver up and running in parallel <br>
(generally have indeed used a pvserver build with mesa and llvmpipe <br>
rendering), how do we attach to it from catalyst?<br>
<br>
Using a GUI "connect" button seems pointless/self-defeating, but how can <br>
I convey to catalyst that I'd like to connect to a particular server?<br>
<br>
Cheers,<br>
<br>
/mark<br>
<br>
On 06/01/18 16:56, Andy Bauer wrote:<br>
> Hi Mark,<br>
> <br>
> If you want to create images from Catalyst runs you'll probably want to <br>
> build the ParaView that you're linking to with either OSMesa or EGL (and <br>
> Qt disabled). This gets around needing the X context for rendering since <br>
> I believe running with offscreen enabled is not sufficient. EGL comes <br>
> with most of the NVIDIA drivers -- see <br>
> <a href="https://blog.kitware.com/off-screen-rendering-through-the-native-platform-interface-egl/" rel="noreferrer" target="_blank">https://blog.kitware.com/off-screen-rendering-through-the-native-platform-interface-egl/</a> <br>
> for how to build PV with it. If you want to go the OSMesa route I'd <br>
> recommend using the ParaView superbuild <br>
> (<a href="https://gitlab.kitware.com/paraview/paraview-superbuild" rel="noreferrer" target="_blank">https://gitlab.kitware.com/paraview/paraview-superbuild</a>) to build it <br>
> for you.<br>
> <br>
> Does this answer your question? I just got back from vacation and am <br>
> trying to catch up on more things than my brain can currently handle so <br>
> let me know if you have more questions.<br>
> <br>
> Best,<br>
> Andy<br>
> <br>
> <br>
> <br>
> On Mon, May 28, 2018 at 11:25 AM Mark Olesen <<a href="mailto:Mark.Olesen@esi-group.com" target="_blank">Mark.Olesen@esi-group.com</a> <br>
> <mailto:<a href="mailto:Mark.Olesen@esi-group.com" target="_blank">Mark.Olesen@esi-group.com</a>>> wrote:<br>
> <br>
> For the mailing list, since this must probably be a FAQ (even if I seem<br>
> to find the answer in the usual places).<br>
> <br>
> I would like to have paraview rendering in parallel for a simulation<br>
> with catalyst. For simplicity, I'm fiddling about on a local<br>
> workstation, but would like to generalize later. it should work without<br>
> live visualization enabled, or requiring a GUI to connect.<br>
> <br>
> I'd presume using something like the following<br>
> <br>
> mpirun -np 12 pvserver --server-port=123456 --force-offscreen-rendering<br>
> <br>
> would be setup a parallel rendering session as usual. However, after<br>
> scouring docs there doesn't seem to be an obvious way to connect this<br>
> within catalyst (without a GUI).<br>
> <br>
> The only access point that I seem to find is to define an MPI<br>
> communicator for initializing catalyst after some how (some hand-waving<br>
> here) querying a pvserver connection for its host topology and defining<br>
> an appropriate communicator.<br>
> <br>
> Cheers,<br>
> <br>
> /mark<br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a> <<a href="http://www.kitware.com" rel="noreferrer" target="_blank">http://www.kitware.com</a>><br>
> <br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
> <br>
> Please keep messages on-topic and check the ParaView Wiki at:<br>
> <a href="http://paraview.org/Wiki/ParaView" rel="noreferrer" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
> <br>
> Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" rel="noreferrer" target="_blank">http://markmail.org/search/?q=ParaView</a><br>
> <br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="https://public.kitware.com/mailman/listinfo/paraview" rel="noreferrer" target="_blank">https://public.kitware.com/mailman/listinfo/paraview</a><br>
> <br>
<br>
-- <br>
Dr Mark OLESEN<br>
Principal Engineer, ESI-OpenCFD<br>
ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY<br>
Mob. +49 171 9710 149<br>
<a href="http://www.openfoam.com" rel="noreferrer" target="_blank">www.openfoam.com</a> | <a href="http://www.esi-group.com" rel="noreferrer" target="_blank">www.esi-group.com</a> | <a href="mailto:mark.olesen@esi-group.com" target="_blank">mark.olesen@esi-group.com</a><br>
</blockquote></div>