Re: [Gmsh] Convert prism to tet

2019-03-12 Thread Christophe Geuzaine
> On 11 Mar 2019, at 17:27, Bob Flandard wrote: > > Hello Users, > > Is it possible to use Gmsh to convert imported prism (or hex) elements into > tetrahedral elements (each prism converted to 3 tets or each hex to 6 tets) ? > The tet mesh would need to be continuous. No, such subdivision i

Re: [Gmsh] Issue with reference to node 0 in elements list in *.msh file

2019-03-12 Thread Christophe Geuzaine
Dear Nathan, This is indeed strange. As there were many bug fixes since 4.0.1, I would really recommend updating your model to the latest Gmsh release. The difference in numbering comes from an upgrade in OpenCASCADE, which changed the way some entities are constructed. If the issue persists

Re: [Gmsh] Multiple-definition error with the gmsh.h_cwrap header for the C++ API

2019-03-12 Thread Juan Sanchez
Hello, I am not a gmsh developer, but I suppose you could do something like this in your code: namespace { #include "gmsh.h" } Then your object file will have a copy of each function in its own anonymous namespace. Regards, Juan On Tue, Mar 12, 2019 at 12:58 PM Julien Hess wrote: > Dea

[Gmsh] Issue with reference to node 0 in elements list in *.msh file

2019-03-12 Thread Nathan J. Neeteson
Hello everyone, I am have been experiencing an odd issue with Gmsh recently. Essentially, in one of my meshes sometimes when I export it as a *.msh file, there is a reference to a 0 node in the $Elements list - there is no 0 node in the $Nodes list and this causes gmshToFoam to fail when conver

[Gmsh] Multiple-definition error with the gmsh.h_cwrap header for the C++ API

2019-03-12 Thread Julien Hess
Dear gmsh users, I would like to use the C++ API of the Linux SDK (compiled with GCC 4) in a program that I must compile with gcc-5.5.0. Specifying "-D_GLIBCXX_USE_CXX11_ABI=0" is not an option, as the program also uses several other libraries compiled with GCC 5 or higher. According to the