> 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/concrete-u-girder-bridge-workflow/loading-cug/loads-cug/prestressing-load-cug/tendon-stressing-cug.md).

# Tendon Stressing \[CUG]

For additional loads that arise due to using Tendons for structural elements can be calculated and defined using this object.

**Stage:** This parameter can be used to specify the stage at which the load is initially applied to the structure.

**Tendon:** Selecting the modeled tendon that will be used for load calculations is done by specifying this parameter.

**Stressing At Start(%):** Jacking force at the start point of the tendon.

**Stressing At End(%):** Jacking force at the end point of the tendon.

**Instantaneous Elastic Shortening Loss \[Ignore/Include]:** The immediate loss of prestressing force in the tendons due to the elastic shortening of the concrete upon the application of the prestressing force can be defined using this parameter.


---

# 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/concrete-u-girder-bridge-workflow/loading-cug/loads-cug/prestressing-load-cug/tendon-stressing-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.