> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/e3d-user-manual/model-entities/toc161394027.md). # Members Understanding members, the two-node frame elements used for beams, frames, and trusses in ENERCALC 3D. A member is a two-node straight frame element with a constant cross section. The term “frame element”, “beam element”, and “member” are used interchangeably in this program. The truss element is a special frame element with moments fully released at both ends. The frame element formulation accounts for axial, torsional, and bending about strong and weak axes, with options to include shear deformations and axial stress stiffening (P-Delta) effects. Moment releases may be applied to either or both ends of the element. The frame element may be used to model continuous beams, 2D or 3D frames, 2D or 3D trusses or a mixture of two. The program provides powerful commands to generate commonly used framed structures such as continuous beams, 2D or 3D frames, arc beams, and non-prismatic beams. A non-prismatic member is approximated by subdividing the original member into several prismatic members. You may access these commands from the Create ribbon. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://enercalc.com/docs/e3d-user-manual/model-entities/toc161394027.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.