> 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-tub-girder-bridge-workflow/loading-stg/loads-stg/dynamic-loads-stg/response-spectrum-curve-stg.md).

# Response Spectrum Curve \[STG]

Response Spectrum Curves can be generated based on the data provided by the user.

**Period/Frequency:** The user can specify the values for the X-axis using this parameter. First, the user should use the choices 'Period' or 'Frequency.' Then, by clicking the three dots and using the 'Edit' option, the user can specify the values for both the X and Y axes, where the X-axis stands for either Frequency or Period, and the Y-axis stands for Acceleration.

![image-20241014-122152.png](https://openbrim.atlassian.net/wiki/download/attachments/2392588299/image-20241014-122152.png?api=v2)

**Points/Equations:** Users can also specify whether the Response Spectrum Curve will be generated according to the data in the form of defined points or with an equation using this parameter. After selecting the choice ‘Points’ or ‘Equations,’ users can use the ‘Edit’ option to modify the data.

If the Period/Frequency parameter is defined as shown in the figure above and point definitions are needed for the curve to be generated, no additional definitions are required. If equations for RSA generation are needed, this parameter can be specified.

**Period/Frequency vs Acceleration:** The defined data will be displayed either as points or equations in the corresponding cell of this column


---

# 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/steel-tub-girder-bridge-workflow/loading-stg/loads-stg/dynamic-loads-stg/response-spectrum-curve-stg.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.