OpenSees Cloud
OpenSees AMI
Misalignment with OpenSees
Original Post - 06 Nov 2022 - Michael H. Scott
Visit Structural Analysis Is Simple on Substack.
OpenSees has been around, solving various earthquake engineering and other problems, for over 20 years. So, I become skeptical when someone reports an error in the fundamental mathematical formulations of OpenSees.
Source: https://screenrant.com/the-office-uk-best-quotes/
Typically, the “error” comes down to misalignment of what you think OpenSees should do, e.g., based on your experience with another structural analysis software, and what you have told OpenSees to do. For example:
- The element formulations are different. Should you include shear and torsional deformations?
- You think moment-rotation and moment-curvature are the same thing.
- Geometric transformations are incorrect.
- Constraints are not handled correctly.
- You used the
Linearalgorithm. - You used an explicit time integrator with large time steps.
- You applied more load than you think. Or less.
- You mixed up static and dynamic DOFs.
- Units are inconsistent.
- Either mass or gravity load is not defined.
- You assumed pseudo-time was the load factor.
- Boundary conditions are wrong.
- You recorded and plotted the wrong response.
- You overwrote an important variable in your script.
There are several other reasons for misalignment.
Sure. There are a few bugs in the low levels of OpenSees, e.g., the inconsistent tangent returned by Concrete23.
But, solving the wave equation? OpenSees has that down.