Notes on Face Meshing Controls for Mapped Meshing

Remember the following notes when using the Face Meshing controls for mapped meshing:

The table below provides an overview of types of faces and how various mesh methods handle when mapped Face Meshing controls are applied to them.

Mesh MethodFace Characteristic

Circular

Triangle

Annular

Internal Loops

Not supported. You must free mesh these faces.

Not supported. You must free mesh these faces. As side faces, triangle faces can be mapped to obtain a wedge mesh at one corner, depending on source face selection.

 

Supported. In the Details View, the Internal Number of Divisions option is activated so you can specify the number of divisions across the annular region. The option is set to 3 in the example below:

 

Not supported. You must free mesh these faces, but note the following: If there is just one internal loop, it is treated as an annular case. For example, if the model above were split in half, you would have a square annulus which would mesh similar to the circular annulus model.

Supported, but mesh quality is poor.

 

You can use inflation to obtain an O-Grid for better quality in corners.

 

Supported. Triangle faces are submapped to tri primitives.

 

As side faces, triangle faces can be mapped to obtain a wedge mesh at one corner, depending on source face selection.

 

Supported. In the Details View, the Internal Number of Divisions option is activated so you can specify the number of divisions across the annular region. The option is set to 3 in the example below:

 

Ignored for source faces. However, internal loops are supported for side faces. If this example is meshed top to bottom, and has mapped faces defined on the sides, it meshes as follows:

 

For more information on using mapped Face Meshing with side faces, see Side Face Handling of Imprinted Regions.

With fillets, chamfers, or large or small angles

Concerns over the mappability of faces may be different depending on whether the faces are source/target faces or side faces. For sweeping to be successful (regardless of whether Sweep, Thin Sweep, or MultiZone is used), all side faces (that is, all non-source/target faces) must be mappable. Ensuring side face mappability is most critical to ensure a successful swept mesh. Ensuring a source face can be mapped should be a lower priority, and your strategy for sweeping should account for this difference. You can use the Show>Mappable Faces option to help determine mappability of faces.

In addition to the mappability of each individual side face, the collective set of faces for a given side may present a problem. For example, for a collective set of faces, all parallel edges need to have the same number of divisions from the top to the bottom of the sweep. Ensuring all side faces of a swept body are mappable does not always ensure the body is sweepable. For example, if parallel edges of a mapped face change in direction, a source edge could become a side edge and make the body impossible to sweep. Also, edge splits on one face need to propagate through the collective set of faces while maintaining a reasonable quality mesh. Reducing the number of edge splits may simplify the sweeping and lead to a better quality mesh. This effect is the result of the simplification in the “interval edge assignment,” or the requirement for the mesher to have the same number of divisions along the sweep path.

Extending splits through the set of side faces may also help the mesher with the incremental edge assignments, as well as with constraining the grid lines along the sweep path to control the mesh quality. The imprinting that occurs with MultiZone creates further complications. See Side Face Handling of Imprinted Regions for more information.


Release 18.2 - © ANSYS, Inc. All rights reserved.