> 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/custom-girder-bridge-workflow/loading-cg/loads-cg/pushover-load-cg-1.md).

# Pushover Load \[CG]

A Pushover Load is the load that a **Pushover Case** increases step by step. It acts on a pier cap or a column and names the Pushover Case it belongs to.

### General

**Element \[Pier Cap/Column]:** Whether the load is applied to a pier cap or to a column.

**Pier Cap:** The pier cap that receives the pushover load. Available when Element is set to Pier Cap, and must then be selected.

**Column:** The column that receives the pushover load. Available when Element is set to Column, and must then be selected.

**Pushover Case:** The pushover case this load belongs to.

**Fx:** Force along the X-axis, scaled by the load factor of the Pushover Case as the push proceeds.

**Fy:** Force along the Y-axis, scaled by the load factor of the Pushover Case as the push proceeds.

**Fz (Gravity):** Vertical force, scaled by the load factor of the Pushover Case as the push proceeds. A positive value acts downward.

**Mx:** Moment about the X-axis, scaled by the load factor of the Pushover Case as the push proceeds.

**My:** Moment about the Y-axis, scaled by the load factor of the Pushover Case as the push proceeds.

**Mz:** Moment about the Z-axis, scaled by the load factor of the Pushover Case as the push proceeds.


---

# 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/custom-girder-bridge-workflow/loading-cg/loads-cg/pushover-load-cg-1.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.
