- edited description
MOAB gmsh read ignoring point materials
I'm unable to get the point materials that are defined in a gmsh mesh file. I believe this happens because the create_elements function seems to ignore points: (ReadGmsh.cpp file)
// do not do anything for point type
if (type.mb_type==MBVERTEX)
return MB_SUCCESS; // do not create anything
Comments (8)
-
reporter -
reporter - edited description
-
The material sets in MOAB are element based (generally). So we ignore attributes on the points. There has not been a request to include these yet. However, if this is an important feature, we can certainly look at adding the necessary code. If you can submit a PR with changes, along with a test file, that would be much appreciated too!
-
reporter @vijaysm I work with fluid dynamics (oil reservoir simulation). It's pretty common, specially when working in 2D, to define boundary conditions for injection or production wells in a point, for example. I'll try to change the code and submit a PR.
-
reporter @vijaysm I've opened the PR here: https://bitbucket.org/fathomteam/moab/pull-requests/298/node-material-gmsh/diff It seems to be working fine with both the C++ interface and PyMoab, but I've never used the C++ interface much, so I advise you or someone else take a careful look if the behaviour is correct.
-
reporter @vijaysm I was wondering, what mesh generation software do you guys use? Is there some software that exports directly to h5m?
-
We primarily use some combination of NetGen, Cubit and Gmsh, in addition to our native mesh generation tools available under MeshKit, which is also part of SIGMA. If you have a mesh file in some other format (gmsh, exodus, vtk), you can convert it to h5m with the
mbconvert
tool. This is pretty straightforward. Should be available in your installation or look for it under tools directory. -
reporter - changed status to resolved
- Log in to comment