Issue with Chord Rotation Capacity Calculation in SeismoStruct Using NTC Standards
Posted: 18 Jul 2024, 11:44
Hello everyone,
I am encountering a doubt with the calculation of the rotation capacity in SeismoStruct when using the NTC standards for verification. Specifically, I observe large variations in the rotation capacity at the chord with minimal changes in the shear span (M/V ratio) (other parameters, including the mechanical percentage of tensile and compressive longitudinal reinforcement, remain unchanged).
For example, in my NLTH analysis, at step 1.61s, the shear span is 0.60796414 meters, and the calculated rotation capacity is 0.01057372 (perfect match with my hand calculation). However, at the next step (1.62s), the shear span changes slightly to 0.607226977 meters, and the rotation capacity suddenly increases to 0.02095776. This drastic change seems to occur when a certain limit is surpassed, although all other parameters remain constant.
Could anyone provide insights into why SeismoStruct behaves this way? Are there specific shear span limits defined within the software when using the NTC standards for section verification? Any advice or clarification on this matter would be greatly appreciated.
Thank you for your assistance.
Best regards,
Daniele
I am encountering a doubt with the calculation of the rotation capacity in SeismoStruct when using the NTC standards for verification. Specifically, I observe large variations in the rotation capacity at the chord with minimal changes in the shear span (M/V ratio) (other parameters, including the mechanical percentage of tensile and compressive longitudinal reinforcement, remain unchanged).
For example, in my NLTH analysis, at step 1.61s, the shear span is 0.60796414 meters, and the calculated rotation capacity is 0.01057372 (perfect match with my hand calculation). However, at the next step (1.62s), the shear span changes slightly to 0.607226977 meters, and the rotation capacity suddenly increases to 0.02095776. This drastic change seems to occur when a certain limit is surpassed, although all other parameters remain constant.
Could anyone provide insights into why SeismoStruct behaves this way? Are there specific shear span limits defined within the software when using the NTC standards for section verification? Any advice or clarification on this matter would be greatly appreciated.
Thank you for your assistance.
Best regards,
Daniele