Topology detection of overset interfaces in Fluent is automatic and does not require user input. However, for it to work well, it requires that the provided meshes are of sufficient quality, particularly when dealing with meshes that have overlapping boundaries.
Overset meshes are built from parts that can be meshed independently, which can lead people to think of this as a much simpler process for mesh generation. This is not always the case, as considerable thought is often required to generate good meshes for the individual components to avoid problems during overset interface initialization.
If you are faced with issues during the initialization of an overset interface, there is most often no recovery without making changes to the mesh. You must analyze the cause of the issue, using the available postprocessing and diagnostic tools, and improve the mesh before the simulation can continue.
When diagnosing overset interface failures, it can be convenient to use the text
commands define/overset-interfaces/intersect and
define/overset-interfaces/clear (available after enabling the
expert tools available under
define/overset-interfaces/options/expert) to execute and clear
the hole cutting without having to initialize the solution.
The issues most often encountered are:
These are the issues that can cause problems with flood filling:
Flood filling of dead cells will fail if Fluent inadvertently identifies seed cells inside of the fluid zone instead of outside. This can occur as a result of complexities in the topology or geometry of the boundary zones, or because of mesh resolution issues. It manifests itself as an entire fluid region, or a complete cell zone, being marked as dead.
This issue can be diagnosed by using the list command with the overset verbosity set
to 1 (see Overset Interface listing).
You can use the TUI command
define/overset-interfaces/debug-hole-cut (available after
enabling the expert tools available under
define/overset-interfaces/options/expert) to identify the
problematic seed cells. This command allows you to execute the hole cutting process on a
specific overset interface and mark the seed cells. When the flood fill option of the
debug command is disabled, it will create two adaption registers with dead cells and
seed cells (see Displaying Registers). The dead marks show the cells cut
by the physical boundary zones. The seed cells (mark0 adaption register) show the cells
that will be used for flood filling. It is critical that all the seed cells are located
inside bodies or outside of the computational domain. If there is a seed cell in the
fluid region, it will cause a flood fill failure.
It is not possible to recover from flood filling failure without making changes to the model.
If no bad seed cells are found, as described in Incorrect Seed Cells, and there are overlapping boundaries, it is likely that the overlapping boundaries do not match sufficiently and the flood filling of dead cells leaks from the inside of the body to the outside. As a result, a complete cell zone can disappear, due to having only dead cells. The permissible tolerance between overlapping boundary zones is at most one cell-size in the wall normal direction. This can be restrictive when dealing with prismatic boundary layer meshes with high cell aspect ratios at the wall.
The define/overset-interfaces/debug-hole-cut text command,
with the flood filling option enabled, marks the cells that will be converted to dead
cells (as a result of flood filling) and generates a mark1 adaption register containing
those cells. If your model suffers from this leakage, you must improve the quality of
the mesh, by making the overlapping boundary zones match better.
If a receptor cell cannot find a valid donor cell, then it becomes an orphan cell. The presence of orphan cells generally indicates that there is insufficient overlap between meshes or that the mesh resolutions do not match well. As a result, the receptors are either finding no candidate donor cells, or invalid candidates (dead or receptor cells).
Orphan cells can be an issue when walls of different meshes are in proximity. You must have at least four cells in a gap, such as the ones between the walls in Figure 5.44: Valid Overset Meshes with Components in Close Proximity, in order to have a good connection between the meshes—otherwise orphan cells are created. When a receptor overlays another receptor, it becomes an orphan.
See Figure 5.55: Invalid Overlap Creating Orphans for an example of insufficient overlap causing the creation of orphan cells. For information on visualizing orphan cells, see Postprocessing Overset Meshes. Figure 5.54: Valid Overlap shows meshes overlapping sufficiently to avoid the creation of orphan cells.
You can mark the orphan cells, as described in Overset Cell Marks, which will likely indicate where the mesh overlap must be increased. Sometimes, increasing the mesh resolution can lead to a sufficient increase in mesh overlap. If mesh resolution is the issue, you can also use local mesh adaption, along with mesh modification, to refine the mesh. Most often the mesh requiring adaption is the mesh where the orphan should find its donors, and not the mesh zone containing the orphan.
If the presence of orphan cells in the simulation is unavoidable and you proceed with a calculation, by default the solver applies a numerical treatment that attempts to assign reasonable values to the orphan cells. This treatment has been found to prevent divergence in some instances, allowing the solution to proceed; however, the orphan cell treatment does not guarantee the solution quality and robustness a priori. The success of this treatment is case dependent, and difficult to predict based on orphan cell counts. It is therefore highly recommended that you make every effort to eliminate orphan cells by modifying the mesh, as described previously.