> 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/templates-for-code-check-ex1-stg/steel-tub-girder-code-check-t-ex1-stg.md).

# Steel Tub Girder Code Check T

If the goal is to check both the constructibility limit state as well as strength service and fatigue, it may be necessary to define more than one tub girder code check template for a project. Results that are mapped with the load combination table will be different for each of these limit states, and having separate templates can help ensure that all necessary checks are performed.

**Step 1:** In order to perform **Code Checks** on **Steel Tub Girders**, assign the appropriate Load Combination Tables.

As girders are part of the **superstructure** of bridges, the Load Combination Tables defined for the superstructure in previous steps should be utilized.

**Step 2:** Navigate to Templates for Code Check > **Steel Tub Girder Code Check**

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

**Step 3:** For Steel Tub Girder code check, 2 Load Combination Tables must be defined.

These are **serviceability** and **constructability.**

Enter the name in the **Name** column as follows:

* for serviceability: **STGTemp\_Srv**
* for constructability: **STGTemp\_Cons**

**Step 4:** Click **three-dots icon** on **Load Combination Table** and set **SuperstructureLCT both them.**

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

**Step 5:** Click **three-dots icon** on **Check For** set data as in the figure.

Keep other parameter constant as default value. (**"Include Haunch for Section Properties?"** and **"Mlat Comp. Method"**)

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

**Step 6:** Navigate to **Bridge Parameters** tab.

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

**Step 7:** This section includes the parameters for Steel Tub Girder code checks, such as **ADTT** (daily average vehicle traffic) and the number of lanes **available for trucks**.

As the project has three lanes, two lanes are designated for truck traffic.

***

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

***

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

| **Steel Tub Girder Code Check**                               |                   |
| ------------------------------------------------------------- | ----------------- |
| Code Parameters                                               | Bridge Parameters |
| \`\`\`                                                        |                   |
| STGTemp\_Srv SuperstructureLCT StrengthServiceFatigue YES FEA |                   |
| STGTemp\_Cons SuperstructureLCT Constructibility YES FEA      |                   |
| \`\`\`                                                        | \`\`\`            |
| STGTemp\_Srv 1000 2                                           |                   |
| STGTemp\_Cons 1000 2                                          |                   |

```|
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openbrim.org/examples/steel-bridge-examples/example-steel-tub-girder-bridge-ex1-stg/templates-for-code-check-ex1-stg/steel-tub-girder-code-check-t-ex1-stg.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.