Zone Type Assignment

This section describes zone naming and the zone type assignment process.

Zone Naming

By default, zones are named after the part and body from which they are derived. For example, part “part” and body “solid body” will result in a zone name of “part-solid_body.” When the zone name is created:


Note:  If you set the Auto Zone Type Assignment option to Off (as described in Meshing Options on the Options Dialog Box), all boundary zones are set to the default zone type WALL.


If a boundary zone was created for a Named Selection (as described in Classes of Zone Types in ANSYS Fluent), the name of the boundary zone is set to the name of the Named Selection.

In cases where the zone naming process could lead to conflicting zone names (for example, in a situation where the potential exists for a zone name that is already in use to be used to name a new zone), one of the following approaches is used:

Because part and body names influence the creation of continuum zones in ANSYS Fluent, it is best practice to assign distinct part and body names that follow these rules:

Zone Type Assignment Process

The section is applicable to boundary zones only.

The zone type is derived from the zone name. To assign zone types, the string comparison operations detailed below are performed during the export process. These string comparison operations, which correspond to the naming conventions described in Standard Naming Conventions for Naming Named Selections, are applied in the order in which they are listed below (that is, at first an exact match is tested, after that a partial match is tested, etc.) and are always case-insensitive. For example, fan, Fan, FAn, and faN are all exact matches for the 'FAN' string comparison and result in a zone type of FAN being assigned.

When the search operation begins, it will start by searching the first portion (or sub-string) of the string and if no match is found, it will search for a match anywhere in the string. For example, if a Named Selection with the name wall_inlet_flange is defined, it will be exported as zone type WALL. The 'inlet' portion of the name will have no effect on zone type assignment.

In some cases a name may match multiple patterns or rules, and the expected zone type may not be assigned. For this reason it is strongly advisable to use only unambiguous names that exactly match one of the rules presented below.

Once they are exported, names are all lowercase. The single quotation marks that are shown enclosing the strings below are not considered during the string comparison operations.

  1. Exact matches are checked:

    'AXIS'
    'EXHAUST_FAN'
    'FAN'
    'INLET_VENT'
    'INTAKE_FAN'
    'INTERFACE'
    'INTERIOR'
    'MASS_FLOW_INLET'
    'OUTFLOW'
    'OUTLET_VENT'
    'POROUS_JUMP'
    'PRESSURE_FAR_FIELD'
    'PRESSURE_INLET'
    'PRESSURE_OUTLET'
    'RADIATOR'
    'RECIRCULATION_INLET'
    'RECIRCULATION_OUTLET'
    'SYMMETRY'
    'THIN'
    'VELOCITY_INLET'
    'WALL'
  2. Partial matches are considered only if an exact match was not found in step 1:

    'AXIS'
    {'EXHAUST' && 'FAN'}
    'FAN'
    {'INLET' && 'VENT'}
    {'INTAKE' && 'FAN'}
    'INTERFACE'
    'INTERIOR'
    {'MASS' && 'FLOW' && 'INLET'}
    'OUTFLOW'
    {'OUTLET' && 'VENT'}
    {'POROUS' && 'JUMP'}
    {'PRESSURE' && 'FAR' && 'FIELD'}
    {'PRESSURE' && 'INLET'}
    {'PRESSURE' && 'OUTLET'}
    'RADIATOR'
    {'RECIRCULATION' && 'INLET'}
    {'RECIRCULATION' && 'OUTLET'}
    'SYMMETRY'
    {'VELOCITY' && 'INLET'}
  3. String comparisons to the special abbreviations listed in the table below are performed if no match was found in step 1 or step 2. If an exact match to one of the strings listed in the table is found, the corresponding zone type is assigned:

    When a match for this string is found...This zone type is assigned...
    'CNDBY'
    INTERFACE
    'EXFAN'
    EXHAUST FAN
    'IFACE'
    INTERFACE
    'IN'
    PRESSURE INLET
    'INFAN'
    INTAKE FAN
    'INTERFACE'
    INTERFACE
    'IVENT'
    INLET VENT
    'MASFI'
    MASS FLOW INLET
    'OUT'
    PRESSURE OUTLET
    'OVENT'
    OUTLET VENT
    'PFAR'
    PRESSURE FAR FIELD
    'PORJ'
    POROUS JUMP
    'PRESF'
    PRESSURE FAR FIELD
    'PRESI'
    PRESSURE INLET
    'PRESO'
    PRESSURE OUTLET
    'PRESS'
    PRESSURE FAR FIELD
    'RAD'
    RADIATOR
    'RINLT'
    RECIRCULATION INLET
    'ROUT'
    RECIRCULATION OUTLET
    'SLIDE'
    INTERFACE
    'SYM'
    SYMMETRY
    'SYMET'
    SYMMETRY
    'SYMM'
    SYMMETRY
    'VELF'
    VELOCITY INLET
    'VELI'
    VELOCITY INLET
  4. Partial matches are considered if no match was found in steps 1, 2, or 3. If a partial match to one of the strings listed in the following table is found, the corresponding zone type is assigned:

    When a match for this string is found...This zone type is assigned...
    'EXHAUST'
    EXHAUST FAN
    'INLET'
    VELOCITY INLET
    'OUTLET'
    PRESSURE OUTLET
    'SYM'
    SYMMETRY
    'THIN'
    THIN
    'WALL'
    WALL
  5. If none of the string comparisons described in steps 1, 2, 3, or 4 result in a match, the boundary zone is assigned zone type WALL by default.


Note:
  • If you are using CutCell and are defining Named Selections for 3D bodies, it is best practice to avoid the use of ANSYS Fluent keywords. For example, do not include the string "inlet" in the Named Selection name.

  • When Named Selections defined in the ANSYS DesignModeler application are required in the Meshing application, you must set the appropriate geometry import options to ensure the Named Selections will be transferred properly. Refer to Importing DesignModeler Named Selections into the Meshing Application for details.

  • For assembly meshing algorithms, the names of parts, bodies, and Named Selections should be limited to 64 characters.


Handling Periodic Regions

To export matching face meshes as PERIODIC boundary zone types, you must perform the following steps:

  1. Define matching face meshes (for 3D) or edge meshes (for 2D only) as Periodic Regions or Cyclic Regions in a Symmetry folder or as Match Controls or Arbitrary Match Controls.

  2. Define two Named Selections for each periodic boundary condition, one Named Selection per side, ensuring that ”periodic” is used in the name (for example, periodic1A, periodic1B...). The same Named Selections could be used to define the periodic or cyclic region.


Note:
  • Periodic regions must belong to the same Fluent mesh cell zone to ensure a successful export.

  • When match controls on faces are used, only one periodic or cyclic transformation is supported (for example, you can export multiple match controls as long as they use the same coordinate system and have the same angle/translation).


Special Cases

Be aware of the following special cases related to boundary zone type assignment:


Release 18.2 - © ANSYS, Inc. All rights reserved.