On Fri, Aug 1, 2014 at 9:27 AM, John Peterson <jwpeter...@gmail.com> wrote:
>
> Oh wait, on closer inspection elem_map is the identity. So, not sure
> what the problem might be...
Are you seeing something like the attached image when you try to view
the sidesets in paraview?
I have seen this issue before, and at the time tracked it down to a
mesh with 2D TRI elements being written to an exodus file with
"num_dim=3" (you can check this by running ncdump on the file).
At that time, a quick fix to make paraview display the sidesets
correctly was to call
ExodusII_IO::use_mesh_dimension_instead_of_spatial_dimension(true);
but this doesn't work for your example, since it's a 2D mesh living in 3D.
What I don't understand is why your original exodus file, which also
has num_dim=3, actually displays correctly in paraview! This might
take a big longer to track down...
BTW, are you sure the sidesets are actually wrong or are they just
being displayed incorrectly by paraview?
--
John
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
