<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3562" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=181450817-20072009><FONT face=Arial
color=#0000ff size=2>Ken,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=181450817-20072009><FONT face=Arial
color=#0000ff size=2>Why not use a VTK format for particle support? Lack
of direct time support? Or, would it be that other programs cannot read
it?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=181450817-20072009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=181450817-20072009><FONT face=Arial
color=#0000ff size=2>Anyone know if VisIt can read current VTK file
formats?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=181450817-20072009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=181450817-20072009><FONT face=Arial
color=#0000ff size=2>Alan</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Zhanping Liu
[mailto:zhanping.liu@kitware.com] <BR><B>Sent:</B> Monday, July 20, 2009 9:55
AM<BR><B>To:</B> Moreland, Kenneth<BR><B>Cc:</B> Scott, W Alan;
paraview<BR><B>Subject:</B> Re: [Paraview] File formats for particle
visualization<BR></FONT><BR></DIV>
<DIV></DIV>
<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></BLOCKQUOTE></BODY></HTML>