> 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/control-and-measurements/power_flicker.md).

# power\_flicker

## Description

The **power\_flicker function** computes the short-term flicker severity (Pst) and long-term flicker severity (Plt) and displays the cumulative probability function (CPF) of an instantaneous flicker level signal (S5 signal).

## Syntax

{% code lineNumbers="true" %}

```matlab
power_flicker
```

{% endcode %}

{% hint style="danger" %}
You must have a Control System Toolbox™ license to use the power\_flicker function.
{% endhint %}

## Dialog Box

<table data-header-hidden><thead><tr><th width="250.111083984375"></th><th></th></tr></thead><tbody><tr><td><strong>Load</strong></td><td><p>Load the S5 signal into the tool. Choose between <strong>From file</strong> and <strong>From workspace</strong>.</p><p>The default value is <strong>From workspace</strong>.</p></td></tr><tr><td><strong>10 minutes Short-term interval (IEC standard)</strong></td><td><p>When this parameter is selected, the short-term interval observation period is set to 10 minutes (600 seconds).</p><p>This setting corresponds to the time specified in the IEC 61000-4-15 standard. This parameter is selected by default.</p></td></tr><tr><td><strong>Short-term interval Tshort (s)</strong></td><td><p>Specify the short-term interval observation period, in seconds.</p><p>This parameter is dimmed when the 10 minutes Short-term interval parameter (IEC standard) parameter is selected. The default value is 600.</p></td></tr><tr><td><strong>Long-term interval (N x Tshort) N</strong></td><td>Specify the number of 10-minute intervals used by the tool to measure the long-term flicker severity (Plt). The default value is 1.</td></tr><tr><td><strong>Start time (s)</strong></td><td><p>Specify the time, in seconds, of the beginning of the observed period.</p><p>The default value is 0.</p></td></tr><tr><td><strong>Number of classes</strong></td><td><p>Specify the number of classes, which are used by the tool to compute the cumulative probability function of the instantaneous flicker level.</p><p>The default value is 256.</p></td></tr><tr><td><strong>Compute</strong></td><td>Compute the percentiles P0.1s, P1s, P3s, P10s, and P50s, which are the flicker levels exceeded for 0.1%, 1%, 3%, 10%, and 50% of the time during the observed period. Computes the short-term flicker severity (Pst) and long-term flicker severity (Plt) and displays the cumulative probability function (CPF) of the S5 signal.</td></tr></tbody></table>


---

# 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/control-and-measurements/power_flicker.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.
