> 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/toc161394028.md).

# Member Sections

How to understand the member section properties used by the analysis engine, including area and inertia.

Each member must have a section assigned to it. The section properties include:

* A: axial section area
* Ay: shear area along the member local y direction
* Az: shear area along member the local z direction
* Izz: moment of inertia about strong the local axis z
* Iyy: moment of inertia about weak the local axis y
* J: torsional moment of inertia

Ay and Az may be zero, in which case, the program ignores shear deformations of the element. Mathematically speaking, the program interprets them as being infinite. For rectangular sections, Ay = Az = 5/6A. For solid circular sections, Ay = Az = 0.9A. For thin-walled hollow circular sections, Ay = Az = 0.5A. For wide flange sections, Ay = web area, Az = area of two flanges \[Ref. 6]. To consider member shear deformation, you must choose the proper option from the command Analysis > Analysis Options. *Shear deformation, when considered, applies to both element stiffness and local deflections.*


---

# 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/toc161394028.md?ask=<question>&goal=<user_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.
