> 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-lines.md).

# Adjust Lines

This page provides guidelines to identify and proactively address real-time simulation and task distribution discrepancies between EMTP and HYPERSIM.

## Adjustment procedure

{% stepper %}
{% step %}

## Verify line modeling for real-time simulation

1. Check how transmission lines are modeled in the circuit, especially their type and length. In HYPERSIM, simulation tasks are distributed based on the propagation delay of transmission lines.
   * Distributed parameter lines (CP type) require a minimum physical length to be compatible with the simulation time step. For a 50 μs time step, the minimum length is approximately **15 km**.
   * Lines shorter than this may not be properly handled during task partitioning
2. Use **CP-type lines** only when their length satisfies the minimum requirement For shorter lines, consider alternative modeling approaches that respect real-time constraints. Always ensure consistency between line length and simulation time step.
   {% endstep %}

{% step %}

## Check for mixed PI and CP line configurations

1. Check if **PI lines are used in parallel with CP lines** in the model. In HYPERSIM, PI lines are solved within a **single simulation task**, while CP lines are split across **multiple tasks** (one per end). Combining PI and CP lines in parallel leads to inconsistencies in task distribution. HYPERSIM will report an **error during model analysis**.
2. Replace PI lines with **CP-type lines** when used in parallel configurations. Ensure consistent modeling of parallel branches to avoid task partitioning conflicts.
   {% endstep %}

{% step %}

## Validate propagation speed of transmission line models

1. Check the propagation speed defined in distributed parameter line models. HYPERSIM enforces physical constraints on propagation speed. If a propagation mode exceeds the **speed of light**, a warning is issued during circuit analysis.
2. Ensure all propagation speeds are **physically valid (≤ speed of light)**. Review line parameters and correct any inconsistencies in model definition.
   {% 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-lines.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.
