> 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/concrete-bridge-examples/example-concrete-u-girder-bridge/combinations-ex1-cug/result-extraction-cases-ex1-cug.md).

# Result Extraction Cases

This section defines result extraction cases for analysis output processing.

{% hint style="info" %}
**Navigation:** Combinations > Result Extraction Cases

For detailed parameter explanations, see the [Result Extraction Cases Reference](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/combinations-cug/result-extraction-cases-cug).
{% endhint %}

## Steps

### Step 1: Navigate to Result Extraction Cases

Navigate to **Combinations > Result Extraction Cases** in the tree view.

### Step 2: Define Extraction Cases

Create extraction cases that specify which analysis results to capture and how they should be processed.

### Step 3: Configure Output Parameters

Set parameters for each extraction case including:

* Load case selection
* Result type (forces, stresses, displacements)
* Output locations

## Verification

{% hint style="success" %}
After completing these steps, result extraction cases are configured for post-processing.
{% endhint %}


---

# 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/concrete-bridge-examples/example-concrete-u-girder-bridge/combinations-ex1-cug/result-extraction-cases-ex1-cug.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.