<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.3790.2759" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=750394514-23102006><FONT face=Arial
color=#0000ff size=2>Hi Randall,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=750394514-23102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=750394514-23102006><FONT face=Arial
color=#0000ff size=2>It's a good starting point, but as you said it only
partially answer my point.</FONT></SPAN><SPAN class=750394514-23102006><FONT
face=Arial color=#0000ff size=2> I guess, It would be easier for the PV team to
list PV features according to the reader employed and to the PV users to
describe the bugs found. In other words, from the PV users side, this
compatibility list could be built by listing the bugs found (I know that Kitware
has a bug list system but some things get a bit dispersed in such system). This
kind of information should be available on the ParaView Oficial's Wiki, as well
as in any other PV information site. We always have question regarding file
formats and their features on the PV maillist.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=750394514-23102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=750394514-23102006><FONT face=Arial
color=#0000ff size=2>Regards</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=750394514-23102006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=750394514-23102006><FONT face=Arial
color=#0000ff size=2>Renato.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=pt-br dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>De:</B> Randall Hand [mailto:randall.hand@gmail.com]
<BR><B>Enviada em:</B> sábado, 21 de outubro de 2006 22:47<BR><B>Para:</B>
Renato N. Elias<BR><B>Assunto:</B> Re: [Paraview] Readers compatibility
list<BR></FONT><BR></DIV>
<DIV></DIV>While not a complete answer to your question, you can find alot of
information on <A
href="http://wiki.vizworld.com/index.php/Paraview_Data_Formats#Supported_Data_Formats">http://wiki.vizworld.com/index.php/Paraview_Data_Formats#Supported_Data_Formats
</A>. It's a complete list of Paraview's File Format and some basic
information on limitations and restrictions. <BR><BR>It's a site
maintained by myself and some friends. It's a Wiki, so we welcome any
contributions or suggestions you care to make. <BR><BR>
<DIV><SPAN class=gmail_quote>On 10/21/06, <B class=gmail_sendername>Renato N.
Elias</B> <<A
href="mailto:rnelias@nacad.ufrj.br">rnelias@nacad.ufrj.br</A>> wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><BR>Hey
guys,<BR><BR>Is there a ParaView compatibility list according to the reader
used?<BR><BR>For example:<BR><BR>VTK Format: all PV filters supported,
parallel reading, lookmarks<BR>Exodus: filter X, Y, Z, volume rendering,
parallel reading, etc... <BR>Plot3D: filter W, K, L (partially
supported)<BR>Ensight: ...<BR>...<BR>...<BR><BR>It would be helpful when
deciding which format should be adopted to use with<BR>ParaView.<BR><BR>maybe
someone in PV team already have something like that.
<BR><BR>Regards<BR><BR>Renato N.
Elias<BR>===============================================<BR>PhD student - <A
href="http://www.nacad.ufrj.br/~rnelias">http://www.nacad.ufrj.br/~rnelias</A><BR>High
Performance Computing Center <BR>Federal University of Rio de Janeiro<BR>Rio
de Janeiro, Brazil<BR>+55(21)
2562-8080<BR><BR>_______________________________________________<BR>ParaView
mailing list<BR><A href="mailto:ParaView@paraview.org">ParaView@paraview.org
</A><BR><A
href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</A><BR></BLOCKQUOTE></DIV><BR><BR
clear=all><BR>-- <BR>----------------------------------------<BR>Randall Hand
<BR>Visualization Scientist<BR>ERDC MSRC-ITL </BODY></HTML>