> 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-node-connector-usage.md).

# Adjust Node Connector Usage

This page provides guidelines to identify and proactively address node connection discrepancies between EMTP and HYPERSIM.

## Adjustment procedure

{% stepper %}
{% step %}

## Verify use of node connectors

Check if the model uses **Pjump** or **Pjump3** elements to connect nodes when a direct connection is not possible. While EMTP uses these elements to connect nodes without adding impedance, HYPERSIM does not include such connection elements in the network admittance matrix. As a result, HYPERSIM may automatically merge connected nodes, which can lead to inconsistencies or errors depending on the circuit configuration, especially in the presence of subsystems.

Avoid relying on pure connection elements when possible:

* Simplify the circuit by removing unnecessary connectors
* Verify that automatic node merging does not alter the intended topology
* Adjust the model structure if inconsistencies or errors occur
  {% endstep %}

{% step %}

## Use impedance-based connectors when required

Check if node connections require preserving electrical behavior beyond simple connectivity. While EMTP provides impedance-type connectors (e.g., Pjump3L), HYPERSIM includes these elements in the network equations to maintain equivalence.

Use impedance-based connectors only when necessary:

* Use inductive or impedance-type connectors to preserve circuit behavior when required
* Avoid overuse, as these elements:
  * Add nodes to the admittance matrix
  * Increase computational complexity and affect performance
    {% 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-node-connector-usage.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.
