# Static Pushover Graph \[CUG]

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: 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:

```
GET https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/reports-cug/static-pushover-graph-cug.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.