On Thu, 11 May 2017, Harshad Sahasrabudhe wrote: > Thanks for your help. The problem was solved. I had tets and > triangles in my mesh file initially, which was causing the mismatch > in number of elements between 2 processors. I removed the triangle > elements and the error went away.
I'd still love to get a test case code if you can replicate the error with libMesh 1.2... or even if you can boil the problem down to a short code with 0.9.5; I can see if it replicates on newer libMesh or not myself. Now that you've discovered more about the problem it's looking more likely to me that it's in the category "corner case we should support but don't" rather than "bug we fixed a year ago that you're just not up to date on yet". However, if you're too busy I understand; it's definitely not *your* problem anymore. Even if there is a current bug with Gmsh loading of multi-manifold meshes, that's only applicable to people who *want* multi-manifold meshes, and if you don't want a combined volume + surface mesh then "remove the triangles" is the correct way to avoid getting one. Thanks, --- Roy ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
