In the current version of ANSYS Fluent, non-conformal interface calculations are handled using one of three approaches depending on the type of interface. Coupled Wall interfaces are handled using interface boundary metrics and Mapped interfaces use a projection approach. The interface boundary metrics and projection approach are both robust algorithms that avoid creating left-handed faces and are particularly useful when you have complex geometries.
The remaining types of non-conformal interfaces are handled using a virtual polygon approach. The virtual polygon approach stores the area vector and centroid of the polygon faces. This approach does not involve node movement and cells are not necessarily water-tight cells. Hence gradients are corrected to take into account the missing face area. Note that in transient cases, the stationary non-conformal interfaces will be automatically preserved by ANSYS Fluent during mesh update.
Previous versions (16.0 and earlier) of Fluent used the virtual polygon approach for all non-conformal interfaces. The interface boundary metrics is a more robust approach for creating coupled wall interfaces than the virtual polygon approach because it avoids creating left-handed faces. Older versions of Fluent (6.1 or earlier) used a triangular face approach, which triangulated the polygon intersection faces and stored triangular faces. This approach involved node movement and water-tight cells, and was not as stable as the virtual polygon approach. Note that case files created in releases prior to 16.0 can be read and run normally in the current version of Fluent unless you recreate any of the interfaces. Recreated coupled wall interfaces will use interface boundary metrics and all other recreated interfaces will use the virtual polygon approach.
It is possible that distorted meshes may be produced during sliding mesh calculations, generating left-handed faces. You cannot obtain a flow solution until all of the faces are “right handed”, and so ANSYS Fluent corrects the left-handedness of these faces automatically. In extreme cases, the left-handed faces cannot be fully corrected and are deleted automatically, so that the solution does not diverge.
Left-handed cells can also be created for the geometries that contain sharp edges and corners, which may affect the final solution. For such geometries, you should first separate the zones and then create the interfaces separately to get the better solution.
The additional input of the angle/translation vector at the angle/translation-vector prompt in the console may be
required to recreate face-periodic interfaces. Also, with the current
mesh interface algorithm in parallel, there is no need for encapsulation.