> 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.

**Minimum Fillet Depth**: This parameter can be used to specify the minimum fillet depth for the designated support lines.

* **Support Line**: This parameter can be used to specify the support line.
* **Minimum Fillet Depth**: This parameter can be used to specify the minimum fillet depth.


---

# 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.