On Thu, 11 May 2017, John Peterson wrote:
On Thu, May 11, 2017 at 7:12 AM, Harshad Sahasrabudhe <[email protected]>
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.
Those lower dimensional elements were probably there for a reason,
though, like specifying boundary conditions.
Is that how we decided to interpret those in the Gmsh case? Not as
overlapping boundary elements?
Newer versions of libmesh should properly support reading Gmsh files
with lower dimensional elements.
That's what I thought, too, but
https://github.com/libMesh/libmesh/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aclosed%20gmsh
doesn't seem to find any relevant fixes that post-date 0.9.5
I would really encourage you to upgrade your code from using libmesh
0.9.5 to a new release as soon as possible... if there is some major
issue preventing you from doing so, we can probably help with
resolving it...
Agreed.
---
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
