ENH: support multiple zones for topo set sources (#1060)

- uses the keywords 'zones' and 'zone' to avoid potential conflicts
  with a named topoSet action, but accepts 'name' for compatibility.
This commit is contained in:
Mark Olesen
2018-10-29 12:54:30 +00:00
parent 26f6f4257a
commit c2e58dca64
25 changed files with 195 additions and 158 deletions

View File

@ -46,13 +46,15 @@ FoamFile
// // Cells in cell zone
// source zoneToCell;
// {
// name ".*Zone"; // Name of cellZone, regular expressions allowed
// zones (".*Zone"); // Name of cellZones, regular expressions allowed
// zone ".*Zone"; // Name of cellZone, regular expressions allowed
// }
//
// // Cells on master or slave side of faceZone
// source faceZoneToCell;
// {
// name ".*Zone"; // Name of faceZone, regular expressions allowed
// zones (".*Zone"); // Name of faceZones, regular expressions allowed
// zone ".*Zone"; // Name of faceZone, regular expressions allowed
// option master; // master/slave
// }
//
@ -190,7 +192,7 @@ FoamFile
// // All faces of faceZone
// source zoneToFace;
// {
// name ".*Zone1"; // Name of faceZone, regular expressions allowed
// zone ".*Zone1"; // Name of faceZone, regular expressions allowed
// }
//
// // Faces with face centre within box
@ -240,7 +242,7 @@ FoamFile
// // All points in pointzone
// source zoneToPoint;
// {
// name ".*Zone"; // name of pointZone, regular expressions allowed
// zone ".*Zone"; // name of pointZone, regular expressions allowed
// }
//
// // Points nearest to coordinates