> 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/statistical-flicker-level-analyzer.md).

# Statistical Flicker Level Analyzer

## Description

The **Statistical Flicker Level Analyzer app** 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).

{% hint style="danger" %}
You must have a Control System Toolbox™ license to use the **Statistical Flicker Level Analyzer** app.
{% endhint %}

<figure><img src="https://799605156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdlNg8IbOdahCpFCyzxSN%2Fuploads%2Fgit-blob-67832a5d919580f19bf8c57c688b1a8b76c76b6e%2Fstat_flicker_level_analyser_app_dialogbox.png?alt=media" alt=""><figcaption></figcaption></figure>

## Open the Statistical Flicker Level Analyzer App

* MATLAB® command prompt:

{% code lineNumbers="true" %}

```matlab
power_flicker
```

{% endcode %}

* [Digital Flickermeter](https://www.opal-rt.com/docs/smart-power-simulation-software-sps/blocks-functions-tools/control-and-measurements/analysis/digital-flickermeter.md) block: Click **Open statistical analysis**

## Parameters

<table data-header-hidden><thead><tr><th width="249.77777099609375"></th><th></th></tr></thead><tbody><tr><td><strong>Short-term interval (Tst)</strong> — Short-term interval value<br>IEC Standard = 600 s (default) | Custom value (s)</td><td>When you select <strong>IEC standard = 600 s</strong>, the short-term interval observation period is 10 minutes (600 seconds). This setting corresponds to the time specified in the IEC 61000-4-15 standard. Select <strong>Custom value (s)</strong> to specify the short-term interval observation period, in seconds. The default value is 300.</td></tr><tr><td><strong>N</strong> — Number of short-term intervals<br>1 (default) | positive integer</td><td>Number of short-term intervals used to measure the long-term flicker severity (Plt).</td></tr><tr><td><strong>Start time (s)</strong> — Analysis start time<br>0 (default) | positive scalar</td><td>Time of the beginning of the observed period, in seconds.</td></tr><tr><td><strong>Number of classes</strong> — Number of classes<br>256 (default) | positive integer</td><td>Number of classes that are used by the tool to compute the cumulative probability function of the instantaneous flicker level.</td></tr></tbody></table>

### **Buttons**

<table data-header-hidden><thead><tr><th width="249.77783203125"></th><th></th></tr></thead><tbody><tr><td><strong>Load</strong> — Load S5 signal<br>button</td><td>Load the S5 signal into the app. Choose between <strong>From Workspace</strong> and <strong>From file</strong>.</td></tr><tr><td><strong>Help</strong> — Open documentation<br>button</td><td>Open the documentation page.</td></tr><tr><td><strong>Compute</strong> — Compute cumulative probability function and flicker levels<br>button</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/simulation-and-analysis/statistical-flicker-level-analyzer.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.
