> 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-rlc-and-shunt-connections.md).

# Adjust RLC and Shunt Connections

This page provides guidelines to identify and proactively address RLC modeling discrepancies between EMTP and HYPERSIM.

## Adjustment procedure

{% stepper %}
{% step %}

## Identify floating Y (shunt) connections

1. Check if R, L, or C components are connected in a **floating star (Y) configuration** using a neutral point created externally. While EMTP allows floating neutral connections, HYPERSIM does **not recognize floating Y shunt configurations**. These components may be interpreted as **series elements with a floating node**, resulting in no power consumption.
2. Replace the configuration with a supported topology:
   * Use a **Bus to ABC** element to represent floating shunt components correctly
   * Alternatively, use a **grounded Y configuration** when applicable
     {% endstep %}

{% step %}

## Verify RLC component configuration (series vs shunt)

1. Check how RLC components are defined and connected in the model. In EMTP, RLC elements are always modeled as **series branches**, even when used to represent shunt behavior. In HYPERSIM, RLC components must be explicitly defined as **series or shunt**, and the distinction affects how they are interpreted.
2. Ensure each component is explicitly configured as either:
   * **Series**, or
   * **Shunt** (grounded Y, floating Y, or delta)
   * Adjust the configuration so that it matches the intended physical behavior of the model
     {% endstep %}

{% step %}

## Ensure RLC element values are valid

1. Check if all R, L, and C values in an RLC component are equal to zero. While EMTP allows all R, L, C values to be zero in a branch, HYPERSIM requires **at least one non-zero element**. A zero-valued branch results in an initialization error.
2. Assign at least one element a non-zero value. You may use a very small value (greater than **1e-10)** to approximate a short circuit.
   {% 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-rlc-and-shunt-connections.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.
