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

# Import from EMTP

## Overview

The **EMTP import workflow** allows users to use EMTP network models directly in HYPERSIM for offline or real‑time simulation.

Since EMTP and HYPERSIM share the same user interface and network data format (`*.ecf`), EMTP circuits can be opened and executed in HYPERSIM without file conversion. This capability enables users to reuse existing EMTP models within HYPERSIM while applying targeted adjustments to account for differences in supported components, numerical solvers, and real‑time constraints.

## Typical workflow

Using an EMTP model in HYPERSIM generally follows these steps:

1. Prepare the EMTP model for HYPERSIM.
2. Open the EMTP model (`*.ecf`) directly in HYPERSIM.
3. Initialize the model (e.g., load flow or control preparation, when required).
4. Run the simulation in HYPERSIM.

Detailed procedures for each step are provided in the corresponding sections of this guide.

## Key capabilities

Using the EMTP import workflow, users can:

* Reuse EMTP network models directly in HYPERSIM
* Execute EMTP‑based EMT simulations in offline or real‑time environments

## When to use the EMTP import workflow

The EMTP import workflow is particularly well suited for:

* Reusing existing EMTP EMT models in HYPERSIM
* Running EMTP models on real‑time simulation platforms
* Validating EMT behavior under fast transients and switching events


---

# 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.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.
