> 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/import-models-from-external-software-or-code/import-from-emtp/adjust-transformer-models.md).

# Adjust Transformer Models

This page provides guidelines to ensure that winding impedances are valid and saturation curves meet HYPERSIM constraints.

## Adjustment procedure

{% stepper %}
{% step %}

## Verify winding impedances

1. Check if short-circuit test data (Z12, Z13, Z23) produces negative values for equivalent impedances (Z1, Z2, Z3). While EMTP allows negative impedance values, HYPERSIM does **not support negative values** for resistors, inductors, or capacitors. Negative values are automatically replaced by zero in HYPERSIM, which alters the model.
2. Adjust short-circuit impedance values and ensure all resulting equivalent impedances are **positive**.

Example:

$$
\begin{aligned}
Z\_{12} &= 0.0455,\text{pu} \\
Z\_{13} &= 0.3667,\text{pu} \\
Z\_{23} &= 0.3112,\text{pu} \\
\\
Z\_1 &= \frac{Z\_{12} + Z\_{13} - Z\_{23}}{2} = 0.0505,\text{pu} \\
Z\_2 &= \frac{Z\_{12} + Z\_{23} - Z\_{13}}{2} = -0.005,\text{pu} \\
Z\_3 &= \frac{Z\_{13} + Z\_{23} - Z\_{12}}{2} = 0.3162,\text{pu}
\end{aligned}
$$

Modify Z<sub>23</sub> so that negative value results from these equations.
{% endstep %}

{% step %}

## Validate saturation curve definition

1. Check the transformer saturation curve defined by (flux, current) points. While, EMTP accepts more flexible curve definitions, HYPERSIM requires stricter conditions. Invalid curves may be rejected or produce incorrect behavior.
2. Ensure the curve satisfies the following:
   * Slopes of segments are **monotonically decreasing**
   * The first point is **not (0, 0)**
   * The total number of points does not exceed **32**

Example: The curve in the figure on the left is valid in both HYPERSIM and EMTP. However, the curve shown in the figure on the right is only valid in EMTP. In HYPERSIM, the slops in the saturation curve must be monotonically decreasing.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7ea74f31e77874140b4c24ee94b8c09bba445eca%2Femtp-saturation-curve.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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/import-models-from-external-software-or-code/import-from-emtp/adjust-transformer-models.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.
