The OpenSees Community

The code you posted looks well to me, everything is consistent: node definition, fix conditions, GT, section definitions and orientations. Probably not causing your problem but, within a fibre {...} block you have "set" commands, May this make OpenSees confused? Different topic: Given the ...

You may be having localisation issues: Coleman&Spacone 2001 "Localization Issues in Force-Based Frames Elements". Despite you use FBE you have to ensure you have enough IPs to actually capture an objective response of the element non-linearity. Remember that this is a distributed plast...

It would be good to have more details about the elastic element and the fibre sections you are using for your ZLS elements, like materials, section discretisation, orientation vector of the ZLS element, etc. With the information you provided I may dare to say that the displacement or the load impose...

I have had similar issues with different version of OpenSEES running in both Windows and Linux machines and HPC facilities. So, I may doubt whether it is completely because of the OS or it is because of the different versions and revisions of OpenSEES. For example, the current version for Windows is...

If elastic, you can calculate the properties by hand and assigned them to the elastic element, as you are currently doing.
You can also try a fibre-based section, and then assign that section to a beam-column element.

Mass in OpenSees should be given in units of force·time²/distance, like kN·s²/m. For example, if the base units of your model is kN and m and you want to define 1000kg then in order to be consistent with your base units you should define that mass as 1 kN·s²/m. You can also create your own set of un...

I would say elements have their own local reference system, so you can define things like Iy and Iz. As a separate case, the domain has its own reference system. Now both RS do not know each other, so you have to let them know how to interact, this is done by the vector vecXZ and the geometric trans...

Are you sure that the same vecXZ vector passed in the geometrical transformation fits all the directions of the elements you defined?
You are saying tha all the elements are defined with the local z axis pointing in the global Y axis.
Also check units, mass and stiffnes definitions.

In OpenSees you have to be consistent with the basic units you are working on. If your basic units are: force in N, length in m and time in seconds, for example, then all the stresses should be given in N/m² = Pa, moments in N·m, kg in N·s²/m, ... etc. It is important to note that some materials are...

According to the commands you are using you have a 3D domain, so the vector passed in the geometrical transformation tells the domain how your element is oriented, i.e. the relationship between the element's local reference system and the global reference system. If you do not provide the vector in ...

Curvature = Rotation / Lp, where Lp is the length over which the rotation occurs. This assumes the rotation is constant over Lp.
You can read any of the many publications in the equivalent plastic hinge length for columns, walls and beams to have a better idea

Hehehe better to get them from the source code and put them into a procedure. Below the proc in case it is useful proc infoIntegracion {inte NoIPs WorP} { # Check info is correct if {$inte!="Lobatto" && $inte!="Legendre" && $inte!="Radau" && $int...

Hi, You can track the moment and curvature directly into the integration point that you are interested in. - recorder element -xml secDsp.out -time -ele $ele -section $sec displacements - recorder element -xml secFrc.out -time -ele $ele -section $sec forces If you are recording a zeroLengthSection e...

A workaround is to define a 2D domain, 2 nodes, 1 elastic section, 1 FBE/DBE element with the require IPs, save the position and weights of the IPs in variables, wipe the 2D model and then start the 3D model as normal, all in the same script execution. The "wipe" command will delete the 2D...

Working now, it gives 0.249 seconds :-D, I do not know if it is ok, I just made it run. What I did to your code was: 1. changed the builder to "model BasicBuilder -ndm 2 -ndf 3" 2. Based on the node coordinates I assumed [3] -- zero length -- [1] -- FBE -- [2], so I changed your code accor...