174 lines
12 KiB
Markdown
174 lines
12 KiB
Markdown
<!-- source-page: 741 -->
|
||
|
||
fluid flow occurs. Separate controls are provided for the contribution of fluid flow across the interface $( q _ { a c r o s s } )$ and the contribution of fluid flow into the interface $( q _ { g a p } )$ .
|
||
|
||
# Input File Usage:
|
||
|
||
Use the following option to specify a cutoff distance $( d _ { a c r o s s } )$ for the contribution of fluid flow across the contact interface $\left( q _ { a c r o s s } \right)$ :
|
||
|
||
$$
|
||
* \text { CONTACT PERMEABILITY, CUTOFF FLOW ACROSS } = d _ {a c r o s s}
|
||
$$
|
||
|
||
Use the following option to specify a cutoff distance $( d _ { g a p } )$ for the contribution of fluid flow into the contact interface $( q _ { g a p } )$ :
|
||
|
||
$$
|
||
* \text { CONTACT PERMEABILITY, CUTOFF GAP FILL } = d _ {g a p}
|
||
$$
|
||
|
||
# Controlling contact permeability associated with fluid flow across a contact interface
|
||
|
||
If you do not specify contact permeability characteristics, the default model ensures continuity of the pore pressures on opposite sides of a contact interface while the contact separation is less than the threshold distance discussed in “Controlling the distance within which pore fluid contact properties are active”:
|
||
|
||
$$
|
||
p _ {A} - p _ {B} = 0,
|
||
$$
|
||
|
||
where $p _ { A }$ and $p _ { B }$ are pore pressures at points on opposite sides of the interface. This relationship implies that contact permeability across the interface is infinite.
|
||
|
||
Alternatively, you can specify a contact permeability, k, such that fluid flow across a contact interface $( q _ { a c r o s s }$ , discussed above in “Including pore fluid properties in a contact property definition”) is proportional to the difference in pore pressure magnitudes across the interface:
|
||
|
||
$$
|
||
q _ {a c r o s s} = k (p _ {A} - p _ {B}).
|
||
$$
|
||
|
||
When defining k directly, define it as
|
||
|
||
$$
|
||
k = k (p _ {c o n t a c t}, \bar {p} _ {p o r e}, \bar {\theta}, \bar {f} _ {\gamma}),
|
||
$$
|
||
|
||
where
|
||
|
||
Pcontact
|
||
|
||
is the contact pressure transmitted across the interface between A and B,
|
||
|
||
$$
|
||
\bar {p} _ {p o r e} = \frac {1}{2} (p _ {p o r e A} + p _ {p o r e B})
|
||
$$
|
||
|
||
$$
|
||
\bar {\theta} = \frac {1}{2} (\theta_ {A} + \theta_ {B})
|
||
$$
|
||
|
||
$$
|
||
\bar {f} _ {\gamma} = \frac {1}{2} \left(f _ {\gamma} ^ {A} + f _ {\gamma} ^ {B}\right)
|
||
$$
|
||
|
||
is the average of the pore pressures at A and B,
|
||
|
||
is the average of the surface temperatures at A and B, and
|
||
|
||
is the average of any predefined field variables at A and B.
|
||
|
||
Figure 37.4.1–2 shows an example of k depending on the contact pressure. Use tabular data to specify the value of k at one or more contact pressures as p increases. The value of k remains constant for contact pressures outside of the interval defined by the data points. Once the surfaces have separated, k remains at a constant value until the separation between the surfaces exceeds the specified flow cutoff distance (see “Controlling the distance within which pore fluid contact properties are active”), at which point k drops to zero.
|
||
|
||
<!-- source-page: 742 -->
|
||
|
||

