Re: [Libmesh-devel] Incorrect boundary IDs from 2D ExodusII mesh created in CUBIT

[John P. <jwp...@gm...>]

On Fri, Aug 1, 2014 at 10:28 AM, John Peterson <jwp...@gm...> wrote:
>
> 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...

Here's something... your original file references side "5" of the TRI3
elements in question:
 elem_ss1 = 1, 17, 33 ;
 side_ss1 = 5, 5, 5 ;


while the libmesh-generated version references side "1"
 elem_ss1 = 1, 17, 33 ;
 side_ss1 = 1, 1, 1 ;

So while I don't understand what side "5" even means on a 3-sided
element, clearly it displays properly in paraview!

Otherwise, all the element numbers in the sets themselves match
between the two files.

-- 
John