OpenSeesPy icon indicating copy to clipboard operation
OpenSeesPy copied to clipboard

Line mesh

Open Ayubirad opened this issue 1 year ago • 2 comments

Dear Dr. @zhuminjie I would appreciate it if you could kindly respond to the questions below:

  1. In the Elastic Beam Column Element definition:
element('elasticBeamColumn', eleTag, *eleNodes, Area, E_mod, G_mod, Jxx, Iy, Iz, transfTag, <'-mass', mass>, <'-cMass'>)

element('elasticBeamColumn', eleTag, *eleNodes, secTag, transfTag, <'-mass', mass>, <'-cMass'>, <'-releasez', releaseCode>, <'-releasey', releaseCode>)

the <'-releasez', releaseCode>, <'-releasey', releaseCode> arguments could be used in the first command too, correct?

  1. In the line mesh definition:

mesh('line', tag, numnodes, *ndtags, id, ndf, meshsize, eleType='', *eleArgs=[])

When I release the moments using the above definition, instead of releasing the moment at nodes defined in *ndtags it releases the moment at all the nodes of the mesh created which leads to an unstable model!

How can I fix that?

  1. Could you please add the Elastic Timoshenko Beam Column Element to the line mesh command too?

All the best, Ayubirad

Ayubirad avatar Apr 19 '23 10:04 Ayubirad

  1. Try it out, see if it works on a simple example
  2. The mesh command applies the same args to each element in the mesh. You can define the first and last elements with release then use mesh to define the interior elements
  3. Yes, we can do that. Note that the elastic Timoshenko element does not have moment releases

mhscott avatar Apr 19 '23 14:04 mhscott

Thanks Prof. @mhscott Regarding number 2, I'm modeling a 3D 36-m Warren truss using elasticBeamColumn elements. Manually defining the first and last elements for each node and releasing the moment would be a really time-consuming process. Thanks for the quick reply. Best regards,

Ayubirad avatar Apr 21 '23 20:04 Ayubirad