> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/openbrimfea/loads-fea/pushover-fea.md).

# Pushover \[FEA]

Pushover holds the **Pushover Case**, a nonlinear static procedure that pushes the structure with an incrementally increasing lateral load or displacement and produces a capacity curve of base shear against displacement.

It shows the sequence in which members yield, the ductility available before collapse, and the lateral strength - none of which a linear analysis can reveal.

Two things determine whether the result is meaningful. The model must actually contain nonlinearity: plastic hinges on the members expected to yield, or inelastic line elements. And the analysis must use **displacement control** if you need the softening branch, because a force-controlled analysis cannot pass the peak of the capacity curve.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openbrim.org/templates/openbrimfea/loads-fea/pushover-fea.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
