Thanks, Andy. Please correct me if I am wrong since I may not get what you really mean here. I agree the first option sounds like a good one, and I am thinking I can modify the co-processing script to add "CreateWriter()" to write the output from the Integrate Variables filter. Since it is not a parallel writer, I am thinking this "CreateWriter()" might work by only writing to disk from the first processor. Otherwise, there might be a way to pass this output value to the simulation code Phasta for it to output the value only from the first processor? Since users need to observe the output from simulation when running it in-situ (without live feed at this point), the only way I can think of is through the disk output for the users to observe, or is there another way?
Thanks again, Hong From: Andy Bauer [mailto:[email protected]] Sent: Monday, April 29, 2013 10:12 AM To: Hong Yi Cc: [email protected] Subject: Re: [Paraview] Output of ParallelUnstructuredGridWriter running on multiple nodes I can think of two options for this, the first is modifying the co-processing script to get the data you want directly from the output without writing it to disk. Look at http://paraview.org/Wiki/ParaView/Python_Scripting for some information on that. Otherwise, you can try using the Python programmable filter to extract the data as well and write it to disk. If it was me I'd go with the first option. Andy On Fri, Apr 26, 2013 at 4:50 PM, Hong Yi <[email protected]<mailto:[email protected]>> wrote: Thanks, Andy. In our case, users only want to observe one integrated velocity value (one output value from Integrate Variable Filter) for the slice at each time step so that they can determine from which time point on this velocity value stops changing which indicates to them the simulation has converged. So this large amount of output files from the ParallelUnstructuredGridWriter is hard to serve this purpose. I am wondering whether there is a way for me to export the SpreadSheetRepresentation view (to view Integrate Variable Filter output) as a screen capture when I export pipeline in python for coprocessing? It looks like the "Export State" GUI for coprocessing only allows to export rendered views, not other types of views. If not, I am thinking perhaps I can write a customized writer plugin to only export the needed output value for our purpose and to make this writer only exports one file for each time step regardless of the number of processors it runs on. Thanks for any more information you can provide! Hong From: Andy Bauer [mailto:[email protected]<mailto:[email protected]>] Sent: Thursday, April 25, 2013 7:43 PM To: Hong Yi Cc: [email protected]<mailto:[email protected]> Subject: Re: [Paraview] Output of ParallelUnstructuredGridWriter running on multiple nodes Hi, 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. Andy On Thu, Apr 25, 2013 at 4:30 PM, Hong Yi <[email protected]<mailto:[email protected]>> wrote: 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. Thanks, Hong _______________________________________________ Powered by www.kitware.com<http://www.kitware.com> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
