0% found this document useful (0 votes)
99 views66 pages

Nonlinear Modeling of RC Structures Using Opensees: University of Naples Federico Ii

This document provides information about linear modeling in OpenSees, including an overview of the different types of objects needed to build a complete OpenSees model. It discusses modeling objects like materials, sections, and elements, as well as analysis, output, and transformation objects. The document also provides examples of commands to construct specific material models, like elastic, elastic-plastic, and concrete materials.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
99 views66 pages

Nonlinear Modeling of RC Structures Using Opensees: University of Naples Federico Ii

This document provides information about linear modeling in OpenSees, including an overview of the different types of objects needed to build a complete OpenSees model. It discusses modeling objects like materials, sections, and elements, as well as analysis, output, and transformation objects. The document also provides examples of commands to construct specific material models, like elastic, elastic-plastic, and concrete materials.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 66

University of Naples Federico II

Department of Structures for Engineering and Architecture


PhD program in Structural Engineering Geotechnics and Seismic Risk

Nonlinear modeling of RC structures using OpenSees


prof. P. Ricci
dr. M. Di Domenico

Lecture 2
Linear modeling
part 1 - theory

June 7th-8th, 2021


Tcl language
To run a structural analysis in OpenSees, different types of objects shall be constructed by means of appropriate commands.
An aggregation of different types of objects constitutes a domain.

COMPLETE OPENSEES MODEL


Tcl language
To run a structural analysis in OpenSees, different types of objects shall be constructed by means of appropriate commands.
An aggregation of different types of objects constitutes a domain.

COMPLETE OPENSEES MODEL

MODELING OBJECTS/DOMAIN ANALYSIS OBJECTS OUTPUT OBJECTS


Tcl language
To run a structural analysis in OpenSees, different types of objects shall be constructed by means of appropriate commands.
An aggregation of different types of objects constitutes a domain.

COMPLETE OPENSEES MODEL

MODELING OBJECTS/DOMAIN ANALYSIS OBJECTS OUTPUT OBJECTS

▪ model
▪ node
▪ mass
▪ SP_constraint
▪ MP_constraint
▪ uniaxialMaterial
▪ section
▪ element
▪ timeSeries
▪ pattern
▪ … and others
Tcl language
To run a structural analysis in OpenSees, different types of objects shall be constructed by means of appropriate commands.
An aggregation of different types of objects constitutes a domain.

COMPLETE OPENSEES MODEL

MODELING OBJECTS/DOMAIN ANALYSIS OBJECTS OUTPUT OBJECTS

▪ model ▪ constraints
▪ node ▪ numberer
▪ mass ▪ system
▪ SP_constraint ▪ test
▪ MP_constraint ▪ algorithm
▪ uniaxialMaterial ▪ integrator
▪ section ▪ analysis
▪ element ▪ eigen
▪ timeSeries ▪ analyze
▪ pattern ▪ … and others
▪ … and others
Tcl language
To run a structural analysis in OpenSees, different types of objects shall be constructed by means of appropriate commands.
An aggregation of different types of objects constitutes a domain.

COMPLETE OPENSEES MODEL

MODELING OBJECTS/DOMAIN ANALYSIS OBJECTS OUTPUT OBJECTS

▪ model ▪ constraints ▪ recorder


▪ node ▪ numberer ▪ print
▪ mass ▪ system ▪ logFile
▪ SP_constraint ▪ test ▪ … and others
▪ MP_constraint ▪ algorithm
▪ uniaxialMaterial ▪ integrator
▪ section ▪ analysis
▪ element ▪ eigen
▪ timeSeries ▪ analyze
▪ pattern ▪ … and others
▪ … and others
Tcl language
To run a structural analysis in OpenSees, different types of objects shall be constructed by means of appropriate commands.
An aggregation of different types of objects constitutes a domain.

COMPLETE OPENSEES MODEL

MODELING OBJECTS/DOMAIN ANALYSIS OBJECTS OUTPUT OBJECTS

▪ model ▪ constraints ▪ recorder


▪ node ▪ numberer ▪ print
▪ mass ▪ system ▪ logFile
▪ SP_constraint ▪ test ▪ … and others
▪ MP_constraint ▪ algorithm
▪ uniaxialMaterial ▪ integrator
▪ section ▪ analysis
▪ element ▪ eigen
▪ timeSeries ▪ analyze
▪ pattern ▪ … and others
▪ … and others
Materials
MODELING COMMANDS

uniaxialMaterial Elastic command

This command is used to construct an elastic uniaxial material object.

uniaxialMaterial Elastic $matTag $E <$eta> <$Eneg>


$matTag integer tag identifying material
$E tangent
$eta damping tangent (optional, default=0.0)
$Eneg tangent in compression (optional, default=E)

example:
uniaxialMaterial Elastic 1 25000 elastic material 1 with stiffness equal to 25000
MODELING COMMANDS

uniaxialMaterial ElasticPP command

This command is used to construct an elastic perfectly-plastic uniaxial material object.

uniaxialMaterial ElasticPP $matTag $E $epsyP <$epsyN $eps0>


