> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/smart-power-simulation-software-sps/blocks-functions-tools/simulation-and-analysis/power_steadystate.md).

# power\_steadystate

## Description

The **power\_steadystate function** computes steady-state values of voltages and currents of model. The function returns the steady-state values of the inductor currents and capacitor voltages (electrical state variables), steady-state voltages and currents of measurement blocks and sources, and steady-state voltages and currents of nonlinear blocks of a model.

If the model contains power electronic switches (diodes, thyristors, IGBTs, and so on), the steady-state values are computed considering them as open-circuit. If the model contains breakers (the Breaker, Three-Phase Breaker, or Three-Phase Fault blocks) the steady-state values are computed considering their initial status (open-circuit or short-circuit).

## Syntax

```
sps = power_steadystate('sys')
```

## Output Arguments

This function returns a structure with these fields:

<table data-header-hidden><thead><tr><th width="249.77777099609375"></th><th></th></tr></thead><tbody><tr><td><strong>Field</strong></td><td><strong>Description</strong></td></tr><tr><td>circuit</td><td>The name of the model</td></tr><tr><td>Frequencies</td><td>Vector listing the source frequencies in the model</td></tr><tr><td>States</td><td>The names of the electrical states of the model</td></tr><tr><td>Xss</td><td>The steady-state values of electrical states of the model</td></tr><tr><td>DependentStates</td><td>The names of the dependent states, if any</td></tr><tr><td>Measurements</td><td>The names of the measurement blocks in the model</td></tr><tr><td>Yss_Measurements</td><td>The steady-state values of the measurement blocks in the model</td></tr><tr><td>Sources</td><td>The names of the electrical source blocks in the model</td></tr><tr><td>Uss_Sources</td><td>The steady-state values of the electrical sources in the model</td></tr><tr><td>NonlinearOutputs</td><td><p>The names of the outputs that correspond to the nonlinear blocks (current-source injection based models).</p><p>This value consist of the measured terminal voltages used by the nonlinear models to compute the corresponding current sources</p></td></tr><tr><td>Yss_NonlinearOutputs</td><td>The steady-state values of the outputs used by the nonlinear blocks</td></tr><tr><td>NonlinearInputs</td><td>The names of the inputs corresponding to the nonlinear blocks in the model</td></tr><tr><td>Uss_NonlinearInputs</td><td>The steady-state values of the current inputs defined by the nonlinear blocks (current-source injection based models)</td></tr></tbody></table>

{% hint style="info" %}
When the model contains more that one source frequency, the Xss, Yss\_Measurements, Uss\_Sources, Yss\_NonlinearOutputs, and Uss\_NonlinearInputs fields return a matrix of steady-state values. For every source frequency listed in the Frequencies field, there is a corresponding column of steady-states values in the matrix.
{% 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://www.opal-rt.com/docs/smart-power-simulation-software-sps/blocks-functions-tools/simulation-and-analysis/power_steadystate.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.
