> 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/cable-stayed-bridge-workflow/organization-csb/cross-project-data-csb/analysis-results-csb.md).

# Analysis Results \[CSB]

For the objects in this section to be shared, the ***Transfer Result Extractions*** setting under ***Shared Objects*** and ***Shared Substructure*** must be set to ‘YES’; otherwise, the analysis result definitions for these objects will not be included in sharing.

To transfer the analysis results for the provided options, this part of the **Cross-Project Data** must be used. For further information on how to share data associated with **Bearing Forces** and **Bottom of Column Forces** refer to the relevant page of the documentation.


---

# 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/cable-stayed-bridge-workflow/organization-csb/cross-project-data-csb/analysis-results-csb.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.