$matTag integer tag identifying material
$E tangent
$epsyP strain or deformation at which material reaches plastic state in tension
$epsyN strain or deformation at which material reaches plastic state in compression.
(optional, default is tension value)
$eps0 initial strain (optional, default: zero)

example:
uniaxialMaterial ElasticPP 1 25000 0.008 elastic-plastic material 1 with stiffness equal to 25000 and yielding at generalized deformation equal to 0.008
MODELING COMMANDS

uniaxialMaterial Concrete01 command

This command is used to construct a uniaxial Kent-Scott-Park concrete material object with no tensile strength.

uniaxialMaterial Concrete01 $matTag $fpc $epsc0 $fpcu $epsU


$matTag integer tag identifying material
$fpc concrete compressive strength at 28 days (compression is negative)
$epsc0 concrete strain at maximum strength
$fpcu concrete crushing strength
$epsU concrete strain at crushing strength
MODELING COMMANDS

uniaxialMaterial Concrete01 command

This command is used to construct a uniaxial Kent-Scott-Park concrete material object with no tensile strength.

uniaxialMaterial Concrete01 $matTag $fpc $epsc0 $fpcu $epsU


$matTag integer tag identifying material
$fpc concrete compressive strength at 28 days (compression is negative)
$epsc0 concrete strain at maximum strength
$fpcu concrete crushing strength
$epsU concrete strain at crushing strength
MODELING COMMANDS

uniaxialMaterial Concrete01 command

This command is used to construct a uniaxial Kent-Scott-Park concrete material object with no tensile strength.

uniaxialMaterial Concrete01 $matTag $fpc $epsc0 $fpcu $epsU


$matTag integer tag identifying material
$fpc maximum stress/force/moment
$epsc0 strain/displacement/rotation at maximum stress/force/moment
$fpcu ultimate stress/force/moment
$epsU strain/displacement/rotation at ultimate

•Compressive parameters should be input as negative values (if input as positive, they will be converted to negative internally).
•The initial slope for this model is (2*$fpc/$epsc0)
MODELING COMMANDS

uniaxialMaterial Concrete01 command

This command is used to construct a uniaxial Kent-Scott-Park concrete material object with no tensile strength.

uniaxialMaterial Concrete01 $matTag $fpc $epsc0 $fpcu $epsU


$matTag integer tag identifying material
$fpc maximum stress/force/moment
$epsc0 strain/displacement/rotation at maximum stress/force/moment
$fpcu ultimate stress/force/moment
$epsU strain/displacement/rotation at ultimate

•Compressive parameters should be input as negative values (if input as positive, they will be converted to negative internally).
•The initial slope for this model is (2*$fpc/$epsc0)

example:
uniaxialMaterial Concrete01 1 -200 -0.016 0 -0.032 no-tension material 1 with strength equal to 200, strain at maximum equal to 0.016, no
residual force at strain equal to 0.032
Sections and elements
Global and local axes
Global and local axes
MODELING COMMANDS

Linear Transformation command


This command is used to construct a linear coordinate transformation (LinearCrdTransf) object, which performs a linear
geometric transformation of beam stiffness and resisting force from the basic system to the global-coordinate system.

geomTransf Linear $transfTag $vecxzX $vecxzY $vecxzZ <-jntOffset $dXi $dYi $dZi $dXj $dYj $dZj>
$transfTag integer tag identifying transformation
X, Y, and Z components of vecxz, the vector used to define the local x-z plane of the local-coordinate system. The local y-axis is defined by taking the
cross product of the vecxz vector and the x-axis.
$vecxzX $vecxzY $vecxzZ These components are specified in the global-coordinate system X,Y,Z and define a vector that is in a plane parallel to the x-z plane of the local-
coordinate system.
These items need to be specified for the three-dimensional problem.
joint offset values -- offsets specified with respect to the global coordinate system for element-end node i (the number of arguments depends on the
$dXi $dYi $dZi
dimensions of the current model). The offset vector is oriented from node i to node j as shown in a figure below. (optional)
joint offset values -- offsets specified with respect to the global coordinate system for element-end node j (the number of arguments depends on the
$dXj $dYj $dZj
dimensions of the current model). The offset vector is oriented from node j to node i as shown in a figure below. (optional)
MODELING COMMANDS

Linear Transformation command


This command is used to construct a linear coordinate transformation (LinearCrdTransf) object, which performs a linear
geometric transformation of beam stiffness and resisting force from the basic system to the global-coordinate system.

geomTransf Linear $transfTag $vecxzX $vecxzY $vecxzZ <-jntOffset $dXi $dYi $dZi $dXj $dYj $dZj>
$transfTag integer tag identifying transformation
X, Y, and Z components of vecxz, the vector used to define the local x-z plane of the local-coordinate system. The local y-axis is defined by taking the
cross product of the vecxz vector and the x-axis.
$vecxzX $vecxzY $vecxzZ These components are specified in the global-coordinate system X,Y,Z and define a vector that is in a plane parallel to the x-z plane of the local-
coordinate system.
These items need to be specified for the three-dimensional problem.

example:
MODELING COMMANDS

Linear Transformation command


