<div dir="ltr"><div>Hi,<br><br></div>I inlined the responses.<br><br>Andy<br><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Apr 5, 2013 at 3:48 PM, Hong Yi <span dir="ltr"><<a href="mailto:hongyi@renci.org" target="_blank">hongyi@renci.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Andy,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Many thanks for all the information that certainly clears up my confusion although I have a follow-up question to confirm with you on the last part regarding
live feed. Let me split the question up into the following two scenarios: <u></u><u></u></span></p>
<p><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><span>(1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">No live feed, but only in-situ viz to write data and rendered image for each time step from the simulation code. In this scenario, I only need to
set up the pipeline, add adaptor calls in the simulation code to do co-processing for each time step and output data for desired time steps, and build and run the simulation code that are linked with Paraview coprocessing or Catalyst. In this case, there is
no need to run pvserver and paraview client, everything related to in-situ/coprocessing viz is integrated into the simulation code, is it right?<u></u><u></u></span></p>
<p><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><span></span></span></p></div></div></blockquote><div><br></div><div>Exactly correct. At this point Catalyst just acts like any other library linked in to your simulation code.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="blue" vlink="purple" lang="EN-US"><div><p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><span>(2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Need live feed and live viz while doing in-situ viz to monitor simulation in progress and possibly can influence simulation by changing some parameters
through paraview client. In this case, I need to run paraview client and connect to the live visualization through
</span>Tools->Connect to Catalyst GUI menu, <span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
where I need to input a port number to connect to the Catalyst. I am not clear on this part. Do I need to run the simulation code linked with Paraview coprocessing/Catalyst, then run pvserver on some port somehow linked to the simulation code, which in turns
can be connected back to the client? I cannot find any specific information on the process of doing live feed in an in-situ live viz scenario, so it’d be great help if you can point me to some resources or just briefly provide high-level info on how this works.
</span></p></div></div></blockquote><div><br></div><div>You are correct on the client for connecting to the simulation run. You don't need to run pvserver for this. If when exporting the script you specify that you want to connect live, it enables the simulation to connect directly to the ParaView client.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="blue" vlink="purple" lang="EN-US"><div><p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Looking forward to the Catalyst Users Guide coming out soon and thanks again for all the expert information!!!<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Best regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hong<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Andy Bauer [mailto:<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>]
<br>
<b>Sent:</b> Friday, April 05, 2013 2:21 PM</span></p><div><div class="h5"><br>
<b>To:</b> Hong Yi<br>
<b>Cc:</b> <a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a><br>
<b>Subject:</b> Re: [Paraview] Live data source for co-processing in Paraview version 3.14.1<u></u><u></u></div></div><p></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Hong,<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">That Catalyst Users Guide is still a couple of weeks away.
<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">To clear up your confusion in the meantime, Catalyst is really a stripped down version of ParaView built with co-processing. The idea behind Catalyst is that there's a lot of stuff in ParaView that isn't needed
for in situ analysis, especially depending on what the desired outputs are. So Catalyst's role is to reduce the size of the libraries that a simulation code needs to link to. For example, if you're not interested in generating screenshots you would have a
lot of overhead for all of the rendering parts of ParaView and some GL implementation. Catalyst would allow you to not include rendering components then. The live feed, Connect to Catalyst, will work with either Catalyst or a full blown ParaView with co-processing
build. In order to connect your simulation to the ParaView GUI through the live feed you should only need to run your simulation code linked with ParaView/Catalyst and a generated Python script which sets things up for live-viz.
<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Regards,<u></u><u></u></p>
</div>
<p class="MsoNormal">Andy<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Fri, Apr 5, 2013 at 12:45 PM, Hong Yi <<a href="mailto:hongyi@renci.org" target="_blank">hongyi@renci.org</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Andy,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I am wondering whether the Catalyst Users Guide is very close to be out and ready to download, perhaps
in the next couple of days hopefully? Although the user guide would most likely answer my question below, I’d like to ask it now since I expect it will have quick answer which would clear up my doubts quickly. Specifically, I am not sure the relationship between
Catalyst and the coprocessing libraries included with Paraview build/install. From what I read, the coprocessing library is called Catalyst in the new ParaView v3.98. I have downloaded catalyst source tree from
<a href="http://catalyst.paraview.org/catalyst/resources/software.html" target="_blank">
http://catalyst.paraview.org/catalyst/resources/software.html</a> and built it into a separate directory from Paraview as instructed. However, when I built Paraview itself, I can enable coprocessing and all needed adaptors which will generate CoProcessing
directory that includes adaptors and CoProcessors and seems it already includes coprocessing library without a separate Catalyst install. I am thinking if I only do in-situ visualization without live data source feed into paraview client for live monitoring,
I might not need a separate catalyst install, is this right? As you instructed in this email thread on live data source, I can use
</span>Tools->Connect to Catalyst GUI menu <span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">
to connect to live data source which definitely requires a sepate Catalyst install. I know I will have to input a port number to accept connections from catalyst, so I think I will have to run catalyst also separately from the catalyst installed directory such
as pvserver in the bin directory under catalyst install which would feed live data source into the paraview client, right? If so, in this case, I am thinking I probably do not need to run another pvserver instance as Paraview server from the Paraview install
directory that the client connects to, but rather to connect to the pvserver instance from Catalyst as live data source? I am hoping to frame my question with not too much confusion, and hoping to clear up the confusion in my head by some quick answer from
you.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Again, looking forward to the Catalyst Users Guide to be out soon!</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hong</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Andy Bauer [mailto:<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>]
<br>
<b>Sent:</b> Thursday, March 21, 2013 3:25 PM</span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><br>
<b>To:</b> Hong Yi<br>
<b>Cc:</b> <a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a><br>
<b>Subject:</b> Re: [Paraview] Live data source for co-processing in Paraview version 3.14.1<u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">I'm working on a Catalyst Users Guide that should cover everything you need. It will probably be ready in a couple of weeks. I'll post to the paraview list when it's ready and where to
download at.<br>
<br>
Andy<u></u><u></u></p>
<div>
<p class="MsoNormal">On Thu, Mar 21, 2013 at 3:17 PM, Hong Yi <<a href="mailto:hongyi@renci.org" target="_blank">hongyi@renci.org</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Andy,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Many thanks for the useful information. This confirms my suspicion on the live data source after
I see information on catalyst, so I’ll just go ahead to upgrade my development environment to the latest Paraview version 3.98.1 to be able to leverage catalyst co-processing library for my in-situ work. I have read up a lot of information on coprocessing
in ParaView so far, so I think I’ll just need to get a specific example running next for a good understanding of specifics, then I can get to specifics such as developing adaptors to interface with the simulation code. At that point, I might have more specific
questions.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Thanks again,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hong</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Andy Bauer [mailto:<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>]
<br>
<b>Sent:</b> Thursday, March 21, 2013 1:59 PM<br>
<b>To:</b> Hong Yi<br>
<b>Cc:</b> <a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a><br>
<b>Subject:</b> Re: [Paraview] Live data source for co-processing in Paraview version 3.14.1</span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Hong,<br>
<br>
The live data source that was done with ParaView 3.14 really was just a demo. It's evolved and has been improved for ParaView 3.98. Not it's in the Tools->Connect to Catalyst GUI menu.<br>
<br>
Catalyst is indeed the evolution of what we called the co-processing tools in older versions of ParaView.
<br>
<br>
If you can give an example of what you're trying to do for in-situ work, I can probably point you in the proper direction.<br>
<br>
Andy<u></u><u></u></p>
<div>
<p class="MsoNormal">On Thu, Mar 21, 2013 at 11:45 AM, Hong Yi <<a href="mailto:hongyi@renci.org" target="_blank">hongyi@renci.org</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">Hello,<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">I built Paraview server version 3.14.1 on a HPC cluster with all co-processing-related flags turned on including enabling co-processing, all adaptors, and plugins, etc., and built
Paraview client/server with no MPI on a local linux machine with co-processing enabled as well. Then I connect the Paraview client running on my local linux machine to the Paraview server running on the HPC cluster to visualize a phasta-generated mesh data
on the HPC cluster. All works except that I don’t find “Live data source” from paraview “Source” menu. I have not really tried coprocessing library yet, but it is in my next to-do list. In the meanwhile, I’d like to get some advice from this list regarding
this missing “Live data source” from Paraview client GUI in case I missed something or did not do something correctly.
<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">On a related question, from
<a href="http://catalyst.paraview.org/" target="_blank">http://catalyst.paraview.org/</a> I don’t see specific information on whether the coprocessing library in earlier version such as 3.14.1 is an earlier version of this catalyst. It appears to me this catalyst
library only works for version 3.98 and can be built into paraview 3.98 by generating catalyst source tree and building it into paraview. For earlier paraview version 3.14.1, I cannot leverage this latest catalyst source since it only works with version 3.98,
is this correct?<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Thanks for any information and explanation. I am trying to get myself up to speed on in-situ visualization for large scale simulation, so any related information on in-situ visualization
is very much appreciated!<u></u><u></u></p>
<p class="MsoNormal"><span style="color:#888888"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#888888">Hong</span><u></u><u></u></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>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><u></u><u></u></p>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
</blockquote></div><br></div></div></div>