> 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/steel-tub-girder-bridge-workflow/reports-stg/static-pushover-graph-stg.md).

# Static Pushover Graph \[STG]

Select the **Pushover Case** and **RSA Case** you intend to compare. Once the cases are selected, OpenBrIM automatically identifies the most critical hinge location on the pier column. For this hinge node, the software extracts the corresponding displacements from both the Pushover Analysis and the Response Spectrum Analysis and performs a side-by-side comparison of these displacement values. An example report output is displayed below.![image-20251117-121136.png](https://openbrim.atlassian.net/wiki/download/attachments/3424387074/image-20251117-121136.png?api=v2)

![image-20251117-121156.png](https://openbrim.atlassian.net/wiki/download/attachments/3424387074/image-20251117-121156.png?api=v2)

## Advanced

**Result Coord. System \[Alignment/Global]:** Coordinate system in which pushover displacements are reported. Alignment uses the local alignment axes of the pier; Global uses the project's global coordinate system.

**Run for Pushover Graph Only (Ignore RSA Case) \[No/Yes]:** When set to Yes, the pushover graph is generated without comparing to a Response Spectrum Analysis case. Use this when an RSA case has not yet been defined or when a standalone pushover curve is needed.


---

# 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://docs.openbrim.org/templates/steel-tub-girder-bridge-workflow/reports-stg/static-pushover-graph-stg.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.