This command is used to construct a linear coordinate transformation (LinearCrdTransf) object, which performs a linear
geometric transformation of beam stiffness and resisting force from the basic system to the global-coordinate system.

geomTransf Linear $transfTag $vecxzX $vecxzY $vecxzZ <-jntOffset $dXi $dYi $dZi $dXj $dYj $dZj>
$transfTag integer tag identifying transformation
X, Y, and Z components of vecxz, the vector used to define the local x-z plane of the local-coordinate system. The local y-axis is defined by taking the
cross product of the vecxz vector and the x-axis.
$vecxzX $vecxzY $vecxzZ These components are specified in the global-coordinate system X,Y,Z and define a vector that is in a plane parallel to the x-z plane of the local-
coordinate system.
These items need to be specified for the three-dimensional problem.

example:
MODELING COMMANDS

Linear Transformation command


This command is used to construct a linear coordinate transformation (LinearCrdTransf) object, which performs a linear
geometric transformation of beam stiffness and resisting force from the basic system to the global-coordinate system.

geomTransf Linear $transfTag $vecxzX $vecxzY $vecxzZ <-jntOffset $dXi $dYi $dZi $dXj $dYj $dZj>
$transfTag integer tag identifying transformation
X, Y, and Z components of vecxz, the vector used to define the local x-z plane of the local-coordinate system. The local y-axis is defined by taking the
cross product of the vecxz vector and the x-axis.
$vecxzX $vecxzY $vecxzZ These components are specified in the global-coordinate system X,Y,Z and define a vector that is in a plane parallel to the x-z plane of the local-
coordinate system.
These items need to be specified for the three-dimensional problem.

example:

geomTransf Linear 1 0 0 -1
MODELING COMMANDS

Linear Transformation command


This command is used to construct a linear coordinate transformation (LinearCrdTransf) object, which performs a linear
geometric transformation of beam stiffness and resisting force from the basic system to the global-coordinate system.

geomTransf Linear $transfTag $vecxzX $vecxzY $vecxzZ <-jntOffset $dXi $dYi $dZi $dXj $dYj $dZj>
$transfTag integer tag identifying transformation
X, Y, and Z components of vecxz, the vector used to define the local x-z plane of the local-coordinate system. The local y-axis is defined by taking the
cross product of the vecxz vector and the x-axis.
$vecxzX $vecxzY $vecxzZ These components are specified in the global-coordinate system X,Y,Z and define a vector that is in a plane parallel to the x-z plane of the local-
coordinate system.
These items need to be specified for the three-dimensional problem.

example:

components of z local axis

geomTransf Linear 1 0 0 -1
MODELING COMMANDS

Linear Transformation command


This command is used to construct a linear coordinate transformation (LinearCrdTransf) object, which performs a linear
geometric transformation of beam stiffness and resisting force from the basic system to the global-coordinate system.

geomTransf Linear $transfTag $vecxzX $vecxzY $vecxzZ <-jntOffset $dXi $dYi $dZi $dXj $dYj $dZj>
$transfTag integer tag identifying transformation
X, Y, and Z components of vecxz, the vector used to define the local x-z plane of the local-coordinate system. The local y-axis is defined by taking the
cross product of the vecxz vector and the x-axis.
$vecxzX $vecxzY $vecxzZ These components are specified in the global-coordinate system X,Y,Z and define a vector that is in a plane parallel to the x-z plane of the local-
coordinate system.
These items need to be specified for the three-dimensional problem.

example:

components of z local axis

geomTransf Linear 2 0 1 0
MODELING COMMANDS

Linear Transformation command


This command is used to construct a linear coordinate transformation (LinearCrdTransf) object, which performs a linear
geometric transformation of beam stiffness and resisting force from the basic system to the global-coordinate system.

geomTransf Linear $transfTag $vecxzX $vecxzY $vecxzZ <-jntOffset $dXi $dYi $dZi $dXj $dYj $dZj>
joint offset values -- offsets specified with respect to the global coordinate system for element-end node i (the number of arguments depends on the
$dXi $dYi $dZi
dimensions of the current model). The offset vector is oriented from node i to node j as shown in a figure below. (optional)
joint offset values -- offsets specified with respect to the global coordinate system for element-end node j (the number of arguments depends on the
$dXj $dYj $dZj
dimensions of the current model). The offset vector is oriented from node j to node i as shown in a figure below. (optional)

example:

Beam with rigid end offsets

geomTransf Linear 2 0 1 0 -jntOffset 0.1 0 0 0.1 0 0


MODELING COMMANDS

PDelta Transformation command


