> 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/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/set-phasor-settings-run-simulation.md).

# Set Phasor Settings & Run Simulation

## Introduction

When using ePHASORSIM, two different execution rates are involved:

* The **CPU model time step** configured in HYPERSIM, which determines how often the surrounding model executes.
* The **ePHASORSIM time step** configured in the **ePHASORSIM Interface** block, which defines the internal solution step used by the phasor-domain solver (default: **10 ms**).

The ePHASORSIM solver is internally decoupled from the HYPERSIM solver, so these two time steps do not need to match.

## Configure the phasor simulation settings

{% stepper %}
{% step %}

### Set the phasor time-step

In the **Common** tab of the **ePHASORSIM Interface** block, specify the **Time Step** used by the ePHASORSIM solver. Click **Apply** to save the configuration.

Choose the ePHASORSIM time step based on the power-system dynamics and performance requirements (default: **10 ms**), not the HYPERSIM execution rate.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-493705cb5acd2d9ad60d305a749b6ff279fdde8e%2Feph-hyp-time-step.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select the number of cores

To enable parallel execution, specify the number of CPU cores available to the ePHASORSIM solver. A value of **1** disables parallelization, while larger values allow the solver to distribute calculations across multiple cores.

For large models, increasing the number of available cores can significantly improve simulation performance.

{% hint style="danger" %}
Parallel execution in ePHASORSIM requires the **EPHASOR\_PARTITION\_POWERSYSTEM**, **EPHASOR\_PARALLELIZE\_GENUNITS**, and **EPHASOR\_NUM\_CORES** license features on both the workstation and simulator licenses. The value of **EPHASOR\_NUM\_CORES** must be greater than or equal to the number of solver cores used by the simulation.
{% endhint %}
{% endstep %}

{% step %}

### Connect the block interfaces and run simulation

With the simulation settings now defined, the model is ready to run.

Before starting the simulation, ensure that all **ePHASORSIM Interface** block ports are connected according to the I/O pins defined in the Excel configuration file. Any required inputs and outputs must be connected to the surrounding HYPERSIM environment.

Once the connections have been verified, save the model and start the simulation on the workstation or simulator.
{% endstep %}
{% endstepper %}

## Performance recommendations

* Start with a **10 ms** phasor time step.
* Use **1 partition** for small models.
* Increase partitions only after confirming performance benefits.
* Allocate dedicated CPU cores for large real-time models.
* Monitor execution margins after changing time step, partitions, or thread allocation.


---

# 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/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/set-phasor-settings-run-simulation.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.
