2.1. Prerequisites for the Fluent Guided Workflows

The workflows rely on starting with a properly defined CAD geometry, and can support geometries that contains multiple bodies, sharing common faces, or even a single, fully enclosed body. To verify that an assembly of bodies are fully connected, use the Force Share option in SCDM, and share any faces that are found. If Force Share is not successful, the workflow will try to connect the remaining unconnected faces. The workflow supports named selections from Ansys DesignModeler (DM) as well as groups from Ansys SpaceClaim Direct Modeler (SCDM) if these are applied on faces (not bodies). These entities will appear as labels in the workflow.


Important:  The use of named selections (DM) and groups (SCDM), for faces surrounding openings (for solid models) and for areas where local sizing is needed, is recommended to easily identify these locations in the workflow. Using named selections and groups will also improve persistence during design changes and improve the performance for larger models.

The workflow recognizes typical naming conventions on boundaries, such as "inlet," "outlet," "far-field," "symmetry," "wall," "interior," or "internal." More precisely, the changing of Fluent boundary types based on name patterns is controlled by an advanced option, which is enabled by default. When enabled, the following patterns and corresponding zone types are applied on all zones:

  • "*inlet*" maps to a velocity-inlet zone

  • "*outlet*" maps to a pressure-outlet zone

  • "*symmetry*" maps to a symmetry zone

  • "*far*field*" maps to a pressure-far-field zone

  • "*mass*inlet*" maps to a mass-flow-inlet zone

  • "*press*inlet*" maps to a pressure-inlet zone

  • "*mass*outlet*" maps to a mass-flow-outlet zone

  • "*outflow*" maps to an outflow zone

  • "*inlet*vent*" maps to an inlet-vent zone

  • "*outlet*vent*" maps to an outlet-vent zone

  • "*intake*fan*" maps to an intake-fan zone

  • "*exh*fan*" maps to an exhaust-fan zone

  • "*fan*" maps to a fan zone

  • "*porous*jump*" maps to a porous-jump zone

  • "*radiator*" maps to a radiator zone

  • "*overset*" maps to an overset zone


Note:  The boundary type "multiple-types" is automatically assigned to labels containing zones with conflicting boundary types.



Note:  Only shrink-wrapped bodies from SCDM/Discovery geometries should include the string "wrap." Normal selections should not include this pattern.


For internal zones (that is, internal zones shared by multiple regions), the following patterns and corresponding zone types are applied:

  • "*internal*" or '*interior*' maps to an internal zone

  • "wall" maps to a wall zone

  • "fluid" or prefixes using "enclosure" or "air" map to a fluid region

Using these naming conventions on boundaries will, by default, cause them to be assigned to corresponding Fluent zone types. Consequently, it is not recommended to use any of these naming conventions within file names or within bodies or parts in the model. Similarly the use of "fluid" or "enclosure" is, by default, used to identify fluid regions on bodies. Consequently, it is not recommended to use these naming conventions within boundary names. In addition, the use of "unknown" should also be avoided.



Note:  The following should be noted with respect to geometry zones and labels:

  • Geometry zones will no longer use the "geom-" prefix. Instead, geometry zones will now use the "origin-" prefix.

  • Geometry labels will no longer use the "object" prefix.