[Gmsh] mesh I/O in memory?

Nico Schlömer nico.schloemer at gmail.com
Tue Jul 19 15:09:37 CEST 2016

Hi everyone,

As the author of pygmsh [1] I sometimes get user complaints about how slow
mesh generation is. The way pygmsh works is that it generates a geo-file in
memory, writes that out, has gmsh run over it to generate a msh-file, then
read in and parse that file to generate the nodes and cells in memory. I'm
wondering if this could be improved.

What comes to mind straight away is passing the geo-file as a string to
gmsh, and to retrieve the msh-file as a string from gmsh. This way, the
slow I/O on the hard drive is avoided. Is that at all possible with gmsh?

Even better would be to retrieve the mesh data directly from gmsh, but I
guess for this it'd need tighter integration with Python which just isn't


[1] https://github.com/nschloe/pygmsh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://onelab.info/pipermail/gmsh/attachments/20160719/8f4b3a14/attachment.html>

More information about the gmsh mailing list