Logo

Applications for Users

  • 1. OpenSees Interpreters
  • 2. Installation
  • 3. Command Manual
    • 3.1. Model Commands
      • 3.1.1. model Command
      • 3.1.2. node Command
      • 3.1.3. SP_Constraint Commands
      • 3.1.4. MP_Constraint Commands
      • 3.1.5. uniaxialMaterial Command
      • 3.1.6. nDMaterial Command
      • 3.1.7. section Command
      • 3.1.8. Geometric Transformation Command
      • 3.1.9. Beam Integration Command
      • 3.1.10. Element Command
        • 3.1.10.1. ZeroLength Element
        • 3.1.10.2. ZeroLength Section Element
        • 3.1.10.3. ZeroLengthND Element
        • 3.1.10.4. CoupledZeroLength Element
        • 3.1.10.5. zeroLengthContact Element
        • 3.1.10.6. zeroLengthContactNTS2D Element
        • 3.1.10.7. zeroLengthInterface2D Element
        • 3.1.10.8. zeroLengthImpact3D Element
        • 3.1.10.9. ZeroLengthContactASDimplex Element
        • 3.1.10.10. Truss Element
        • 3.1.10.11. Corotational Truss Element
        • 3.1.10.12. Elastic Beam Column Element
        • 3.1.10.13. Displacement-Based Beam Column Element
        • 3.1.10.14. Force-Based Beam Column Element
        • 3.1.10.15. Modified Elastic Beam Column Element
        • 3.1.10.16. Gradient Inelastic (GI) Beam-Column Element
        • 3.1.10.17. MVLEM_3D Element
        • 3.1.10.18. SFI-MVLEM-3D Element
        • 3.1.10.19. E-SFI-MVLEM-3D Element
        • 3.1.10.20. Displacement-Based Beam Element (Asymmetric Sections)
        • 3.1.10.21. Mixed Beam Element (Asymmetric Sections)
        • 3.1.10.22. E-SFI Element
        • 3.1.10.23. ASDShellQ4 Element
        • 3.1.10.24. Quadrilateral Element
        • 3.1.10.25. SSPquad Element
        • 3.1.10.26. MEFI Element
        • 3.1.10.27. ASDShellT3 Element
        • 3.1.10.28. stdBrick Element
        • 3.1.10.29. bbarBrick Element
        • 3.1.10.30. SSPbrick Element
        • 3.1.10.31. FourNodeTetrahedron Element
        • 3.1.10.32. TenNodeTetrahedron Element
        • 3.1.10.33. BeamColumnJoint Element
        • 3.1.10.34. ElasticTubularJoint Element
        • 3.1.10.35. Joint2D Element
        • 3.1.10.36. Inno3DPnPJoint Element
        • 3.1.10.37. LehighJoint2D Element
        • 3.1.10.38. Two Node Link Element
        • 3.1.10.39. TripleFrictionPendulumX Element
        • 3.1.10.8. zeroLengthImpact3D Element
        • 3.1.10.40. PML Element
        • 3.1.10.41. ASDEmbeddedNode Element
        • 3.1.10.42. ASDAbsorbingBoundary Element (2D and 3D)
        • 3.1.10.43. RockingBC Element
        • 3.1.10.44. FSIFluidBoundaryElement2D Element
        • 3.1.10.45. FSIFluidElement2D Element
        • 3.1.10.46. FSIInterfaceElement2D Element
      • 3.1.11. Time Series Command
      • 3.1.12. Pattern Command
      • 3.1.13. Damping Commands
    • 3.2. Analysis Commands
    • 3.3. Output Commands
    • 3.4. Misc. Commands
  • 4. Examples
  • 5. Questions, Bugs & Feature Requests
  • 6. Copyright and License

Framework for Developer

  • 1. Source Code
  • 2. Building Application
  • 3. References
  • 4. Extending Application
  • 5. Contributing Code & Documentation
  • 6. Issues
OpenSees Documentation
  • 3. Command Manual
  • 3.1. Model Commands
  • 3.1.10. Element Command
  • 3.1.10.38. Two Node Link Element
  • View page source

3.1.10.38. Two Node Link Element

This command is used to construct a twoNodeLink element object, which is defined by two nodes. The element can have zero or non-zero length. It can have 1 to 6 degrees of freedom; only the transverse and rotational DOFs are coupled when the element has non-zero length. For non-zero length you can optionally specify how P-Delta moments (around local x and y) are distributed among moment at node i, moment at node j, and shear couple (the three ratios sum to 1), and the shear center as a fraction of the element length from node i. The element does not contribute to Rayleigh damping by default. For non-zero length the local x-axis is from nodal geometry unless -orient is given; for zero length the geometry is ignored and orientation vectors define the spring directions.

element twoNodeLink $eleTag $iNode $jNode -mat $matTags -dir $dirs <-orient $x1 $x2 $x3 $y1 $y2 $y3> <-pDelta $Mratios> <-shearDist $sDratios> <-doRayleigh> <-mass $m>

Note

If the element has zero length and orientation vectors are not specified, the local axes coincide with the global axes. Otherwise the local z-axis is the cross product of the x- and y-vectors.

The valid queries when creating an ElementRecorder are ‘force,’ ‘localForce,’ ‘basicForce,’ ‘localDisplacement,’ ‘basicDisplacement’ and ‘material $matNum matArg1 matArg2 …’.

Relationship to zeroLength

The twoNodeLink can be thought of as a zeroLength element with length. Unlike zeroLength, the local x-axis for non-zero length is taken from the vector between the two nodes, so you do not need to specify orientation unless you want to override it. The element is often used for dampers but also applies to other uncoupled force-deformation responses. When both translational and rotational springs are used, the shear distance (-shearDist) is the center of rotation as a fraction of the element length; it couples the moment-rotation response to lateral displacement. For zeroLength, lateral displacement depends only on the translational spring; for twoNodeLink it also depends on the rotational spring and the shear distance (default 0.5). With section-based response (e.g. fiber sections), twoNodeLink can model coupled axial, shear, and flexural behavior efficiently.

See also

Notes (OpenSees wiki)

Two Node Link’s Awakening (Portwood Digital) for more on comparison with zeroLength and flexural response.

Example

From the OpenSees wiki: 2D link with tag 1 between nodes 1 and 2, materials 1, 2, 3 in directions 1, 2, 3. 3D link with tag 1, materials in directions 1, 2, 6.

  1. Tcl Code

# 2D
element twoNodeLink 1 1 2 -mat 1 2 3 -dir 1 2 3

# 3D
element twoNodeLink 1 1 2 -mat 1 2 3 -dir 1 2 6
  1. Python Code

# 2D
ops.element('twoNodeLink', 1, 1, 2, '-mat', 1, 2, 3, '-dir', 1, 2, 3)

# 3D
ops.element('twoNodeLink', 1, 1, 2, '-mat', 1, 2, 3, '-dir', 1, 2, 6)

Code developed by: Andreas Schellenberg


© Copyright 2022, The Regents of the University of California.

Built with Sphinx using a theme provided by Read the Docs.