You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
Could you please add the Elastic Timoshenko Beam Column Element to the line mesh command too?
All the best,
Ayubirad
The text was updated successfully, but these errors were encountered:
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
Yes, we can do that. Note that the elastic Timoshenko element does not have moment releases
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,
Dear Dr. @zhuminjie
I would appreciate it if you could kindly respond to the questions below:
the
<'-releasez', releaseCode>, <'-releasey', releaseCode>
arguments could be used in the first command too, correct?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?
All the best,
Ayubirad
The text was updated successfully, but these errors were encountered: