> 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/box-culvert-workflow/reports-bc/culvert-analysis-results-bc.md).

# Culvert Analysis Results \[BC]

The Culvert Analysis Results report presents the forces extracted from the analysis at the culvert's design cut positions — the slab midspans and faces, and the wall ends and midheight — for each load combination in the selected table.

It reports what the analysis produced rather than what a code check makes of it, so it is the place to look when a demand in the code check needs tracing back to a combination and a location.

## General

**Box Culvert:** The culvert barrel to report on. A selection is required.

**Load Combination Table:** The table of factored load combinations the results are extracted for. Use the same table the code check uses, so the two documents describe the same combinations.

**Decimals Shown:** Number of decimal places used for the reported values, between 0 and 6.


---

# 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/box-culvert-workflow/reports-bc/culvert-analysis-results-bc.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.