BeamContact2D

From OpenSeesWiki
Revision as of 17:09, 13 June 2020 by Mhscott (talk | contribs) (Change terminology to retained/constrained)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search




This command is used to construct a BeamContact2D element object.

element BeamContact2D $eleTag $iNode $jNode $cNode $lNode $matTag $width $gTol $fTol <$cFlag$>


$eleTag unique integer tag identifying element object
$iNode $jNode retained nodes (-ndm 2 -ndf 3)
$cNode constrained node (-ndm 2 -ndf 2)
$lNode Lagrange multiplier node (-ndm 2 -ndf 2)
$matTag unique integer tag associated with previously-defined nDMaterial object
$width the width of the wall represented by the beam element in plane strain
$gTol gap tolerance
$fTol force tolerance
$cFlag optional initial contact flag
$cFlag = 0 >> contact between bodies is initially assumed (DEFAULT)
$cFlag = 1 >> no contact between bodies is initially assumed




The BeamContact2D element is a two-dimensional beam-to-node contact element which defines a frictional contact interface between a beam element and a separate body. The retained nodes (3 DOF) are the endpoints of the beam element, and the constrained node (2 DOF) is a node from a second body. The Lagrange multiplier node (2 DOF) is required to enforce the contact condition. Each contact element should have a unique Lagrange multiplier node. The Lagrange multiplier node should not be fixed, otherwise the contact condition will not work.

Under plane strain conditions in 2D, a beam element represents a unit thickness of a wall. The width is the dimension of this wall in the 2D plane. This width should be built-in to the model to ensure proper enforcement of the contact condition. The Excavation Supported by Cantilevered Sheet Pile Wall practical example provides some further examples and discussion on the usage of this element.


NOTE:

  1. The BeamContact2D element has been written to work exclusively with the ContactMaterial2D nDMaterial object.
  2. The valid recorder queries for this element are:
    1. force - returns the contact force acting on the constrained node in vector form.
    2. frictionforce - returns the frictional force acting on the constrained node in vector form.
    3. forcescalar - returns the scalar magnitudes of the normal and tangential contact forces.
    4. masterforce - returns the reactions (forces and moments) acting on the retained nodes.
    5. The BeamContact2D elements are set to consider frictional behavior as a default, but the frictional state of the BeamContact2D element can be changed from the input file using the setParameter command. When updating, value of 0 corresponds to the frictionless condition, and a value of 1 signifies the inclusion of friction. An example command for this update procedure is provided below
  3. The BeamContact2D element works well in static and pseudo-static analysis situations.
  4. In transient analysis, the presence of the contact constraints can effect the stability of commonly-used time integration methods in the HHT or Newmark family (e.g., Laursen, 2002). For this reason, use of alternative time-integration methods which numerically damp spurious high frequency behavior may be required. The TRBDF2 integrator is an effective method for this purpose. The Newmark integrator can also be effective with proper selection of the gamma and beta coefficients. The trapezoidal rule, i.e., Newmark with gamma = 0.5 and beta = 0.25, is particularly prone to instability related to the contact constraints and is not recommended.


EXAMPLES:

BeamContact2D element with tag 1, connectivity with nodes 1, 2, 3, and 4, material with tag 1, width 0.5, gap and force tolerances of 1.0e-10, and a contact flag set to assume initial contact.

element BeamContact2D 1  1 2 3 4  1  0.5 1.0e-10 1.0e-10 0

Update all of the BeamContact2D elements with tags between 10 and 20 to consider a frictionless interface

setParameter -value 0 -eleRange 10 20 friction


REFERENCES:

Laursen, T. A. (2002). Computational Contact and Impact Mechanics. Springer-Verlag, Berlin.


Code Developed by: Chris McGann, Pedro Arduino, & Peter Mackenzie-Helnwein, at the University of Washington