"...db/functionObjects/writeLocalObjects/writeLocalObjects.H" did not exist on "b78e8b6e51e76c40475a6900a6c9d24d04a7c00d"
splitMeshRegions adds all cells to cellZone
Functionality to add/problem to solve
(Brief scope) splitMeshRegions -cellZones will split the mesh according to the cellZones. It then keeps all the zones in the corresponding cellZone so now all cells in a region are in the cellZone. This can give problems if other cellZones are needed.
Target audience
cht cases which are generated from a single mesh
Proposal
- explicitly remove the cellZones (since all the cells in the region are in the cellZone) when running splitMeshRegions -cellZones
- or suppress warnings from e.g. reconstructParMesh about cells being in multiple cellZones
What does success look like, and how can we measure that?
E.g. tutorials/heatTransfer/chtMultiRegionSimpleFoam/cpuCabinet which does
- splitMeshRegions -cellZones
- topoSet
- reconstructParMesh