The coordinate system that the strain_recovery method assumes the input loading is in is not the same as the local beam coordinate system. This update adds a keyword argument gxbeam_order (similar to the compliance_matrix method) that , if true, updates the input loading to the correct coordiante system and then outputs beam stresses and strains in the GXBeam local frame. If it is false nothing is changed from before. I added an additional test for this.
In the future it would be good to add an example of this to the docs, as currently none of the examples couple the output of the beam analysis with strain recovery; the loads are explicitly defined.
The coordinate system that the
strain_recoverymethod assumes the input loading is in is not the same as the local beam coordinate system. This update adds a keyword argumentgxbeam_order(similar to thecompliance_matrixmethod) that , if true, updates the input loading to the correct coordiante system and then outputs beam stresses and strains in the GXBeam local frame. If it isfalsenothing is changed from before. I added an additional test for this.In the future it would be good to add an example of this to the docs, as currently none of the examples couple the output of the beam analysis with strain recovery; the loads are explicitly defined.