Hi All,
Could you please expand on the response of "beams or columns names should be understood as their design paths"? When using AISC 360, the design path (i.e., what equations are evaluated) is dictated by the nature of the force (e.g. Chapter E for compression, Chapter F for flexure, Chapter H for a combination of these, ...). How does the designation of beam/bar/column affect the "design path"? Perhaps this is different for other codes/standards? Or do you mean to indicate something else by the term "design path"?
Please note that I also saw this link "https://forums.autodesk.com/t5/robot-structural-analysis-forum/differences-between-beam-bars-and-col...", which seemed to indicate the same thing to me. Specifically, it seems to indicate that there is some change in how Robot applies AISC 360 based on these terms beam/bar/column however I'm not aware of what that might be - the different chapters are selected based only on the nature of the force and (in some cases) the type of cross section (e.g., W-shape, HSS, ...). For convenience, the response in this link that suggests this to me is reproduced below:
Defining a bar as Column will lead the design module to design the bar as column,
Defining a bar as Beam will lead the design module to design the bar as beam, etc
What does this response "design as a column" mean in Robot with regard to AISC 360? Would Chapter F (i.e., flexure - often associated with beams) then be skipped for a 'column' in Robot? Similarly, would a 'beam' in Robot not be evaluated per Chapters D and/or E regardless of the axial force? Does this mean that one needs to use the type 'bar' to force evaluation by all applicable AISC 360 equations? Is there any documentation of this?
Thanks,
Keith