To compute the flux across the non-conformal boundary, ANSYS Fluent must first compute the intersection between the interface zones that make up the boundary. In the case of fluid-to-fluid zone interfaces and solid-to-solid zone interfaces, the resulting intersection produces an interior zone where the two interface zones overlap (see Figure 5.26: Completely Overlapping Mesh Interface Intersection). In the case of fluid-to-solid zone interfaces, a coupled wall zone is produced where the interface zones overlap (see The Coupled Wall Option).
Note: If the zones on either side of a solid-to-solid interface
are of differing materials, the interface must be treated as a coupled
wall instead of as an interior. If Fluent detects this scenario
during case read or initialization it will issue a warning and prompt
you to run the mesh/modify-zones/slit-interior-between-diff-solids TUI command.
If one of the interface zones extends beyond the other (Figure 5.27: Partially Overlapping Mesh Interface Intersection), by default ANSYS Fluent will create additional wall zones for the portion(s) of the boundary where the two interface zones do not overlap.
Fluxes across the mesh interface are computed using the faces resulting from the intersection of the two interface zones, not from the interface zone faces.
In the example shown in Figure 5.28: Two-Dimensional Non-Conformal Mesh Interface, the interface zones are composed of faces A-B and B-C, and faces D-E and E-F.
The intersection of these zones produces the faces a-d, d-b, b-e, and e-c. Faces produced in the region where the two cell zones overlap (d-b, b-e, and e-c) are grouped to form an interior or coupled wall zone (depending on the types of the adjacent cell zones), while the remaining face (a-d) forms a wall zone.
To compute the flux across the interface into cell IV, face D-E is ignored and instead faces d-b and b-e are used to bring information into cell IV from cells I and III.
While the previous discussion described the default treatment of a non-conformal interface, there are several options you can enable at the interface in order to revise the treatment of the fluxes and/or reduce the memory usage and processing time:
periodic boundary condition
periodic repeats
coupled wall
matching
mapped
static
These non-conformal interface options are described in the following sections.
Non-conformal interfaces can be used to implement a periodic boundary condition like that described for conformal periodic boundaries (see Periodic Boundary Conditions). The advantage of using a mesh interface is that, unlike the standard periodic boundary condition, the nodes of the two zones do not have to match one-for-one.
The interface zones that utilize the periodic boundary condition option (Figure 5.29: Non-Conformal Periodic Boundary Condition (Translational) and Figure 5.30: Non-Conformal Periodic Boundary Condition (Rotational)) are coupled in the manner described in the previous section, except that the zones do not overlap (that is, the zones are not spatially coincident at any point). In order to generate the new faces that will be used to compute the fluxes across the interface, the nodes of the first zone are either translated or rotated (about a given axis) onto the other zone. The distance/angle that the nodes are translated/rotated is called the “periodic offset”. The new faces will be defined between all of the combined nodes, and then applied to each of the original zones.
The periodic repeats option is appropriate when each of the interface zones is adjacent to a non-conformal periodic interface or a pair of conformal periodic zones (see Figure 5.31: Translational Non-Conformal Interface with the Periodic Repeats Option and Figure 5.32: Rotational Non-Conformal Interface with the Periodic Repeats Option). The periodic repeats option takes into account the repeating nature of the flow solutions in the two cell zones in the following manner. Wherever the interface zones overlap (that is, wherever interface zone 1 and 2 are spatially coincident), the fluxes on either side of the interface are coupled in the usual way. The portion of interface zone 1 that does not overlap is coupled to the non-overlapping portion of interface zone 2, by translating or rotating the fluxes by the periodic offset. This is similar to the treatment of non-conformal periodic boundary conditions. The periodic repeats option is typically used in conjunction with the sliding mesh model when simulating the interface between a rotor and stator.
As described previously, the typical function of non-conformal interfaces is to couple fluid zones, so as to permit fluid flow to pass from one mesh interface to the other. Another available option is to create a coupled wall boundary at the interface. In such a case, fluid flow would not pass across the interface, as the interface is acting as a wall zone. Coupled wall heat transfer, on the other hand, would be permitted. Such an interface is required if one or both of the cell zones is a solid. It is also allowable if both of the cell zones are fluids; for example, you can model a thin wall or baffle separating the two fluid zones. Figure 5.33: Non-Conformal Coupled Wall Interfaces illustrates coupled walls with both solid and fluid zones.
Note that coupled walls can also make use of the periodic repeats option. That is, both options can be invoked simultaneously. For details see Using a Non-Conformal Mesh in ANSYS Fluent.
When two interface zones do not match well (which could result from different mesh topologies, geometric misalignment, or the existence of large gaps), wall zones will be created on the interface. If, in such cases, you want to have only internal zones generated on the interface (that is, interior or wall / shadow pairs), it is best to use a matching interface. If the interface zones are completely overlapping (see Figure 5.26: Completely Overlapping Mesh Interface Intersection) as opposed to partially overlapping (see Figure 5.27: Partially Overlapping Mesh Interface Intersection) and so no wall zones are expected to be created on the mesh interface, it is recommended that you select the Matching option.
Note: The Matching option is also compatible with the periodic boundary condition option.
Figure 5.34: Matching Non-Conformal Wall Interfaces below shows two interface zones that do not match up well in the center -- the interface zone on the right has an inverted spike. Even with such a large mismatch, the Matching option still enables you to create an interface with only the interior zone.
When the Matching option is selected, ANSYS Fluent checks if one interface zone sits on top of the other and displays messages if there is an overlap of cell zones that are connected through a mesh interface (therefore making the interface invalid for use). Since the severity of zone overlap is different for matching interfaces and non-matching interfaces, ANSYS Fluent displays different messages accordingly.
For example, for non-matching interfaces:
Info: Interface zones overlap for mesh interface (interface-name). This could adversely affect your solution.
Likewise, for matching interfaces:
Warning: Interface zone overlaps for mesh interface (interface-name).
This could generate left-handed faces on the interface and make it invalid for use.The Mapped option is an alternative approach for modeling coupled walls between zones. This approach is more robust than the standard non-conformal interface formulations when the interface zones penetrate each other or have gaps between them. The Mapped option is useful in situations where using the standard non-conformal interface formulations causes the simulation to fail (as may occur when there is interface penetration or gaps between interfaces, causing the creation of left-handed faces at the interface).
Figure 5.35: Non-Conformal Mapped Interface with a Gap and Penetration shows significant penetration between the two interface zones and large gap. The mapped option allows you to create a coupled wall even with the large amount of penetration and gap shown in this image.
The Mapped option only works in conjunction with the Coupled Wall option. Enabling the Mapped automatically enables Coupled Wall.
You can use the Interface Options Dialog Box to modify the global settings for the mapped interfaces, as well as to convert existing mesh interfaces (either all of them or just those that have penetrating zones) to use the Mapped option.
You can confirm that you created good quality mapped interfaces by performing a mesh
check. If you have mapped interfaces that did not pass the quality check, Fluent will
suggest that you use the text command
define/mesh-interface/improve-quality, which allows you to
increase the interface tolerance to improve the quality of the mapped interfaces.
Note the following limitations when using the Mapped option:
The Mapped option can only be applied if at least one side of the interface consists of only solid zones.
The Mapped option is not compatible with shell conduction.
Thermal coupling calculations will not be performed at mapped interfaces for the Eulerian multiphase model.
No other interface options besides Coupled Wall are allowed with the Mapped option.
For the S2S model, the Face to Face basis for the view factors is not compatible with mapped interfaces for polyhedral meshes.
Mapped interfaces are not supported with the density-based solver.
Mapped interfaces are not supported with the Lagrangian discrete phase model.
Mapped interfaces are not supported with moving / deforming meshes.
For a default mesh interface or when the Coupled and/or Matching options are enabled, ANSYS Fluent will automatically create zones that will be needed if the interface should change due to motion (from moving reference frames or sliding meshes) or deformation. If you know in advance that the interface zones will not be moving or deforming relative to each other at the interface, then (and only then) it is recommended that you enable the Static option. The Static option prevents the creation of such zones, and thus reduces the memory usage and processing time (for both the creation of the interface and the running of the calculation). This reduction can be significant, especially when there are many zones on both sides of the interface.
Warning: If the Static option is applied at an interface that does end up undergoing relative motion or deformation, the results will be incorrect.
Note that the Static option is not limited to steady-state cases.
The following sub-sections describe the automatic naming conventions for each type of non-conformal interface:
The automatic naming convention for interface boundary zones is as follows: <mesh interface name> (user-provided) - side (1 or 2) - wall - <interface zone name>.
The automatic naming convention for interface wall zones is as follows: <mesh interface name> (user-provided) - wall1 (only wall1, because the other wall is the shadow of wall1) - <connection number> (1–m, where m is the number of zones in interface zone side 1) - <connection number> (1–n, where n is the number of zones in interface zone side 2) - shadow (for interface wall zone side 2 only).
The automatic naming convention for interface interior zones is as follows: <mesh interface name> (user-provided) - interior - <connection number> (1–m, where m is the number of zones in interface zone side 1) - <connection number> (1–n, where n is the number of zones in interface zone side 2).
The automatic naming convention for interface boundary zones is as follows: <mesh interface name> (user-provided) - side (1 or 2) - wall - <interface zone name>.
The automatic naming convention for interface interior zones is as follows: <mesh interface name> (user-provided) - periodic.
The automatic naming convention for interface interior zones is as follows: <mesh interface name> (user-provided) - periodic.
The automatic naming convention for interface boundary zones is as follows: <mesh interface name> (user-provided) - side (1 or 2) - wall - <interface zone name>.
The automatic naming convention for interface wall zones is as follows: <mesh interface name> (user-provided) - wall1 (only wall1, because the other wall is the shadow of wall1) - <connection number> (1–m, where m is the number of zones in interface zone side 1) - <connection number> (1–n, where n is the number of zones in interface zone side 2) - shadow (for interface wall zone side 2 only).
For example,
> define/mesh-interfaces/list
List of Mesh Interfaces
Interface Name: cw:01
Interface Options: Coupled
Description Name ID Area Area Percentage
---------------------- ------------------------------ ---------- ------------------ -----------------
Interface-Zone-1 a2 17 0.1707190424
Interface-Zone-1 a1 13 0.1707191467
Interface-Zone-2 b1 4 36.7499923706
Boundary-Zone-2 cw:01-side2-wall-b1 53 36.4085540771 99.070915%
Interface-Wall-Zone-1 cw:01-wall1-1-1 50 0.1706306934 99.948250%
Interface-Wall-Zone-1 cw:01-wall1-2-1 49 0.1706308126 99.948257%
Interface-Wall-Zone-2 cw:01-wall1-1-1-shadow 54 0.1706306934 0.464301%
Interface-Wall-Zone-2 cw:01-wall1-2-1-shadow 55 0.1706308126 0.464302%
The automatic naming convention for interface interior zones is as follows: <mesh interface name> (user-provided) - interior - <connection number> (1–m, where m is the number of zones in interface zone side 1) - <connection number> (1–n, where n is the number of zones in interface zone side 2).
The automatic naming convention for interface boundary zones is as follows: <mesh interface name> (user-provided) - side (1 or 2) - wall - <interface zone name>.
The automatic naming convention for interface wall zones is as follows: <mesh interface name> (user-provided) - wall (1 or 2) - <connection number> (1–m, where m is the number of zones in interface zone side 1) - <connection number> (1–n, where n is the number of zones in interface zone side 2).
For example,
> define/mesh-interfaces/list
List of Mesh Interfaces
Interface Name: map:01
Interface Options: Mapped
Description Name ID Area Area Percentage
---------------------- ------------------------------ ---------- ------------------ -----------------
Interface-Zone-1 a2 17 0.1707190424
Interface-Zone-1 a1 13 0.1707191467
Interface-Zone-2 b1 4 36.7499923706
Boundary-Zone-2 map:01-side2-wall-b1 32 36.4085540771 99.070915%
Interface-Wall-Zone-1 map:01-wall1-a2 28 0.1707190424 100.000000%
Interface-Wall-Zone-1 map:01-wall1-a1 27 0.1707191467 100.000000%
Interface-Wall-Zone-2 map:01-wall2-b1 29 0.3414205313 0.929036%