This command is used to construct the P-Delta Coordinate Transformation (PDeltaCrdTransf) object, which performs a linear
geometric transformation of beam stiffness and resisting force from the basic system to the global coordinate system,
considering second-order P-Delta effects.
geomTransf PDelta $transfTag $vecxzX $vecxzY $vecxzZ <-jntOffset $dXi $dYi $dZi $dXj $dYj $dZj>
$transfTag integer tag identifying transformation
X, Y, and Z components of vecxz, the vector used to define the local x-z plane of the local-coordinate system. The local y-axis is defined by taking the
cross product of the vecxz vector and the x-axis.
$vecxzX $vecxzY $vecxzZ These components are specified in the global-coordinate system X,Y,Z and define a vector that is in a plane parallel to the x-z plane of the local-
coordinate system.
These items need to be specified for the three-dimensional problem.
joint offset values -- offsets specified with respect to the global coordinate system for element-end node i (the number of arguments depends on the
$dXi $dYi $dZi
dimensions of the current model). The offset vector is oriented from node i to node j as shown in a figure below. (optional)
joint offset values -- offsets specified with respect to the global coordinate system for element-end node j (the number of arguments depends on the
$dXj $dYj $dZj
dimensions of the current model). The offset vector is oriented from node j to node i as shown in a figure below. (optional)
MODELING COMMANDS

Elastic Section command

This command allows the user to construct an ElasticSection. The inclusion of shear deformations is optional.

section Elastic $secTag $E $A $Iz $Iy $G $J <$alphaY $alphaZ>


$secTag unique section tag
$E Young's Modulus
$A cross-sectional area of section
$Iz second moment of area about the local z-axis
$Iy second moment of area about the local y-axis (required for 3D analysis)
$G Shear Modulus (optional for 2D analysis, required for 3D analysis)
$J torsional moment of inertia of section (required for 3D analysis)
$alphaY shear shape factor along the local y-axis (optional)
$alphaZ shear shape factor along the local z-axis (optional)

example:
section Elastic 1 90000 30000 6.75e8 6.75e8 12000 1.00e12
MODELING COMMANDS

Section Aggregator command


This command is used to construct a SectionAggregator object which aggregates groups previously-defined UniaxialMaterial
objects into a single section force-deformation model. Each UniaxialMaterial object represents the section force-deformation
response for a particular section degree-of-freedom (dof). There is no interaction between responses in different dof directions.
section Aggregator $secTag $matTag1 $dof1 $matTag2 $dof2 ....... <-section $sectionTag>
$secTag unique section tag
$matTag1 $matTag2 ... tag of previously-defined UniaxialMaterial objects
$dof1 $dof2 ... the force-deformation quantity to be modeled by this section object. One of the following section dof may be used:
P Axial force-deformation
Mz Moment-curvature about section local z-axis
Vy Shear force-deformation along section local y-axis
My Moment-curvature about section local y-axis
Vz Shear force-deformation along section local z-axis
T Torsion Force-Deformation
$sectionTag tag of previously-defined Section object to which the UniaxialMaterial objects are aggregated as additional force-deformation relationships
MODELING COMMANDS

Section Aggregator command


This command is used to construct a SectionAggregator object which aggregates groups previously-defined UniaxialMaterial
objects into a single section force-deformation model. Each UniaxialMaterial object represents the section force-deformation
response for a particular section degree-of-freedom (dof). There is no interaction between responses in different dof directions.
section Aggregator $secTag $matTag1 $dof1 $matTag2 $dof2 ....... <-section $sectionTag>
$secTag unique section tag
$matTag1 $matTag2 ... tag of previously-defined UniaxialMaterial objects
$dof1 $dof2 ... the force-deformation quantity to be modeled by this section object. One of the following section dof may be used:
P Axial force-deformation
Mz Moment-curvature about section local z-axis
Vy Shear force-deformation along section local y-axis
My Moment-curvature about section local y-axis
Vz Shear force-deformation along section local z-axis
T Torsion Force-Deformation
$sectionTag tag of previously-defined Section object to which the UniaxialMaterial objects are aggregated as additional force-deformation relationships

example:
section Elastic 1 90000 30000 6.75e8 6.75e8 12000 1.00e12
uniaxialMaterial ElasticPP 1 25000 0.008
uniaxialMaterial ElasticPP 2 20000 0.012
MODELING COMMANDS

Section Aggregator command


This command is used to construct a SectionAggregator object which aggregates groups previously-defined UniaxialMaterial
objects into a single section force-deformation model. Each UniaxialMaterial object represents the section force-deformation
response for a particular section degree-of-freedom (dof). There is no interaction between responses in different dof directions.
section Aggregator $secTag $matTag1 $dof1 $matTag2 $dof2 ....... <-section $sectionTag>
$secTag unique section tag
$matTag1 $matTag2 ... tag of previously-defined UniaxialMaterial objects
$dof1 $dof2 ... the force-deformation quantity to be modeled by this section object. One of the following section dof may be used:
P Axial force-deformation
Mz Moment-curvature about section local z-axis
Vy Shear force-deformation along section local y-axis
My Moment-curvature about section local y-axis
Vz Shear force-deformation along section local z-axis
T Torsion Force-Deformation
$sectionTag tag of previously-defined Section object to which the UniaxialMaterial objects are aggregated as additional force-deformation relationships

example:
section Elastic 1 90000 30000 6.75e8 6.75e8 12000 1.00e12
uniaxialMaterial ElasticPP 1 25000 0.008
Section 2 is defined by elastic section 1, but it is associated with an elastic-plastic
uniaxialMaterial ElasticPP 2 20000 0.012 behavior around y local axis defined by material 1 and with an elastic-plastic behaviour
section Aggregator 2 1 My 2 Mz -section 1 around z local axis defined by material 2.
MODELING COMMANDS

