diff --git a/applications/utilities/mesh/manipulation/splitMeshRegions/splitMeshRegions.C b/applications/utilities/mesh/manipulation/splitMeshRegions/splitMeshRegions.C index 88ca441e98..7da3c22269 100644 --- a/applications/utilities/mesh/manipulation/splitMeshRegions/splitMeshRegions.C +++ b/applications/utilities/mesh/manipulation/splitMeshRegions/splitMeshRegions.C @@ -39,17 +39,29 @@ Description - mesh with cells put into cellZones (-makeCellZones) Note: + - cellZonesOnly does not do a walk and uses the cellZones only. Use + this if you don't mind having disconnected domains in a single region. + This option requires all cells to be in one (and one only) cellZone. + + - cellZonesFileOnly behaves like -cellZonesOnly but reads the cellZones + from the specified file. This allows one to explicitly specify the region + distribution and still have multiple cellZones per region. + + - useCellZonesOnly does not do a walk and uses the cellZones only. Use + this if you don't mind having disconnected domains in a single region. + This option requires all cells to be in one (and one only) cellZone. + + - Should work in parallel. cellZones can differ on either side of processor boundaries in which case the faces get moved from processor patch to directMapped patch. Not - ery well tested. + very well tested. + - If a cell zone gets split into more than one region it can detect the largest matching region (-sloppyCellZones). This will accept any region that covers more than 50% of the zone. It has to be a subset so cannot have any cells in any other zone. - - useCellZonesOnly does not do a walk and uses the cellZones only. Use - this if you don't mind having disconnected domains in a single region. - This option requires all cells to be in one (and one only) cellZone. + - writes maps like decomposePar back to original mesh: - pointRegionAddressing : for every point in this region the point in the original mesh @@ -1137,63 +1149,6 @@ EdgeMap