Updating Command Language Manual
Moderators: silvia, selimgunay, Moderators
Updating Command Language Manual
i am updating the command-language manual.
any recommendations on needs and clarifications would be appreciated.
any recommendations on needs and clarifications would be appreciated.
Silvia Mazzoni, PhD
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
> in the recorder specify the option to choose a recording timestep:
-dT $dt
> Specify that the zerolength elements can only connect 2DOF nodes.
> indicate how to remove recorders
(e.g.
set a [recorder $arguments]
remove a
)
> Also discuss removing fixities.
>Indicate that the model basicbuilder command can be used many times in our model to define different DOF regions.
>Indicate how can one apply pore pressure conditions conditions in the UCSD quad-up elements:
set Timeseries24 "Constant -factor 134.56"
pattern MultipleSupport 2 {
groundMotion 24 Plain -vel $Timeseries24
imposedMotion 24 3 24
}
>I think there is no documentation on the multiaxialcyclic plasticity model (there is the relevant info in the source files)
>setTime command
>loadconst command
-dT $dt
> Specify that the zerolength elements can only connect 2DOF nodes.
> indicate how to remove recorders
(e.g.
set a [recorder $arguments]
remove a
)
> Also discuss removing fixities.
>Indicate that the model basicbuilder command can be used many times in our model to define different DOF regions.
>Indicate how can one apply pore pressure conditions conditions in the UCSD quad-up elements:
set Timeseries24 "Constant -factor 134.56"
pattern MultipleSupport 2 {
groundMotion 24 Plain -vel $Timeseries24
imposedMotion 24 3 24
}
>I think there is no documentation on the multiaxialcyclic plasticity model (there is the relevant info in the source files)
>setTime command
>loadconst command
thank you
about the last 2, they are under miscellaneous commands
also, some elements and features are not documented officially as either the documentation has not been provided or the features have not been tested fully.
thank you
about the last 2, they are under miscellaneous commands
also, some elements and features are not documented officially as either the documentation has not been provided or the features have not been tested fully.
thank you
Silvia Mazzoni, PhD
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
for "Indicate how can one apply pore pressure conditions conditions in the UCSD quad-up elements:
set Timeseries24 "Constant -factor 134.56"
pattern MultipleSupport 2 {
groundMotion 24 Plain -vel $Timeseries24
imposedMotion 24 3 24
}
"
can you please be specific as to which elements (where should i put it into the manuaL)
thank you!
set Timeseries24 "Constant -factor 134.56"
pattern MultipleSupport 2 {
groundMotion 24 Plain -vel $Timeseries24
imposedMotion 24 3 24
}
"
can you please be specific as to which elements (where should i put it into the manuaL)
thank you!
Silvia Mazzoni, PhD
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
Structural Consultant
Degenkolb Engineers
235 Montgomery Street, Suite 500
San Francisco, CA. 94104
-
- Posts: 79
- Joined: Tue Nov 07, 2006 3:17 am
- Location: Jacobs
-
- Posts: 79
- Joined: Tue Nov 07, 2006 3:17 am
- Location: Jacobs
-
- Posts: 71
- Joined: Sat Nov 29, 2008 10:18 am
- Location: -
Re: Updating Command Language Manual
Silvia! The geomTranf command for a 3d model! I'll really appreciate any improvement in this part of the manual.
PS: also, change this sentence:
"The local y-axis is defined by taking the cross product of the x-axis and the vecxz vector."
by this one:
"The local y-axis is defined by taking the cross product of the vecxz vector and the x-axis."
Since,
---------------------------
local y-axis := vecxz [crossProduct] local x-axis;
---------------------------
Thanks in advance.
PS: also, change this sentence:
"The local y-axis is defined by taking the cross product of the x-axis and the vecxz vector."
by this one:
"The local y-axis is defined by taking the cross product of the vecxz vector and the x-axis."
Since,
---------------------------
local y-axis := vecxz [crossProduct] local x-axis;
---------------------------
Thanks in advance.
Hugo Esquivel
For the UC San Diego Soil Elements
> FourNodeQuadUP elements
I haven't tried it on the other three UCSD soil Elements but since for all the four elements the velocity of the third DOF is the pore pressure then it should work for all four.
To set pore pressure to be $p at node $NodeID then one should write:
set Timeseries "Constant -factor $p"
pattern MultipleSupport 1 {
groundMotion $GMID Plain -vel $Timeseries
imposedMotion $NodeID 3 $GMID
}
-------------------------
for "Indicate how can one apply pore pressure conditions conditions in the UCSD quad-up elements:
set Timeseries24 "Constant -factor 134.56"
pattern MultipleSupport 2 {
groundMotion 24 Plain -vel $Timeseries24
imposedMotion 24 3 24
}
"
can you please be specific as to which elements (where should i put it into the manuaL)
thank you!
> FourNodeQuadUP elements
I haven't tried it on the other three UCSD soil Elements but since for all the four elements the velocity of the third DOF is the pore pressure then it should work for all four.
To set pore pressure to be $p at node $NodeID then one should write:
set Timeseries "Constant -factor $p"
pattern MultipleSupport 1 {
groundMotion $GMID Plain -vel $Timeseries
imposedMotion $NodeID 3 $GMID
}
-------------------------
for "Indicate how can one apply pore pressure conditions conditions in the UCSD quad-up elements:
set Timeseries24 "Constant -factor 134.56"
pattern MultipleSupport 2 {
groundMotion 24 Plain -vel $Timeseries24
imposedMotion 24 3 24
}
"
can you please be specific as to which elements (where should i put it into the manuaL)
thank you!
-
- Posts: 71
- Joined: Sat Nov 29, 2008 10:18 am
- Location: -
Re: Updating Command Language Manual
Hi Silvia. Now it seems that in OpenSees v2.0, the rigidLink command doesn't accept the argument "rod" but "bar".
Thanks in advance.
Thanks in advance.
Hugo Esquivel