Elastic Beam Column Element command

This command is used to construct an elasticBeamColumn element object.

element elasticBeamColumn $eleTag $iNode $jNode $A $E $G $J $Iy $Iz $transfTag <-mass $massDens> <-cMass>
$eleTag unique element object tag
$iNode $jNode end nodes
$A cross-sectional area of element
$E Young's Modulus
$G Shear Modulus
$J torsional moment of inertia of cross section
$Iz second moment of area about the local z-axis
$Iy second moment of area about the local y-axis
$transfTag identifier for previously-defined coordinate-transformation (CrdTransf) object
$massDens element mass per unit length (optional, default = 0.0)
-cMass to form consistent mass matrix (optional, default = lumped mass matrix)

example:
element elasticBeamColumn 1 1 2 90000 30000 12000 1.00e12 6.75e8 6.75e8 1
MODELING COMMANDS

Elastic Beam Column Element command

This command is used to construct an elasticBeamColumn element object.

element elasticBeamColumn $eleTag $iNode $jNode $A $E $G $J $Iy $Iz $transfTag <-mass $massDens> <-cMass>
$eleTag unique element object tag
$iNode $jNode end nodes
$A cross-sectional area of element
$E Young's Modulus
$G Shear Modulus
$J torsional moment of inertia of cross section
$Iz second moment of area about the local z-axis
$Iy second moment of area about the local y-axis
$transfTag identifier for previously-defined coordinate-transformation (CrdTransf) object
$massDens element mass per unit length (optional, default = 0.0)
-cMass to form consistent mass matrix (optional, default = lumped mass matrix)

example:
element elasticBeamColumn 1 1 2 90000 30000 12000 1.00e12 6.75e8 6.75e8 1

tag of a previously-defined geomTransf object, i.e., of a previously-defined local axis system


MODELING COMMANDS

Truss Element command

This command is used to construct a truss element object with a UniaxialMaterial identifier:

element truss $eleTag $iNode $jNode $A $matTag <-rho $rho> <-cMass $cFlag> <-doRayleigh $rFlag>
$eleTag unique element object tag
$iNode $jNode end nodes
$A cross-sectional area of element
$matTag tag associated with previously-defined UniaxialMaterial
$rho mass per unit length, optional, default = 0.0
$cFlag consistent mass flag, optional, default = 0
cFlag = 0 lumped mass matrix (default)
cFlag = 1 consistent mass matrix
$rFlag Rayleigh damping flag, optional, default = 0
rFlag = 0 NO RAYLEIGH DAMPING (default)
rFlag = 1 include Rayleigh damping

example:
element truss 1 1 2 100 1 truss element 1 between nodes 1 and 2 with Area 100 and UniaxialMaterial 1
MODELING COMMANDS

Truss Element command

This command is used to construct a truss element object with a Section identifier:

element trussSection $eleTag $iNode $jNode $secTag <-rho $rho> <-cMass $cFlag> <-doRayleigh $rFlag>
$eleTag unique element object tag
$iNode $jNode end nodes
$secTag tag associated with previously-defined Section
$rho mass per unit length, optional, default = 0.0
$cFlag consistent mass flag, optional, default = 0
cFlag = 0 lumped mass matrix (default)
cFlag = 1 consistent mass matrix
$rFlag Rayleigh damping flag, optional, default = 0
rFlag = 0 NO RAYLEIGH DAMPING (default)
rFlag = 1 include Rayleigh damping

example:
element trussSection 1 1 2 1 truss element 1 between nodes 1 and 2 with section 1
Loads
Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:
Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object
Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose a linear lateral load distribution with maximum force at the top equal to 5000?
Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose a linear lateral load distribution with maximum force at the top equal to 5000?

1.00 node 4

0.75 node 3

0.50 node 2

0.25 node 1

1. Define a linear pattern with load equal to


0.25 applied to node 1, a load equal to 0.50
to node 2 etc.
Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose a linear lateral load distribution with maximum force at the top equal to 5000?

1.00 node 4

0.75 node 3

0.50 node 2 2. Define a linear TimeSeries: The load


multiplier will vary linearly from 0 up to a
maximum value set by the user (e.g., 5000)
0.25 node 1

1. Define a linear pattern with load equal to


0.25 applied to node 1, a load equal to 0.50
to node 2 etc.
Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose a linear lateral load distribution with maximum force at the top equal to 5000?

1.00 node 4 5000 0 node 4

0.75 node 3 node 3

0.50 node 2 2. Define a linear TimeSeries: The load node 2


multiplier will vary linearly from 0 up to a
maximum value set by the user (e.g., 5000)
0.25 node 1 node 1

1. Define a linear pattern with load equal to OpenSees will apply this load up to a
0.25 applied to node 1, a load equal to 0.50 maximum value of the multiplier set
to node 2 etc. by the user (e.g., 5000) with a certain
number of steps set by the user (1 or
more than 1)
Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose a linear lateral load distribution with maximum force at the top equal to 5000?

5000 0 node 4

Each step represents a unit of time in OpenSees domain


