> 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/steel-i-girder-bridge-workflow/reports-sig/fillet-depth-sig.md).

# Fillet Depth \[SIG]

By taking girder deflection into account based on the concrete deck casting (for both pouring and hardening stages), the fillet depth may need to be recalculated. To achieve this, this object can be utilized. However, for the deflections based on DC1 (non-composite dead load case) and DC2 (composite dead load case) to be calculated successfully, the analysis and design must be completed.

![image-20241128-072756.png](https://openbrim.atlassian.net/wiki/download/attachments/2127167531/image-20241128-072756.png?api=v2)

## General

**DC1**: Specify the non-composite dead load case using this parameter.

**DC2**: Specify the composite dead load case using this parameter.

**Girder**: Specify the related girder.

## What the report shows

The fillet is read from the girder **as modelled**: the concrete from the deck bottom to the top of the top flange at every station. That is the Haunch Thickness minus the top flange thickness, plus two corrections for what the girder line does not follow between its supports. The girder takes the deck thickness and the cross slope at its supports and splice ends and runs straight between them, while the deck soffit follows the actual deck thickness and the actual cross slope. So extra deck thickness between supports reduces the fillet, and in a superelevation transition the fillet changes by the difference between the actual cross slope at the girder and the straight-line one, which can be several inches. The table lists, per station, the profile grade line and its chord between supports, the DC1 and DC2 deflections, the fillet as modelled, the fillet after those deflections (a downward deflection deepens it), the top-flange splice plate thickness wherever the station falls on a field splice's outer top plate, and the clear fillet above the plate.

There is no minimum-fillet input on this object any more. To set the haunch so that the fillet stays within limits, use **Compute Linear Haunch** on the girder's Haunch Thickness column: it asks for the minimum and maximum fillet depth, keeps the girder straight between supports while the deck follows the vertical curve, and clears the top-flange splice plates. The girder's read-only **Min./Max. Fillet Depth** columns then show the result, measured the same way as this report.

The report's final section plots, for each girder, the top of deck and the top of the top flange along the girder, and the fillet depth as modelled and after the DC1+DC2 deflection, with the least and greatest fillet marked.


---

# 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/templates/steel-i-girder-bridge-workflow/reports-sig/fillet-depth-sig.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.