> 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/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/use-a-cyme-model/import-the-cyme-model.md).

# Import the CYME Model

{% stepper %}
{% step %}

### Open the ePHASORSIM Solver block mask

Double-click the **ePHASORSIM Solver** block to open its mask.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-bb975d1dcd879640cf609db9785186ba741428a2%2Feph-rtlab-CYME-mask.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Browse to the SXST file

1. Navigate to the **Network data** tab.
2. From the **Input file format** drop-down menu, select **CYME**.
3. Under **SXST file**, click **Select** and choose the model's **SXST** file. To view or edit the contents of the selected file, click **Open**.
   {% endstep %}

{% step %}

### (Optional) Import power-flow data

If a CYME power-flow solution is available, it can be used to initialize the network operating point. Under **Power-flow report**, click **Select** and choose the load-flow results file exported from CYME (`.xls`). To view or edit the contents of the selected file, click **Open**.
{% endstep %}

{% step %}

### Apply changes

Click **Apply**. The CYME network data is now imported. Follow the next steps to complete the block configuration.
{% 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/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/use-a-cyme-model/import-the-cyme-model.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.