|
||
Figure 37.4.1–2 Contact-pressure-dependent contact permeability.
|
||
|
||
Input File Usage: \*CONTACT PERMEABILITY $k , p _ { c o n t a c t } , \bar { p } _ { p o r e } , \bar { \theta }$
|
||
|
||
# Defining gap permeability to be a function of predefined field variables
|
||
|
||
In addition to the dependencies mentioned previously, the gap permeability can be dependent on any number of predefined field variables, $\bar { f } _ { \gamma }$ . To make the gap permeability depend on field variables, at least two data points are required for each field variable value.
|
||
|
||
Input File Usage: $\begin{array} { r l } { { } } & { { \ast \mathrm { C O N T A C T ~ P E R M E A B I L I T Y , D E P E N D E N C I E S } = n } } \\ { { } } & { { k , ~ p _ { c o n t a c t } , ~ \bar { p } _ { p o r e } , ~ \bar { \theta } , ~ \bar { f } _ { \gamma } } } \end{array}$
|
||
|
||
# Coupled heat transfer–pore fluid contact properties
|
||
|
||
Heat transfer can be considered simultaneously with pore fluid flow, in which case heat flow across the contact interface can occur in conjunction with fluid flow. These various contact property aspects are defined with separate options as part of a single contact property definition that you assign to the contact interaction; see “Thermal contact properties,” Section 37.2.1, for details on defining heat transfer properties.
|
||
|
||
# Output
|
||
|
||
You can write the contact surface variables associated with the interaction of contact pairs to the Abaqus/Standard data (.dat), results (.fil), and output database (.odb) files. In addition to the surface variables associated with the mechanical contact analysis (shear stresses, contact pressures, etc.) several pore fluid-related variables (such as pore fluid volume flux per unit area) on the contact interface can be reported. A detailed discussion of these output requests can be found in “Surface output
|
||
|
||
<!-- source-page: 743 -->
|
||
|
||
from Abaqus/Standard” in “Output to the data and results files,” Section 4.1.2, and “Surface output in Abaqus/Standard and Abaqus/Explicit” in “Output to the output database,” Section 4.1.3.
|
||
|
||
Abaqus/Standard provides the following output variables related to the pore fluid interaction of surfaces:
|
||
|
||
<table><tr><td>PFL</td><td>Pore volume flux per unit area leaving the slave surface.</td></tr><tr><td>PFLA</td><td>PFL multiplied by the area associated with the slave node.</td></tr><tr><td>PTL</td><td>Time integrated PFL.</td></tr><tr><td>PTLA</td><td>Time integrated PFLA.</td></tr><tr><td>TPFL</td><td>Total pore volume flux leaving the slave surface.</td></tr><tr><td>TPTL</td><td>Time integrated TPFL.</td></tr></table>
|
||
|
||
<!-- source-page: 744 -->
|
||
|
||
<!-- source-page: 745 -->
|
||
|
||
# 38. Contact Formulations and Numerical Methods
|
||
|
||
Contact formulations and numerical methods in Abaqus/Standard 38.1
|
||
|
||
Contact formulations and numerical methods in Abaqus/Explicit 38.2
|
||
|
||
<!-- source-page: 746 -->
|
||
|
||
<!-- source-page: 747 -->
|
||
|
||
# 38.1 Contact formulations and numerical methods in Abaqus/Standard
|
||
|
||
• “Contact formulations in Abaqus/Standard,” Section 38.1.1
|
||
• “Contact constraint enforcement methods in Abaqus/Standard,” Section 38.1.2
|
||
• “Smoothing contact surfaces in Abaqus/Standard,” Section 38.1.3
|
||
|
||
<!-- source-page: 748 -->
|
||
|
||
<!-- source-page: 749 -->
|
||
|
||
# 38.1.1 CONTACT FORMULATIONS IN Abaqus/Standard
|
||
|
||
Products: Abaqus/Standard Abaqus/CAE
|
||
|
||
# References
|
||
|
||
• “Surfaces: overview,” Section 2.3.1
|
||
• “Defining general contact interactions in Abaqus/Standard,” Section 36.2.1
|
||
• “Defining contact pairs in Abaqus/Standard,” Section 36.3.1
|
||
• \*CONTACT
|
||
• \*CONTACT PAIR
|
||
• “Defining general contact,” Section 15.13.1 of the Abaqus/CAE User’s Guide, in the HTML version of this guide
|
||
• “Defining surface-to-surface contact,” Section 15.13.7 of the Abaqus/CAE User’s Guide, in the HTML version of this guide
|
||
• “Defining self-contact,” Section 15.13.8 of the Abaqus/CAE User’s Guide, in the HTML version of this guide
|
||
• “Using contact and constraint detection,” Section 15.16 of the Abaqus/CAE User’s Guide, in the HTML version of this guide
|
||
|
||
# Overview
|
||
|
||
Abaqus/Standard provides several contact fomulations. Each formulation is based on a choice of a contact discretization, a tracking approach, and assignment of “master” and “slave” roles to the contact surfaces. For general contact interactions, the discretization, tracking approach, and surface role assignments are selected automatically by Abaqus/Standard; for contact pairs, you can specify these aspects of the contact formulation using the interface described in “Defining contact pairs in Abaqus/Standard,” Section 36.3.1. The default contact formulation is applicable in most situations, but you may find it desirable to choose another formulation in some cases. This section discusses in detail the formulations that Abaqus/Standard uses in contact simulations.
|
||
|
||
Your choice of a tracking approach will have a considerable impact on how contact surfaces interact. In Abaqus/Standard there are two tracking approaches to account for the relative motion of two interacting surfaces in mechanical contact simulations:
|
||
|
||
• finite sliding, which is the most general and allows any arbitrary motion of the surfaces (see “Finitesliding interaction between deformable bodies,” Section 5.1.2 of the Abaqus Theory Guide, and “Finite-sliding interaction between a deformable and a rigid body,” Section 5.1.3 of the Abaqus Theory Guide); and
|
||
|
||
• small sliding, which assumes that although two bodies may undergo large motions, there will be relatively little sliding of one surface along the other (see “Small-sliding interaction between bodies,” Section 5.1.1 of the Abaqus Theory Guide).
|
||
|
||
<!-- source-page: 750 -->
|
||
|
||
You can choose between node-to-surface contact discretization and true surface-to-surface contact discretization for each of the above tracking approaches.
|
||
|
||
# Formulations for general contact
|
||
|
||
General contact in Abaqus/Standard always uses the finite-sliding, surface-to-surface contact formulation. This formulation can also be used for contact pairs, but it is not the default. The discussions in this section of finite-sliding, surface-to-surface contact apply equally to general contact and to contact pairs.
|
||
|
||
In a general contact domain the master and slave roles are assigned to surfaces automatically, although it is possible to override these default assignments. The behavior of master surfaces and slave surfaces is consistent across general contact and contact pair interactions. The specification of master and slave surfaces in a general contact domain is covered in detail in “Numerical controls for general contact in Abaqus/Standard,” Section 36.2.6.
|
||
|
||
# Discretization of contact pair surfaces
|
||
|
||
Abaqus/Standard applies conditional constraints at various locations on interacting surfaces to simulate contact conditions. The locations and conditions of these constraints depend on the contact discretization used in the overall contact formulation. Abaqus/Standard offers two contact discretization options: a traditional “node-to-surface” discretization and a true “surface-to-surface” discretization.
|
||
|
||
# Node-to-surface contact discretization
|
||
|
||
With traditional node-to-surface discretization the contact conditions are established such that each “slave” node on one side of a contact interface effectively interacts with a point of projection on the “master” surface on the opposite side of the contact interface (see Figure 38.1.1–1). Thus, each contact condition involves a single slave node and a group of nearby master nodes from which values are interpolated to the projection point.
|
||
|
||
Traditional node-to-surface discretization has the following characteristics:
|
||
|
||
• The slave nodes are constrained not to penetrate into the master surface; however, the nodes of the master surface can, in principle, penetrate into the slave surface (for example, see the case on the upper-right of Figure 38.1.1–2).
|
||
• The contact direction is based on the normal of the master surface.
|
||
• The only information needed for the slave surface is the location and surface area associated with each node; the direction of the slave surface normal and slave surface curvature are not relevant. Thus, the slave surface can be defined as a group of nodes—a node-based surface.
|
||
• Node-to-surface discretization is available even if a node-based surface is not used in a contact pair definition.
|
||
|
||
# Surface-to-surface contact discretization
|
||
|
||
Surface-to-surface discretization considers the shape of both the slave and master surfaces in the region of contact constraints. Surface-to-surface discretization has the following key characteristics:
|