<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [Paraview] exodus reader troubles</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Mike Stephens wrote:<BR>
> two things:<BR>
> in paraview 2.6.2, the exodus reader reads<BR>
> my data file just fine and i've used it to<BR>
> great success. however, i've been recently<BR>
> asked to do something with the node sets that<BR>
> are part of the exodus data.<BR>
> it seems to read them in okay; but as soon as<BR>
> i try to change the view of the camera (i.e.<BR>
> the scene is re-rendered) it crashes paraview.<BR>
> i get an error about an array type mis-match.<BR>
<BR>
Can you please send the exact error message?<BR>
<BR>
> question 2:<BR>
> paraview 3 won't even read my exodus files<BR>
> that paraview 2.6.2 reads fine.<BR>
<BR>
Can you provide an example file?<BR>
<BR>
> i've tried the released pv3 and a cvs build<BR>
> we did a few weeks ago. not much to go on;<BR>
> i don't get much feedback from pv3.<BR>
<BR>
What does that mean? Does PV3 crash? Does it<BR>
just show an empty screen? Print an error<BR>
message?<BR>
<BR>
> anyone have any ideas?<BR>
<BR>
Without more specific error messages or a way<BR>
to replicate your problems, there's not much<BR>
to try. One thing you can do is renamed your<BR>
ExodusII files so that they end in ".exii" (instead<BR>
of ".exo", ".g", ...). If you read in files<BR>
with this different extension, a different Exodus<BR>
reader will be used -- one under development<BR>
to support new features.<BR>
<BR>
David</FONT>
</P>
</BODY>
</HTML>