Ethan/ all,
Good catch, good research. Since this is an Exodus bug, and thus will affect
Sandia, I wrote it up in the bug tracker. I also took it as a Sandia bug.
Unless things change, it is scheduled to be fixed for the next release -
version 5.1.
You can keep up with this bug here:
Hello,
After discussion with a lot of meshing people, and especially Greg Sjaardema at
SNL, the ExodusII lead, I believe there is a bug in the ExodusII reader for the
case of arbitrary polyhedra.
Below is an extremely detailed description of the issue, along with a response
by Greg explaining
Hi Andy,
Your explanation made it a lot clearer for me. I tested it out with multiple
pvservers running on a single node and I was able to connect with my
simulation. Success!
However, when I tried running pvservers across more than one node, the Catalyst
connection failed. I saw a bunch of
How to activate (selectively if possible ?) debug traces when using
ParaView ?
I am in the process of creating new couples of HDF5 / XDMF files : for
now, it is bugged, so the XDMF reader crashes when I open it in
ParaView. I need to "see" why ParaView crashes : that is, I need to
understand
