When an overset interface is initialized, there are three main steps that Fluent completes to establish connectivity between the participating zones:
Hole cutting is the process by which cells lying outside of the flow region (that is, inside bodies and outside of the computational domain) are marked as dead cells. This is achieved by marking all the cells that are cut by physical boundary zones (wall, inlet, outlet, symmetry, and so on), and marking seed cells determined to lie outside the flow region for subsequent flood filling of dead cells. The result of this flood filling is a valid overset mesh with maximum mesh overlap.
Figure 5.49: Overset Component and Background Meshes Before Hole Cutting and Figure 5.50: Overset Component and Background Meshes After Hole Cutting show an overset mesh before and after hole cutting. All of the background cells that are bounded or cut by the cylinder wall are classified as dead during hole cutting. The maximum overlap mesh shown in Figure 5.50: Overset Component and Background Meshes After Hole Cutting is a valid overset mesh, however, it may not be ideal. An overly large overlap between component and background meshes is computationally inefficient (the equations are solved in more cells than are necessary). Additionally, the cell sizes of the overlapping meshes may vary greatly—this affects the data interpolation and is detrimental to solution quality. Ideally meshes should transition in regions of similar resolution.
Overlap minimization is used to minimize mesh overlap among different component and background meshes by converting additional solve cells into receptor cells and turning unnecessary receptors into dead cells. During this process, a solve cell is turned into a receptor cell if the cell can find a suitable donor cell with higher donor priority. By default, smaller cells have a higher donor priority. Thus, in mesh overlap areas, without additional user input the solver attempts to obtain the solution on the finest local mesh. The resulting mesh interface moves to an area where the meshes are more comparable in cell size, leading to better solution quality. Figure 5.51: Overset Component and Background Meshes After Overlap Minimization shows the cylinder case from the previous figure after the overlap minimization step.
Note that overlap minimization is not literally minimizing the mesh overlap. The overlap minimization is based on a flood filling of receptor cells, wherever suitable solve cells with higher donor priority can be found. The resulting actual mesh overlap depends on the local donor priority distribution.
Also note that with overlap minimization, data interpolation between cell zones does not necessarily occur at the overset boundaries. The purpose of specifying an overset boundary is primarily to specify that overset mesh coupling should happen, and not where it should occur.
You have the option to specify different donor priority methods
in order to control the location of the overset interface. The text user interface command
define/overset-interfaces/options/donor-priority-method allows
you to specify that the donor priority is based either on the cell size (proportional to
the inverse of the cell volume) or the boundary distance (proportional to the inverse of
the distance to the closest boundary). Overlap minimization with donor priority based on
cell size (default) works best if the component mesh resolution is fine near walls and
increases away from walls, to spacings similar to—or larger than—the
background mesh (see Figure 5.49: Overset Component and Background Meshes Before Hole Cutting for an example of
this type of mesh). If the overlapping meshes have uniform and nearly identical
resolutions, then overlap minimization based on cell size will not reduce the overlap and
a donor priority based on the boundary distance should be used instead. The following two
figures illustrate an overset mesh before and after initialization where a donor priority
based on boundary distance is used. Note that for the evaluation of donor priorities based
on boundary distance, all boundaries (including inlets, outlets, and so on) are used for
the distance evaluation.
You have the option for additional control over the overlap
minimization process by assigning grid priorities to component and background meshes,
using the text user interface command
define/overset-interfaces/grid-priorities. Meshes (that is,
cell zones) with higher grid priorities are favored during the minimization process,
irrespective of the local cell donor priority. If two cell zones have the same grid
priority, then the cell donor priorities are used for the overlap minimization. For
example, by assigning a higher grid priority to a coarser mesh, you can force Fluent to
minimize the finer mesh and obtain the solution on the coarser mesh, even if the donor
priority is based on cell size. Using grid priorities, similar to using donor priority
based on boundary distance, is helpful if local mesh distributions are irregular, and
produce overlap regions that are irregular as well. Note that the grid priorities take
precedence over the donor priorities.
You have the option of disabling overlap minimization by using
the text command
define/overset-interfaces/options/minimize-overlap?. This
command is only available globally and applies to all overset interfaces in the
domain.
The donor search is the final step in establishing the domain connectivity. Fluent searches other meshes for valid solve cells for each receptor. The solve cell containing the cell centroid of the receptor cell, along with its connected solve cells, are used as donor candidates for a given receptor. Each receptor must have at least one valid donor cell.
There must be four or more cells in the overlap of both meshes to ensure a successful donor search. The receptor cells, which form the fringe layer of a mesh zone, must overlap sufficiently with the opposite mesh, such that they find valid solve cells as donors. For an example of valid mesh overlap, see Figure 5.54: Valid Overlap.