Virtual bodies are supported for assembly meshing algorithms only. If your model does not contain a “solid” to represent a flow region, a virtual body can be defined so that you can mesh the flow region without having to use the DesignModeler application or another solid modeler to model it. Virtual bodies are extremely beneficial in cases where it is not practical to extract flow volumes in a modeler. They can be defined by material point only, or by material point and a group of fluid surfaces.
As defined by a material point, the virtual body is an object that is defined by a coordinate system representing the origin of a material, and which extends from the origin until it reaches the face of another solid (i.e., as when a ray is traced from the origin to the closest solid).
The two main reasons for using a group of fluid surfaces to help define a virtual body are performance and mesh quality.
For example, consider a case involving a large assembly for which you want to analyze a small flow volume but have no interest in the solid mesh. If you define the virtual body by material point only, assembly meshing refines and resolves every solid in the assembly, and finally, using mesh separation and the material point, identifies the flow volume and discards the solid mesh. However, if you select a group of fluid surfaces to help define the virtual body, assembly meshing resolves only the boundaries of the fluid surfaces in the group; essentially, it ignores all other boundaries. This approach typically speeds up mesh generation by a factor of two or more.
With respect to mesh quality, using a group of fluid surfaces to help define a virtual body is a good idea if you have a fluids-only problem (Keep Solid Mesh is set to No) where within the solids there are 3D details and/or bodies that are smaller than the minimum size and hence would be problematic to resolve.
If fluid surface creation using the Extend to Connection option “leaks” to the outside of the domain, the leak needs to be closed. This approach provides an alternative way of detecting leaks. Extend to Connection is discussed in more detail below.
Virtual bodies and fluid surface objects are not supported when Meshing application capabilities are accessed from within the Mechanical application.
A virtual body and the optional group of fluid surfaces that is used to help define it are represented in the Tree Outline by Virtual Body objects and Fluid Surface objects respectively. A material point must be specified when a Fluid Surface object is being used to help define a virtual body. Both the Fluid Surface object and the Virtual Body object will remain underdefined until the material point is specified.
The Fluid/Solid material property for a virtual body is always set to Fluid (read-only).
The steps for defining a virtual body are presented here.
Select the Geometry object in the Tree Outline.
Insert a Virtual Body object into the Tree using either of these methods:
Right-click on the Geometry object and select Insert > Virtual Body from the context menu.
Choose Virtual Body on the Geometry context toolbar.
Note: If this is the first Virtual Body object to be inserted, a Virtual Body Group object will be inserted into the Tree along with the Virtual Body object as its child object.
In the Details View, specify a value for Visible. The default is Yes. If set to No, the resultant mesh of the virtual body will not appear in the Geometry window.
Specify a value for Suppressed. The default is No. If set to Yes, the virtual body will be suppressed and will not be meshed, nor will it be sent to the solver if it is already meshed.
In the Details View, Used By Fluid Surface specifies whether the virtual body is being used by a group of fluid surfaces. The default is No. If the virtual body will be used by a group of fluid surfaces, insert a Fluid Surface object into the Tree by right-clicking on the Virtual Body object and selecting Insert > Fluid Surface from the context menu.
Alternatively, you can change the setting to Yes in the Details View, and a new Fluid Surface object will be inserted under the Virtual Body object.
Only one Fluid Surface object can be associated to any one Virtual Body object.
If you switch the value of Used By Fluid Surface from Yes to No, the Fluid Surface object will be hidden.
Click the Virtual Body object in the Tree to continue defining it. For Material Point, specify the coordinate system to be used for the virtual body, and the faces will be oriented accordingly. The default is Please Define.
The Fluid Surface object and Virtual Body object will remain underdefined until a material point is specified.
You can either select the default coordinate system or define a local coordinate system. In either case, the setting will be retained, even if the Used By Fluid Surface setting is changed later.
The remaining fields for the virtual body are read-only:
Fluid/Solid - Always set to Fluid for virtual bodies.
Nodes, Elements, Mesh Metric - Data associated with the virtual body when meshed.
If Used By Fluid Surface is No, the definition of the virtual body is now complete. If the virtual body will be used by a group of fluid surfaces (that is, Used By Fluid Surface is Yes), expand the Virtual Body object in the Tree Outline to expose the Fluid Surface object.
To define and make adjustments to the group of fluid surfaces, click the Fluid Surface object and use the following controls. These controls appear in the Details View of the Fluid Surface object.
Faces To Group: In the Geometry window, select the faces that should be members of the group. Refer to the example of the aero valve assembly below for information about automating face selection.
Master Virtual Body: Read-only name of the master virtual body.
Priority: Determines which group will claim cells in cases where groups overlap. The priority is initially based on the rule: the smaller the volume, the higher the priority.
Suppressed: Read-only setting that is inherited from the virtual body.
Remember the following information when defining virtual bodies:
Connections are not supported.
Statistics are supported.
When coordinate systems are created they are represented in the Tree as objects named Coordinate System, Coordinate System 2, Coordinate System 3, and so on.
Toggling the value of Used By Fluid Surface from Yes to No will result in the following behaviors:
If you switch from Yes to No, the Fluid Surface object will be hidden.
If you switch from No to Yes, the Fluid Surface object will be inserted into the Tree Outline, and the virtual body will become the master body.
If a group of fluid surfaces is being used to help define a virtual body, its suppression status is inherited from the virtual body and is read-only.
You should not use a group of fluid surfaces to help define a virtual body if one or more internal baffles (i.e., Surface Body with free edges) is located inside the flow volume void where you specified the material point. These baffles do not resolve properly in ANSYS Fluent.
For flow volume extraction, make sure that capping faces have been created in your CAD package. Capping faces must be selected manually when defining virtual bodies. See Using the Extend to Connection Option with Fluid Surface Grouping for an example.
Using one surface body to cap multiple inlets/outlets is not supported. Make sure that each opening is capped with at least one face.
The mesh around the edges of a capping surface must be properly resolved both by size and feature to ensure that no leakage occurs.
Contact sizing might be used to close gaps smaller than 1/4 of the minimum size. Note that contact sizing will not properly recover features around the gap, therefore you should exclude inflation in this area.
It is not recommended to use contact sizing to close a gap if faces in the connection are already included in the sharp angle control.
Contact sizing tools are not supported on baffle surfaces or capping surfaces.
If you create a fluid body using Boolean operations from solid volumes, but shared topology fails, the recommended action is to not use this geometry configuration in assembly meshing. Instead remove the fluid volumes and add a material point to extract the fluid volume inside meshing. Also see Handling of Interfaces Between Bodies in Assembly Meshing.
The Mesh cell state will go out-of-date and will require updating if:
You suppress/unsuppress a virtual body.
You delete a virtual body.
You change the location of the material point that you selected for a virtual body.
You select a different material point for a virtual body.
Named Selection names for internal face zones are not interpreted. In cases where two enclosed voids share a face, the face zone is assigned type WALL automatically regardless of whether a Named Selection has been defined for the face. In these cases, the mesh generation cannot cross any boundary so you must define a virtual body with material point for each flow volume void in order for the volumes to be meshed.
When an assembly mesh is exported to ANSYS Fluent, Virtual Body Group names and Virtual Body names are handled the same as part names and body names respectively. The zone naming rules that are applied to real part and body names are also applied to Virtual Body Group names and Virtual Body names. For example, part “part” and body “solid body” will result in a zone name of “part-solid_body.” Similarly, Virtual Body Group "virtual_body_group" and Virtual Body "virtual_body" will result in a zone name of "virtual_body_group-virtual_body." Refer to Fluent Mesh Export for details.
For fluids of different properties (for example, air, water, etc.), it is recommended that you create virtual bodies within different virtual body groups to make sure the fluid zones are separated inside ANSYS Fluent.
As described in Define Connections the Mechanical help, connections can be contact regions, joints, mesh connections, and so on. To aid in picking faces related to flow volumes, you can use the Extend to Connection option on the Extend Selection drop-down menu. Extend to Connection searches for faces that are adjacent to the current selection as well as all faces that are adjacent to each of the additional selections within the part, up to and including all connections on the selected part. For example, if you are using a group of fluid surfaces to help define a virtual body, you can generate connections, pick one face on each body of the flow volume, and then select Extend to Connection. As a result, the faces related to the flow volume are picked. See Using the Extend to Connection Option with Fluid Surface Grouping for an example.
The extent of the faces that will be included when Extend to Connection is used depends greatly on the current set of connections, as defined by the specified connections criteria (for example, Connection Type, Tolerance Value, and so on). By modifying the criteria and regenerating the connections, a different set of faces may be included. Refer to Common Connections Folder Operations for Auto Generated Connections in the Mechanical help for more information.
Extend to Connection is also helpful in cases where you want to scope a size function locally to the faces of a virtual body. For example, consider a case in which you want to assign a smaller size function curvature angle to a fluid region and you want to keep the solid mesh (Keep Solid Mesh is set to Yes). When Physics Preference is CFD, the default curvature angle of 18 degrees has been determined to be suitable for use in flow simulations. For solids, the angle can probably be as large as 30-40 degrees. Hence, by setting the global Curvature Normal Angle to 30 degrees and scoping a curvature normal angle of 18 degrees locally to the faces of the virtual body (after roughly picking the faces and using Extend to Connection to find adjacent faces), you can avoid unnecessary mesh refinement in the solid parts.
In cases where fluid extraction is successful in the DesignModeler application (or any other CAD package) but Shared Topology fails, and you plan to solve a conjugate heat transfer problem and hence keep the solid mesh, two problems may occur because you now have two boundaries all along the surface of the fluid domain:
The Shared Topology failure indicates that the fluid domain does not match the original boundaries very well, which may lead to bad quality cells.
Any Named Selection created on the solid bodies may be lost in cases where the corresponding fluid wall is present. Due to the conformal mesh that will be generated by assembly meshing, only one of the geometry faces in contact will get surface mesh elements associated to it. Alternatively, the Named Selection may be added to the fluid wall as well.
To avoid these problems, you can suppress the fluid volume and use material point-based extraction inside assembly meshing.
For the example shown below, in the case of a Shared Topology failure, you could:
Keep the Boolean subtraction operation but suppress the solid body and use a virtual body instead.
Remove the Boolean subtraction operation in the DesignModeler application or CAD package so that the solid overlaps the same volume as the fluid (the meshing will do the volume extraction).

