> On Nov 14, 2015, at 11:21 AM, Torquil Macdonald Sørensen <torq...@gmail.com> 
> wrote:
> 
> Hi!
> 
> I'm a libmesh beginner, and I seem to be having some trouble with
> importing meshes created by GMSH 2.11.0. In GMSH, I create a simple unit
> cube, and define faces and a volume. Then I create a 3d mesh and save in
> the MSH format (ASCII version 2). I have attached the file cube.msh.
> 
> When I run the simple attached libmesh program import_gmsh.cpp, I get
> the following error message:
> 
> Cannot handle meshes with dimension mismatch greater than 1.

This error means that your mesh has 1, 2, and 3D elements in it... not 
something our Gmsh reader is currently able to handle.  We assume that lower 
dimensional elements are used to define boundary conditions, but don't yet 
handle reading edge-based (?) BCs.  This could probably be fixed.


> If I try to use an UNV mesh file exported from GMSH, I get the error
> message:
> 
> ERROR: UNV-element type 21 not supported.

Not sure about this error, I'd have to look up what element type 21 is in the 
UNV format.


> 
> and if I try an INP mesh file from GMSH:
> 
> ERROR: Expected boundary element of dimension 2 but got 1

Same limitation as the Gmsh reader.


> Btw, when I run libmesh-config --ldflags, it returns just a blank line.
> I suppose that it is meant to return something like -lmesh_opt?

Try libmesh-config --libs 


> I'm using the GIT master branch of libmesh, built with GCC 5.2.1 20151110.
> 
> Best regards
> Torquil Sørensen
> <cube.unv>
> <cube.inp>
> ------------------------------------------------------------------------------
> _______________________________________________
> Libmesh-users mailing list
> Libmesh-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libmesh-users

------------------------------------------------------------------------------
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to