When generating meshes for Polyflow-based systems using the Ansys Meshing application,
note that you can assign names to the surfaces and volumes of the geometry by
defining Named Selections. Such names will be saved and recognized by any downstream
application associated with the mesh, including Polydata, Polyflow, Polyfuse,
Polystat, and Ansys CFD-Post. In this way, you can use the names of the boundaries and
sub-domains to easily identify the corresponding geometric entity. For example: the
boundary where you will impose a given flow rate could be named
inflow or inlet; a boundary
where the flow will exit the domain could be named outlet
or outflow. This is particularly useful when you have a
large number of boundaries.
When entering a name for a Named Selection, note the following:
The names should not be too long, as Polyflow applications will only retain the last 12 characters of the names you assign.
Certain characters are incompatible with Polyflow applications, and so will be replaced automatically with an acceptable character within the Polyflow applications. The following characters are replaced with an underscore (
_): dash (-), space ( ), colon (:), semicolon (;), period (.), comma (,), exclamation point (!), forward slash (/), backslash (\), left square bracket ([), right square bracket (]), and number sign / pound / hash (#). Also, an asterisk (*) is replaced with the letterx. It is recommended that you try to avoid using such incompatible characters in your Named Selections.The names you define should be distinct. If Polydata detects identical names, a suffix “_j” will be added to the names, where j is an index number that makes each of the entities unique.
You can create Named Selections to specify specialized modeling conditions on edges for 2D or shell geometry; and edges and faces for 3D geometry. The exported mesh file will contain the mesh nodes and elements associated with those Named Selections in PMesh format. For 2D geometries, you can define 1D internal and external PMeshes; for 3D geometries, you can define 2D external PMeshes and 1D and 2D internal PMeshes. Note that the PMeshes cannot be defined on the border. For more information about PMeshes, see the Polyflow User's Guide.
Note that the downstream Polyflow applications assign numerical IDs to the domains, boundaries, and PMeshes based on the alphabetical order of the names (without consideration of whether the letters are upper or lower case). These IDs are referenced by Polydata and Polyflow when reading the Polyflow mesh file (whereas CFD-Post references the name itself). Therefore, if you delete a Named Selection after it has been used in a Polyflow simulation and recreate a new one with the same name, the ID will be the same as the original, and you can conduct further simulations without conflict.