> 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/retaining-wall-workflow/dynamic-loads-rw/eigenvalue-and-rsa-case-rw.md).

# Eigenvalue and RSA Case \[RW]

## Eigenvalue and RSA Case

Eigenvalue and RSA can be done using this section of the workflow.

To use the response spectrum results in design, add this case to a result extraction case under **Combinations** (its **Stages | Factors** list accepts it), then assign that result extraction case to **EQ (Earthquake Load)** in **Limit States**.

### Modal Parameters

**Stage:** Specify the stage for which eigenvalue and response spectrum analysis will be generated. The chosen stage will be used to determine the elements of a bridge to be considered for eigenvalue and RSA. The case is analyzed only while this stage is active.

**# of Mode Shapes:** The number of mode shapes to compute in the eigenvalue/RSA analysis. Increase this value to capture the higher-frequency modes needed for higher seismic mass participation targets. With the default of 0, no mode results are produced.

**Applied Mass:** Lists what the case's mass is made of: the elements' own mass and, from the stages of the Stage's chain whose **Include Mass** is set to Yes, the loads attached to those stages and the weight they carry without stiffness. (Read-only)

### RSA Curves

**Curve in Dir. 1:** This parameter is used to set the response spectrum curve previously defined under the **Dynamic Loads** category with the **Response Spectrum Curve** object for Eigenvalue and RSA.

**Scale in Dir. 1:** This refers to the scaling factor applied to the response spectrum curve. The scaling factor adjusts the spectral values to account for specific conditions (e.g., the intensity of seismic loads or normalization requirements).

**Curve in Dir. 2:** This parameter is used to set the response spectrum curve previously defined under the **Dynamic Loads** category with the **Response Spectrum Curve** object for Eigenvalue and RSA.

**Scale in Dir. 2:** This refers to the scaling factor applied to the response spectrum curve. The scaling factor adjusts the spectral values to account for specific conditions (e.g., the intensity of seismic loads or normalization requirements).

**Curve in Dir. 3:** This parameter is used to set the response spectrum curve previously defined under the **Dynamic Loads** category with the **Response Spectrum Curve** object for Eigenvalue and RSA.

**Scale in Dir. 3:** This refers to the scaling factor applied to the response spectrum curve. The scaling factor adjusts the spectral values to account for specific conditions (e.g., the intensity of seismic loads or normalization requirements).

**Dir. Angle:** This is the **rotation angle** (in degrees) of the principal axis used for the seismic response.When seismic forces act along an axis that isn’t perfectly aligned with the global axes (e.g., rotated by 30°), this parameter specifies that rotation angle to account for directional effects correctly.

### RSA Combination

**Damping Ratio:** The damping ratio represents the energy dissipation in the system, expressed as a fraction of critical damping, and it can be specified using this parameter. It influences how quickly the oscillations from seismic loads decay.

**Model Combination Method \[CQC/SRSS]:** The model computation method can be specified using this parameter.

* **CQC (Complete Quadratic Combination):** This method is used when modes are closely spaced or have significant modal coupling. It accounts for the correlation between modes.
* **SRSS (Square Root of the Sum of the Squares):** This method assumes modes are uncorrelated. It is suitable when the modal frequencies are sufficiently separated.

**Spatial Combination Method \[ABS/SRSS/CQC3]:** The spatial computation method can be specified using this parameter.

* **ABS (Absolute Sum):** This method sums the absolute values of responses from different directions. It is a conservative approach.
* **SRSS (Square Root of the Sum of the Squares):** This method combines responses from multiple directions, assuming they are independent. It provides a less conservative result than ABS.
* **CQC3:** Combines the directional responses accounting for the correlation between the two horizontal components, using the critical-angle formulation.

**γ - (CQC3):** The ratio of the minor to the major horizontal spectrum used by the CQC3 spatial combination. Applies only when the Spatial Combination Method is CQC3.

### Mass Source

Eigenvalue and RSA-related calculations consider the bridge elements constructed based on the Stage parameter of this object. However, for loads that are not generated by objectwise methods (such as roadway and stay-in-place formwork), this section can be utilized.

The loads defined under **Loading > Loads >Static Loads** and **Element Loads** can be assigned to the Mass Case parameters.

The Stage itself also counts as a mass case: its chain's attached loads and carried weight take the first of Mass Case 1 to 5 that is left empty. If all five are used, the Stage's loads are not counted as mass and an issue says so; clear one Mass Case to count them.

**Mass Case 1:** Specify a mass case (a previously defined static load or element load case).

**Mass Case 1 Factor:** This factor is a multiplier applied to the mass defined in Mass Case 1 when the mass matrix is assembled. It adjusts the effective mass used in the analysis to reflect variations in loading conditions or design considerations.

**Mass Case 2:** Specify a mass case (a previously defined static load or element load case).

**Mass Case 2 Factor:** This factor is a multiplier applied to the mass defined in Mass Case 2 when the mass matrix is assembled. It adjusts the effective mass used in the analysis to reflect variations in loading conditions or design considerations.

**Mass Case 3:** Specify a mass case (a previously defined static load or element load case).

**Mass Case 3 Factor:** This factor is a multiplier applied to the mass defined in Mass Case 3 when the mass matrix is assembled. It adjusts the effective mass used in the analysis to reflect variations in loading conditions or design considerations.

**Mass Case 4:** Specify a mass case (a previously defined static load or element load case).

**Mass Case 4 Factor:** This factor is a multiplier applied to the mass defined in Mass Case 4 when the mass matrix is assembled. It adjusts the effective mass used in the analysis to reflect variations in loading conditions or design considerations.

**Mass Case 5:** Specify a mass case (a previously defined static load or element load case).

**Mass Case 5 Factor:** This factor is a multiplier applied to the mass defined in Mass Case 5 when the mass matrix is assembled. It adjusts the effective mass used in the analysis to reflect variations in loading conditions or design considerations.

**Self Mass Factor:** Multiplier on the elements' own mass (default 1). The Stage never supplies the members' own mass, so this factor alone controls it.

**Additional Mass Case:** This parameter is used to define additional mass cases when necessary.

* **Mass Case :** Specify an additional mass case (a previously defined static load or element load case).
* **Mass Case Factor:** This factor is a multiplier applied to the mass defined in additional Mass Cases. It adjusts the effective mass used in the analysis to reflect variations in loading conditions or design considerations.


---

# 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/retaining-wall-workflow/dynamic-loads-rw/eigenvalue-and-rsa-case-rw.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.
