Hi Ning,<br><br>The most common use case will be to call the adapter on every node/process. The python script for the coprocessing will by default run on every process as well (if I remember correctly this is the symmetric python mode). I'm not that familiar with the parallel rendering and compositing process in paraview but I'm assuming that it will work properly. You will have to modify the python script yourself though in order to do that. The current script generator is set up to use the parallel XML writers in order to output the desired results. We have plans to stream the results from the simulation to a paraview client but that is not a top priority at this time.<br>
<br>By the way, the nightly paraview documentation has been updated so that it will now include the coprocessing classes. For now just look for the classes that begin with vtkCP.<br><br>Andy<br><br><div class="gmail_quote">
On Tue, Mar 23, 2010 at 10:38 AM, liuning <span dir="ltr"><<a href="mailto:tantics@gmail.com">tantics@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Andy,<div><br></div><div>Thank you very much for your efforts. I tried the co-processing example on a single machine and it worked. But I still have some questions on how to apply the co-processing to a parallel environment.</div>
<div><br></div><div>First, you mentioned that the adapter should be called from the simulation code. Since the simulation is performed on a cluster and use MPI to communicate, is the adapter called from the simulation code of every node or just a master node(e.g. the node with rank=0)?</div>
<div><br></div><div>Second, normally the client control the parallel viz through server manager, which knows how to deal with the VTK pipeline. But if we are doing a in-situ viz, it seems that the simulation code that drives the whole pipeline.If it is true,then how to synchronize the rendering and compositing process?</div>
<div><br></div><div>Thanks again,</div><div><br></div><div>-Ning<br> <br><div class="gmail_quote">On Tue, Mar 23, 2010 at 12:52 AM, Andy Bauer <span dir="ltr"><<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I sent this out to the paraview list but wanted to make sure that you got it as well. It is still incomplete but hopefully gets people going. Let me know if you have any questions and/or problems.<br>
<br>==============================<br>
<br>I added a wiki page for the coprocessing work that is getting integrated into paraview. It is at <a href="http://paraview.org/Wiki/CoProcessing" target="_blank">http://paraview.org/Wiki/CoProcessing</a><br><br>The
wiki still needs a bit more work but hopefully it will get people going
in the proper direction and answer most of the basic questions. Note
that the paraview "nightly" documentation hasn't been updated since
1/5/2010 so it doesn't include information on coprocessing yet but we
are working on fixing the problem.<br><font color="#888888"><font color="#888888">
<br>Andy</font>
</font></blockquote></div><br></div>
</blockquote></div><br>