Alternatively, if the solids/fluids only partially touch as in the case shown below, mesh at the interface between Body 1 and Body 2 may get associated to either Face A or Face B. If you need to define a Named Selection for Face B, it should include both Face A and Face B to ensure proper association.
Note: You must use a similar approach when applying inflation to shared faces between a solid body and a fluid body in cases involving multiple parts. That is, select both sets of overlapping faces when defining the local inflation control. See Applying Local (Scoped) Inflation Controls and Regenerating the Inflation Mesh for related information.

Because this approach may result in the Named Selection including the larger area (i.e., all of Face A), you may need to split out Face A with imprints to get the proper topology.
In cases where a solid spatially divides a fluid into multiple regions and you want to recover the mesh in only one region, you can use a virtual body and material point to define the region to be meshed.
For example, in Figure 186: Solid Bodies Dividing a Fluid Body, the image on the left shows a mesh group that consists of two solid bodies, and which divides a fluid body into multiple regions. The image on the right shows the corresponding mesh that is obtained using the CutCell algorithm.
Figure 187: Virtual Body Defined to Separate Fluid Region shows the same model, but in this case a virtual body and material point have been defined to further separate the fluid region. The image on the right shows the corresponding mesh that is obtained using the CutCell algorithm.
This example illustrates how you can use the Extend to Connection option and fluid surface grouping together to solve assembly meshing problems.
The first figure shows a model of an aero valve, for which a virtual body is being used to represent the flow volume. Notice the Material Point that is inside the virtual body.

Automatic connections were generated for the model and are highlighted in the figure below.

As described in the procedure above, to use a group of fluid surfaces to help define a virtual body, all of the faces that should be members of the group must be selected and assigned as the Faces To Group in the Details View. Using the face picker to select all of the faces manually in the Geometry window may be difficult. However, by using the Extend to Connection option, you need to select only one face on each body of the flow volume (that is, one face on each of the domains that will be “closed” by the connections). In the figure below, five faces have been picked.

After you select one face on each body of the flow volume, select the Extend to Connection option. In this example, the figure below shows the faces that are selected automatically after the Extend to Connection option is chosen. The option captures all faces that will “touch” the flow volume, except for any capping faces. The capping faces, such as the inlet face, must be picked manually. After all capping faces are picked, you can click the Faces To Group field in the Details View to apply your selection and then proceed with generating the mesh.

The figure below shows a view of the resulting mesh, with the inlet on the right.
