> 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/examples/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/superstructure-code-checks-ex1-stg/steel-tub-girder-code-check-aashto-ex1-stg.md).

# Steel Tub Girder Code Check (AASHTO)

**Step 1:** In this section, you can specify the Tub Girder that you want to be checked, the station at which you want to be checked, and the code content that you want to perform for it. This information is necessary for performing code checks.

**Step 2:** Navigate to Superstructure Code Checks > **Steel Tub Girder Code Check (AASHTO)**

![](https://openbrim.atlassian.net/wiki/download/attachments/2169995287/image-20230227-135807.png?api=v2)

**Step 3:** Click **three-dots icon** on **Girder** and set **G1** and **G2**.

One of the girders will be subjected to **constructibility code check template** while the other will undergo **service code check template.**

**Step 4:** Enter **Station** \[ft] value as 100 both them.

![](https://openbrim.atlassian.net/wiki/download/attachments/2169995287/image-20230227-140804.png?api=v2)

**Step 5:** Additionally, click **three-dots icon** on **Code Check Template** and set code check as in the figure.

**Step 6:** Keep other parameter constant as default value.

![](https://openbrim.atlassian.net/wiki/download/attachments/2169995287/image-20230227-141034.png?api=v2)

**Step 7:** Navigate Reinforcement tab.

Click **three-dots icon** on **Input Data Preference** and set **"Lumped"**.

![](https://openbrim.atlassian.net/wiki/download/attachments/2169995287/image-20230227-141733.png?api=v2)

**Step 8:** Set deck rebar material to **A615\_60** both them\*\*.\*\*

![](https://openbrim.atlassian.net/wiki/download/attachments/2169995287/image-20230227-142056.png?api=v2)

**Step 9:** Enter **"Lumped Reinforcement"** parameters specified in the corresponding cells as in the figure.

(Note that based on the input data preference, inputs not applicable automatically turns into **N/A**).

![](https://openbrim.atlassian.net/wiki/download/attachments/2169995287/image-20230227-143420.png?api=v2)

**Step 10:** You can make adjustments to the **"Stiffener"** tab if you wish.

![](https://openbrim.atlassian.net/wiki/download/attachments/2169995287/image-20230227-143722.png?api=v2)

***

{% hint style="success" %}
The Steel Tub Girder Code Check (AASHTO) have been created.
{% endhint %}

***

If icon won't appear, collapse page tree menu by clicking on arrow or using shortcut "\[".

\| `STGCC1 G1 100 STGTemp_Srv InteriorPanel 50 STGCC2 G2 100 STGTemp_Cons InteriorPanel 50` | `STGCC1 Lumped A615_60 8 3 4 3 0 0 NULL NULL NULL NULL 0 0 1 STGCC2 Lumped A615_60 8 3 4 3 0 0 NULL NULL NULL NULL 0 0 1` | \`\`\` STGCC1 NO 5 1 YES Use Cross Frame Spacing 82 NO NULL 50 STGCC2 NO 5 1 YES Use Cross Frame Spacing 82 NO NULL 50

```|
```


---

# 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/examples/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/superstructure-code-checks-ex1-stg/steel-tub-girder-code-check-aashto-ex1-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.