<div dir="ltr"><div><div>Hi,<br><br></div>The parallel XML data set writers all write independently of each other (no MPI communication is needed in the writers). Because of this they can't tell process 0 when writing it's meta-data file that it doesn't need to write out meta data for them. <br>
<br></div>Andy<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 25, 2013 at 4:30 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">I am running a simulation in-situ linked with ParaView CoProcessing library with a pipeline that includes “slice->Integrate Variables Filter->ParallelUnstructuredGridWriter” so that integrated velocity value for a slice at each time point
can be written out while running the simulation in-situ. The output from this ParallelUnstructureGridWriter for each time step includes one pvtu file plus one vtu file from each running node, so that is a lot of output files for each time point especially
when running on a large number of nodes in parallel. However, it looks like only the output vtu file from processing node 0 includes valid velocity range value while other output vtu files from other nodes include only blank/empty values. So I am wondering
whether there is a good way to set up only outputting vtu file from processing node 0 to prevent output of those large number of files that don’t include valid/useful values. Any suggestions are very much appreciated.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks,<span class="HOEnZb"><font color="#888888"><u></u><u></u></font></span></p><span class="HOEnZb"><font color="#888888">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Hong<u></u><u></u></p>
</font></span></div>
</div>
<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><br>
<br></blockquote></div><br></div>