node 3

node 2
If a Linear TimeSeries is used, each value of the load pattern multiplier is named PSEUDOTIME
node 1

OpenSees will apply this load up to a


maximum value of the multiplier set
by the user (e.g., 5000) with a certain
number of steps set by the user (1 or
more than 1)
Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose a linear lateral load distribution with maximum force at the top equal to 5000?

5000 0 node 4

Each step represents a unit of time in OpenSees domain


node 3

node 2
If a Linear TimeSeries is used, each value of the load pattern multiplier is named PSEUDOTIME
node 1

OpenSees will apply this load up to a The Plain Pattern object and the Linear TimeSeries object are usually used to
maximum value of the multiplier set perform the (force-controlled) gravity load analysis and the (displacement-
by the user (e.g., 5000) with a certain
number of steps set by the user (1 or controlled) pushover analysis
more than 1)
MODELING COMMANDS

Linear TimeSeries command

This command is used to construct a TimeSeries object in which the load factor applied is linearly proportional to the time in
the domain.

timeSeries Linear $tag <-factor $cFactor>


$tag unique tag among TimeSeries objects.
$cFactor the linear factor (optional, default=1.0)

example:
timeSeries Linear 1
MODELING COMMANDS

Plain Pattern command


This command allows the user to construct a LoadPattern object. Each plain load pattern is associated with a TimeSeries object
and can contain multiple NodalLoads, ElementalLoads and SP_Constraint objects. The command to generate LoadPattern object
contains in { } the commands to generate all the loads and the single-point constraints in the pattern.
pattern Plain $patternTag $tsTag <-fact $cFactor> {
load...
eleLoad...
sp...
...
}
$patternTag unique tag among load patterns
$tsTag the tag of the time series to be used in the load pattern
$cFactor constant factor (optional, default=1.0)
load... command to nodal load
eleLoad ... command to generate elemental load
sp ... command to generate single-point constraint
MODELING COMMANDS

Plain Pattern command


This command allows the user to construct a LoadPattern object. Each plain load pattern is associated with a TimeSeries object
and can contain multiple NodalLoads, ElementalLoads and SP_Constraint objects. The command to generate LoadPattern object
contains in { } the commands to generate all the loads and the single-point constraints in the pattern.
pattern Plain $patternTag $tsTag <-fact $cFactor> {
load...
eleLoad...
sp...
...
}
$patternTag unique tag among load patterns
$tsTag the tag of the time series to be used in the load pattern
$cFactor constant factor (optional, default=1.0)
load... command to nodal load
MODELING COMMANDS

Plain Pattern command


This command allows the user to construct a LoadPattern object. Each plain load pattern is associated with a TimeSeries object
and can contain multiple NodalLoads, ElementalLoads and SP_Constraint objects. The command to generate LoadPattern object
contains in { } the commands to generate all the loads and the single-point constraints in the pattern.
pattern Plain $patternTag $tsTag <-fact $cFactor> {
load...
eleLoad...
sp...
...
}
$patternTag unique tag among load patterns
$tsTag the tag of the time series to be used in the load pattern
$cFactor constant factor (optional, default=1.0)
load... command to nodal load

load $nodeTag (ndf $LoadValues)


$nodeTag tag of node to which load is applied.
$loadvalues ndf reference load values.
MODELING COMMANDS

Plain Pattern command


This command allows the user to construct a LoadPattern object. Each plain load pattern is associated with a TimeSeries object
and can contain multiple NodalLoads, ElementalLoads and SP_Constraint objects. The command to generate LoadPattern object
contains in { } the commands to generate all the loads and the single-point constraints in the pattern.
pattern Plain $patternTag $tsTag <-fact $cFactor> {
load...
eleLoad...
sp...
...
}
$patternTag unique tag among load patterns
$tsTag the tag of the time series to be used in the load pattern
$cFactor constant factor (optional, default=1.0)
load... command to nodal load
eleLoad ... command to generate elemental load
MODELING COMMANDS

Plain Pattern command


This command allows the user to construct a LoadPattern object. Each plain load pattern is associated with a TimeSeries object
and can contain multiple NodalLoads, ElementalLoads and SP_Constraint objects. The command to generate LoadPattern object
contains in { } the commands to generate all the loads and the single-point constraints in the pattern.
pattern Plain $patternTag $tsTag <-fact $cFactor> {
load...
eleLoad...
sp...
...
}
$patternTag unique tag among load patterns
$tsTag the tag of the time series to be used in the load pattern
$cFactor constant factor (optional, default=1.0)
load... command to nodal load
eleLoad ... command to generate elemental load

eleLoad -ele $eleTag1 <$eleTag2 ....> -type -beamUniform $Wy $Wz <$Wx>
$eleTag1 $eleTag2 ... tag of PREVIOUSLY DEFINED element
$Wy $Wz $Wx magnitude of uniformly distributed reference load acting in direction along member length (Wx) and along y and z local axes (Wy and Wz)
MODELING COMMANDS

Plain Pattern command


