On Mon, Apr 26, 2010 at 2:18 PM, Lorenzo Botti <[email protected]> wrote:
> Hi all,
> I noticed a problem in the visualization (with paraview) of hex27 elements
> written using exodusII_IO.
> The connectivity is broken resulting in a corrugated surface.
> I took a look at the patran documentation, nodes numbering as well as face
> numbering seems correct to me.
>
> Is someone else aware of this problem? Could it be a vtk problem?
> Can I read exodus files with others open source visualization tools?
We've had problems with the Hex27 numbering in ExodusII before. It
looks like Derek was the last one to change the indices around...here
are the diffs from that version:
svn diff -r3391:3462 exodusII_io_helper.C
const int ExodusII_IO_Helper::ElementMaps::hex27_node_map[27] = {
// Vertex and mid-edge nodes
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
// Mid-face nodes and centroid
- 26, 21, 22, 23, 24, 25, 20};
+ 21, 25, 24, 26, 23, 22, 20};
-const int ExodusII_IO_Helper::ElementMaps::hex27_face_map[6] = {1,
0, 3, 5, 4, 2};
+const int ExodusII_IO_Helper::ElementMaps::hex27_face_map[6] = {1,
2, 3, 4, 0, 5};
-const int ExodusII_IO_Helper::ElementMaps::hex27_inverse_face_map[6]
= {2, 1, 6, 3, 5, 4};
+const int ExodusII_IO_Helper::ElementMaps::hex27_inverse_face_map[6]
= {5, 1, 2, 3, 4, 6};
You might try reverting them and see if that helps? Perhaps paraview
is going off an older Exodus numbering scheme.
--
John
------------------------------------------------------------------------------
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
