On Fri, Aug 1, 2014 at 9:17 AM, David Knezevic <dkneze...@seas.harvard.edu> wrote: > Hi All, > > I've attached a simple 2D mesh with TRI3 elements that was made in CUBIT. It > has four sidesets (one for each boundary), and when I view the mesh in CUBIT > the sidesets look fine. > > But when I read this mesh into libMesh, it mixes up the sidesets so that the > boundary IDs are on internal edges. > > So I first wanted to check if anyone else can reproduce this bug with the > attached mesh?
If I had to guess, I'd say the sideset setting code is ignoring/not using the non-identity elem_map which is in this file. Cubit-14 makes extensive use of the elem_map while previous versions didn't really, we've been ironing out a few bugs related to this over the last year or so... I'll take a look. -- 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