This command allows the user to construct a LoadPattern object. Each plain load pattern is associated with a TimeSeries object
and can contain multiple NodalLoads, ElementalLoads and SP_Constraint objects. The command to generate LoadPattern object
contains in { } the commands to generate all the loads and the single-point constraints in the pattern.
pattern Plain $patternTag $tsTag <-fact $cFactor> {
load...
eleLoad...
sp...
...
1.00 node 4
}
0.75 node 3
$patternTag unique tag among load patterns
$tsTag the tag of the time series to be used in the load pattern 0.50 node 2
$cFactor constant factor (optional, default=1.0)
load... command to nodal load 0.25 node 1

eleLoad ... command to generate elemental load


X
example:
MODELING COMMANDS

Plain Pattern command


This command allows the user to construct a LoadPattern object. Each plain load pattern is associated with a TimeSeries object
and can contain multiple NodalLoads, ElementalLoads and SP_Constraint objects. The command to generate LoadPattern object
contains in { } the commands to generate all the loads and the single-point constraints in the pattern.
pattern Plain $patternTag $tsTag <-fact $cFactor> {
load...
eleLoad...
sp...
...
1.00 node 4
}
0.75 node 3
$patternTag unique tag among load patterns
$tsTag the tag of the time series to be used in the load pattern 0.50 node 2
$cFactor constant factor (optional, default=1.0)
load... command to nodal load 0.25 node 1

eleLoad ... command to generate elemental load


X
example:
pattern Plain 1 1 {
load 1 0.25 0 0 0 0 0
load 2 0.50 0 0 0 0 0
load 3 0.75 0 0 0 0 0
load 4 1.00 0 0 0 0 0}
MODELING COMMANDS

Plain Pattern command


This command allows the user to construct a LoadPattern object. Each plain load pattern is associated with a TimeSeries object
and can contain multiple NodalLoads, ElementalLoads and SP_Constraint objects. The command to generate LoadPattern object
contains in { } the commands to generate all the loads and the single-point constraints in the pattern.
pattern Plain $patternTag $tsTag <-fact $cFactor> {
load...
eleLoad...
sp...
...
}
element 2
$patternTag unique tag among load patterns
$tsTag the tag of the time series to be used in the load pattern
$cFactor constant factor (optional, default=1.0)
load... command to nodal load
eleLoad ... command to generate elemental load

example:
MODELING COMMANDS

Plain Pattern command


This command allows the user to construct a LoadPattern object. Each plain load pattern is associated with a TimeSeries object
and can contain multiple NodalLoads, ElementalLoads and SP_Constraint objects. The command to generate LoadPattern object
contains in { } the commands to generate all the loads and the single-point constraints in the pattern.
pattern Plain $patternTag $tsTag <-fact $cFactor> {
load...
eleLoad...
sp...
...
}
element 2
$patternTag unique tag among load patterns
$tsTag the tag of the time series to be used in the load pattern
$cFactor constant factor (optional, default=1.0)
load... command to nodal load
eleLoad ... command to generate elemental load

example:
pattern Plain 1 1 {
eleLoad -ele 2 -type -beamUniform 0.0 -5.0 0.0
}
Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose an acceleration history at the building base?


Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose an acceleration history at the building base?

1.00 1.00

1. Define a uniform excitation pattern


Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose an acceleration history at the building base?

2. Define a path TimeSeries: the load


multiplier is the base acceleration (varying
with time) contained in a file reporting the
entire time-history
1.00 1.00

1. Define a uniform excitation pattern


Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose an acceleration history at the building base?

2. Define a path TimeSeries: the load


multiplier is the base acceleration (varying
with time) contained in a file reporting the
entire time-history
1.00 1.00 0.05 0.05

1. Define a uniform excitation pattern OpenSees will apply step-by-step each


value of the acceleration time-history
Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose an acceleration history at the building base?

Each step represents a unit of time in OpenSees domain

If a Path TimeSeries is used, each absolute time in the time-history is named PSEUDOTIME

0.05 0.05

OpenSees will apply step-by-step each


value of the acceleration time-history
Pattern and TimeSeries
In OpenSees, loads are always applied by means of two commands. In fact, OpenSees assumes that “loads” are always defined by
two parts/objects:

SHAPE MULTIPLIER LOAD


The load shape is defined by a Pattern object The load multiplier is defined by a TimeSeries object

Example: How to impose an acceleration history at the building base?

Each step represents a unit of time in OpenSees domain

If a Path TimeSeries is used, each absolute time in the time-history is named PSEUDOTIME

0.05 0.05

OpenSees will apply step-by-step each


value of the acceleration time-history The Uniform Excitation Pattern object and the Path TimeSeries object are
usually used to perform nonlinear time-history dynamic analysis
MODELING COMMANDS

Path TimeSeries command

This command is used to construct a Path TimeSeries object. The relationship between load factor and time is input by the user
as a series of discrete points in the 2d space (load factor, time). The input points can come from a file or from a list in the script.

timeSeries Path $tag -dt $dt -filePath $filePath <-factor $cFactor>

$tag unique tag among TimeSeries objects.


$filePath file containing the load factors values (i.e., the base acceleration)
$fileTime file containing the time values for corresponding load factors
$dT time interval between specified points.
$cFactor optional, a factor to multiply load factors by (default = 1.0)
MODELING COMMANDS

