> 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/concrete-u-girder-bridge-workflow/loading-cug/loads-cug/water-load-cug/buoyancy-cug.md).

# Buoyancy \[CUG]

**Stage:** Choose the stage at which to apply the load.

**Support Line:** Select the support line. The buoyancy load will be applied to the substructure components below this support line. The uplift force is automatically calculated by OpenBrIM based on the submerged volume of piles, footings, and pier columns.

**Water Table Elevation Input \[Input/Use Soil Set Data]:** This parameter controls how the Water Table Elevation is specified. If a Soil Set is already defined in the model, it can be assigned parametrically; otherwise, the user can specify it separately.

**Water Table Elevation:** Specifies the global elevation of the water table.

**Soil Set:** Assign the Soil Set for the Water Table Elevation.


---

# 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/concrete-u-girder-bridge-workflow/loading-cug/loads-cug/water-load-cug/buoyancy-cug.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.