Christopher J. Bateman

Just hit this issue myself. Looks like it is expecting the dtypes of ```mesh.cells[...].data``` to be int32/int64.

Looks like the simplest workaround is to use the ```gmsh``` write method as from [here](http://jsdokken.com/src/pygmsh_tutorial.html). ```python import gmsh import pygmsh with pygmsh.geo.Geometry() as geom: rec = geom.add_rectangle(0, 1, 0, 2,...

A workaround I found for this in the interim is to use the ```*.geo_unrolled``` format instead of ```*.msh```. Works for the above environment settings (however didn't work when using gmsh==3.0.6).

A possibly more reliable workaround is to work with the fipy.meshes.mesh.Mesh class directly - which bypasses the GmshX class's need to load the mesh from file (which I have still...

Awesome, thanks @wd15. No rush on my end as the workaround I posted above got me past the blocking point for my work. In the interim I'll keep adding details...

Here is an updated version of the above workaround that works for both 2D and 3D volumetric meshes. ```python import itertools import numpy as np from meshio import Mesh as...