Path TimeSeries command

This command is used to construct a Path TimeSeries object. The relationship between load factor and time is input by the user
as a series of discrete points in the 2d space (load factor, time). The input points can come from a file or from a list in the script.

timeSeries Path $tag -dt $dt -filePath $filePath <-factor $cFactor>


timeSeries Path $tag -fileTime $fileTime -filePath $filePath <-factor $cFactor>

$tag unique tag among TimeSeries objects.


$filePath file containing the load factors values (i.e., the base acceleration)
$fileTime file containing the time values for corresponding load factors
$dT time interval between specified points.
$cFactor optional, a factor to multiply load factors by (default = 1.0)
MODELING COMMANDS

Path TimeSeries command

This command is used to construct a Path TimeSeries object. The relationship between load factor and time is input by the user
as a series of discrete points in the 2d space (load factor, time). The input points can come from a file or from a list in the script.

timeSeries Path $tag -dt $dt -filePath $filePath <-factor $cFactor>


timeSeries Path $tag -fileTime $fileTime -filePath $filePath <-factor $cFactor>

$tag unique tag among TimeSeries objects.


$filePath file containing the load factors values (i.e., the base acceleration)
$fileTime file containing the time values for corresponding load factors
$dT time interval between specified points.
$cFactor optional, a factor to multiply load factors by (default = 1.0)

example:
set path1 GMdirectory/record1.txt
timeSeries Path 1 -dt 0.005 -filePath $path1
MODELING COMMANDS

Path TimeSeries command

This command is used to construct a Path TimeSeries object. The relationship between load factor and time is input by the user
as a series of discrete points in the 2d space (load factor, time). The input points can come from a file or from a list in the script.

timeSeries Path $tag -dt $dt -filePath $filePath <-factor $cFactor>


timeSeries Path $tag -fileTime $fileTime -filePath $filePath <-factor $cFactor>

$tag unique tag among TimeSeries objects.


$filePath file containing the load factors values (i.e., the base acceleration)
$fileTime file containing the time values for corresponding load factors
$dT time interval between specified points.
$cFactor optional, a factor to multiply load factors by (default = 1.0)

example:
set path1 GMdirectory/record1.txt
timeSeries Path 1 -dt 0.005 -filePath $path1
set acc1 GMdirectory/acceleration1.txt
set time1 GMdirectory/time1.txt
timeSeries Path 1 -fileTime $time1 -filePath $acc1
MODELING COMMANDS

Uniform Excitation Pattern command


The UniformExcitation pattern allows the user to apply a uniform excitation to a model acting in a certain direction.

pattern UniformExcitation $patternTag $dir -accel $tsTag <-vel0 $vel0> <-fact $cFactor>
$patternTag unique tag among load patterns
$dir direction in which ground motion acts
1 - corresponds to translation along the global X axis
2 - corresponds to translation along the global Y axis
3 - corresponds to translation along the global Z axis
4 - corresponds to rotation about the global X axis
5 - corresponds to rotation about the global Y axis
6 - corresponds to rotation about the global Z axis
$tsTag tag of the TimeSeries series defining the acceleration history.
$vel0 the initial velocity (optional, default=0.0)
$cFactor constant factor (optional, default=1.0)
MODELING COMMANDS

Uniform Excitation Pattern command


The UniformExcitation pattern allows the user to apply a uniform excitation to a model acting in a certain direction.

pattern UniformExcitation $patternTag $dir -accel $tsTag <-vel0 $vel0> <-fact $cFactor>
$patternTag unique tag among load patterns
$dir direction in which ground motion acts
1 - corresponds to translation along the global X axis
2 - corresponds to translation along the global Y axis
3 - corresponds to translation along the global Z axis
4 - corresponds to rotation about the global X axis
5 - corresponds to rotation about the global Y axis
6 - corresponds to rotation about the global Z axis
$tsTag tag of the TimeSeries series defining the acceleration history.
$vel0 the initial velocity (optional, default=0.0)
$cFactor constant factor (optional, default=1.0)

example:

1.00 1.00
X
MODELING COMMANDS

Uniform Excitation Pattern command


The UniformExcitation pattern allows the user to apply a uniform excitation to a model acting in a certain direction.

pattern UniformExcitation $patternTag $dir -accel $tsTag <-vel0 $vel0> <-fact $cFactor>
$patternTag unique tag among load patterns
$dir direction in which ground motion acts
1 - corresponds to translation along the global X axis
2 - corresponds to translation along the global Y axis
3 - corresponds to translation along the global Z axis
4 - corresponds to rotation about the global X axis
5 - corresponds to rotation about the global Y axis
6 - corresponds to rotation about the global Z axis
$tsTag tag of the TimeSeries series defining the acceleration history.
$vel0 the initial velocity (optional, default=0.0)
$cFactor constant factor (optional, default=1.0)

example:
set path1 GMdirectory/record1.txt
timeSeries Path 1 -dt 0.005 -filePath $path1 1.00 1.00
X
pattern UniformExcitation 1 1 -accel 1

You might also like