This PR resolves an issue with amorphous and void phases in the gmsh output.
For example 1, switching to gmsh created a TriMesh that look like this:
After the switch, the mesh looks like this:
Approach
The regions and facets of the PolyMesh are all considered physical in the gmsh input geometry. Once the mesh has been created, elements in void regions are removed and facets between amorphous regions of the same phase are removed.
The boundaries between amorphous regions are preserved in the TriMesh. This is an artifact of how a geometry is defined in gmsh. The image below shows all the boundaries between regions. These boundaries are apparent in the TriMesh output.
PR Checklist
[ ] All tox commands succeed
[x] Docs have been added / updated (for bug fixes / features)
PR Summary
Purpose
This PR resolves an issue with amorphous and void phases in the gmsh output.
For example 1, switching to gmsh created a TriMesh that look like this:![trimesh_was](https://user-images.githubusercontent.com/41959581/118292662-df5e4480-b4a6-11eb-8de9-9c2532c266ca.png)
After the switch, the mesh looks like this:![trimesh_is](https://user-images.githubusercontent.com/41959581/118292691-e422f880-b4a6-11eb-9b9f-ec60df68ef01.png)
Approach
The regions and facets of the PolyMesh are all considered physical in the gmsh input geometry. Once the mesh has been created, elements in void regions are removed and facets between amorphous regions of the same phase are removed.
The boundaries between amorphous regions are preserved in the TriMesh. This is an artifact of how a geometry is defined in gmsh. The image below shows all the boundaries between regions. These boundaries are apparent in the TriMesh output.![polymesh](https://user-images.githubusercontent.com/41959581/118293239-71fee380-b4a7-11eb-9c5b-f579dff1fdd2.png)
PR Checklist
tox
commands succeed