STAAD.Pro Ideas Portal

Welcome to the STAAD.Pro Ideas portal. The purpose of this site is to post ideas for enhancements and new features. We value your feedback and our team regularly reviews your suggestions for consideration in future releases.

You have 3 options for providing feedback:

  1. Vote for an existing Idea. The popularity of an Idea helps us understand its importance to our users.

  2. Comment on an existing Idea. We want to hear your unique point of view.

  3. Add a new Idea. If no existing Idea describes what you would like, add a new one!

When you Vote, Comment, or Add an idea you will also be subscribed to that Idea and will receive status updates. Please note that we may merge or rename Ideas for clarity. Thank you for your support and feedback, it is always appreciated!

Add a new idea Subscribe
Status Future consideration
Created by Tom Pallister
Created on Feb 14, 2024

RELATED IDEAS

OpenSTAAD function to extract the Beam Forces summary table for the selected beams

Hi,

Typically, to get end forces to design the connection for a certain beam size, a group is created and the bounding beam forces for the group are extracted using the "Beam Results - Beam Forces - Summary table" using the "Results Setup - Range - Group" drop down menu.

This gives the maximum and minimum Fx Fy Fz Mx My Mz for a selection of members meaning a common connection design can be used to cover that group.

This process can be achieved manually by setting up each selection and copying and pasting the results however when the number of groups is large this is time consuming and could be achieved much more efficiently with an OpenSTAAD function.


The function, "GetMemberEndForcesSummary" is proposed, and would take in an array of beam numbers and output a Variant Array of dimensions (0 to 12, 0 to 9) as per the attached image.

Best Regards,

Tom

Beam Forces Sum...
Beam Forces Summary Table.PNG
Open full size
Beam Forces Summary Table.PNG
  • Admin
    Carlos Aguera
    Reply
    |     Feb 19, 2024

    Thank you for posting this idea. It seems a reasonable suggestion. It is however, subtly different to the data reported in the table that is displayed in the Post Processing. The tables report values of the results set. The default being the whole model, but the scope can be altered using one of the Range option in the Results Setup. Not the current selection.

    I would perhaps extend the idea to provide methods for which it would be possible to get a list of members that have been assigned to a given property reference. In that way an alternative method to achieve the above would be to get the list, then using a loop routine get the results for each member and then only use those for nodes which are also used in a column so you dont account for beams that have been split to say to connect a secondary beam.