> 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/example-models/control-and-measurements/flickermeter-statistical-analysis-module.md).

# Flickermeter Statistical Analysis Module

This example shows a method to compute short-term flicker severity of a phase-to-ground voltage taken from one feeder of a given remote community.

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

## Description

The statistical analysis of instantaneous flicker level is performed on a phase-to-ground voltage taken from one feeder of a given network. The analyzed signal comes from a phasor simulation of 650 sec of duration of a detail model of a remote community (not discussed here).

We can observe in the analyzed signal (Signal with flicker) that a large and relatively slow voltage fluctuation is superimposed on small voltage fluctuations induced by distributed thermal storage systems. It is apparent that the slow moving voltage fluctuation did not induce significant flicker compared to the small voltage fluctuations.

The magnitude of the phasor signal is used to regenerate a 60 Hz sinewave voltage that is connected at the input of the Digital Flickermeter block. Doing so, the block can compute the instantaneous flicker level present in the voltage. The signal is saved in the S5 workspace variable. The statistical analysis module of the flickermeter is used to analyze the S5 signal.

## Simulation

1. Run the simulation. When completed, click the Open statistical analysis button of the flickermeter block.
2. In the Statistical Analysis of Instantaneous Flicker Level window, load the S5 signal from workspace. The instantaneous flicker level signal is then displayed in the upper diagram.
3. In the analysis section, set the start time value to 50 seconds to exclude from the analysis the initial spike in amplitude in the instantaneous flicker level.
4. Click the Compute button.

The cumulative probability function (CFP) is then displayed in the lower diagram. The short-term flicker severity value Pst is displayed along with the P0s, P1s, P3s, P10s, and P50s percentiles corresponding to the flicker levels exceeded for 0.1%, 1%, 3%, 10% and 50% of the time during the observed period.

## Command

Example model name: power\_KALFlicker

{% code lineNumbers="true" %}

```matlab
open('power_KALFlicker')
```

{% endcode %}


---

# 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/example-models/control-and-measurements/flickermeter-statistical-analysis-module.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.
