This is not really a bug, but is an inconsistency that is causing difficulties for me.
The Truss element supports queries 'axialForce,' 'forces,' 'localForces' for ElementRecorder in recording force information, but the CorotTruss supports only 'axialForce'.
I am working on an optimization program that automatically generates input files for openSees, both for linear and large displacement analysis. It would be _much_ easier if I could use 'localForces' for CorotTruss, the way I can for Truss and ElasicBeamColumn.
OpenSees is a great program.
Thank you,
Kirk Martini
CorotTruss recorder queries.
Moderators: silvia, selimgunay, Moderators