<div>Yes, the VTK EnSight Reader does support particle files while I am not sure if the term "particles" Alan mentioned is just the one supported by the VTK EnSight Reader. There seem to be multiple definitions of "particles". For example, the one in 'measured particles' (supported by the VTK EnSight Reader) might be different from that in 'particle tracing'.</div>
<div> </div>
<div>-Zhanping</div>
<div> </div>
<div>-- <br>Zhanping Liu, PhD<br>Kitware, Inc.<br>28 Corporate Drive<br>Clifton Park, NY 12065-8662<br>Phone: 518-371-3971 x 138<br><a href="http://www.zhanpingliu.org">http://www.zhanpingliu.org</a><br><br><br></div>
<div class="gmail_quote">On Mon, Jul 20, 2009 at 11:44 AM, Moreland, Kenneth <span dir="ltr"><<a href="mailto:kmorel@sandia.gov">kmorel@sandia.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div><font face="Calibri, Verdana, Helvetica, Arial"><span style="FONT-SIZE: 11pt">Any file format that holds unstructured grid or poly data and supports 0D cells (vertices, points, spheres, or whatever you want to call them) is sufficient. If the particles remain consistent from one time step to the next, then I recommend the Exodus format because it has direct support for time and you can place everything in a single file. However, Exodus assumes that the topology of your data does not change, so it does not directly support particles that are born or die.<br>
<br>If you do have particles that are born and die, I’ve heard of success with the EnSight format. If at all possible, also write out “global ids” that uniquely identify the particles from one timestep to the next. If you do not have that, it limits what ParaView can do with the particles.<br>
<br>-Ken<br><br><br>On 7/16/09 7:37 PM, "Scott, W Alan" <<a href="http://wascott@sandia.gov" target="_blank">wascott@sandia.gov</a>> wrote:<br><br></span></font>
<blockquote><span style="FONT-SIZE: 11pt"><font face="Arial">I have a user that runs particle physics simulations and wants to write this into files that ParaView can easily read.<br> <br>What are good file formats for particle simulations?<br>
<br>Thanks,<br> <br>Alan<br> <br>--------------------------------------------------------<br>W. Alan Scott<br>ParaView Support Manager<br> <br>GAITS<br>Sandia National Laboratories, MS 0822<br>Org 9326 - Building 880 A1-C<br>
(505) 284-0932 FAX (505) 845-0833<br>---------------------------------------------------------<br> <br> <br> <br> <br> <br></font><font face="Calibri, Verdana, Helvetica, Arial"><br></font></span></blockquote><span style="FONT-SIZE: 11pt"><font face="Calibri, Verdana, Helvetica, Arial"><br>
</font></span><font size="2"><font face="Consolas, Courier New, Courier"><span style="FONT-SIZE: 10pt"><br> **** Kenneth Moreland<br> *** Sandia National Laboratories<br>*********** <br>*** *** *** email: <a href="http://kmorel@sandia.gov" target="_blank">kmorel@sandia.gov</a><br>
** *** ** phone: (505) 844-8919<br> *** web: <a href="http://www.cs.unm.edu/~kmorel" target="_blank">http://www.cs.unm.edu/~kmorel</a><br></span></font></font><font face="Calibri, Verdana, Helvetica, Arial"><span style="FONT-SIZE: 11pt"><br>
</span></font></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><br clear="all">
<div></div><br>