> 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/example-models/ephasorsim-example-models/2000-bus-synthetic-grid-on-footprint-of-texas.md).

# 2000-Bus Synthetic Grid on Footprint of Texas

## Description

The **2000-Bus Synthetic Grid on Footprint of Texas** example can be created by starting a new RT‑LAB project. From the menu bar, select **File > New > RT‑LAB Project**. Enter a name and location for your project, then click **Next**. From the available templates list, navigate to **ePHASORsim** and select **phasor20\_TEXAS**, then click **Finish**.

This demo shows transient stability simulation of a synthetic 2000-bus grid that built on the footprint of Texas \[1]. The following modifications are made to the original data provided in \[2]:

1. All renewable energy generators in the original \*.raw file that have no corresponding dynamic data in \*.dyr are represented as classical generators (GENCLS).
2. All the loads are converted to constant impedance type, assuming 1 p.u. voltage.
3. Parameters of some components in the \*.dyr file are modified to resolve initialization issues and also to stabilized the system with time-step of 10 ms.

The modified files are named phasor20\_TEXAS.raw and phasor20\_TEXAS.dyr and they exist in the model folder.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-642295a1e11f7c67d51835dd89f1527180a61f58%2Fphasor20_TEXAS_page-0001.jpg?alt=media" alt=""><figcaption><p>The diagram of the network is visualized by GEPHI [2].</p></figcaption></figure>

{% hint style="info" %}
To improve the performance this model is configured to run on two cores (2 and 3) on a target. The `EPHASOR_THREADS` environment variable can be revised in the Variables tab of RT-LAB GUI to modify this configuration. By doing so, due to synchronization mechanisms used during parallel computation, it is advised to disable XHP to avoid isolation loss events.
{% endhint %}

## Requirements

* MATLAB R2019b and later

## Simulation and results

The simulation of 2000-bus system starts from steady state. At t=1s, one of the lines connecting the buses 1079 and 3048 is tripped. This is then followed by consecutive tripping of two large generators located at bus-7098 ('WADSWORTH 3') and bus-5262 ('GLEN ROSE \~3') at t=10s and t=20s, respectively. The machine at bus-7099 is picked to be the reference for measuring the relative rotor angle.

A few signals from the simulation results for two generators at bus-1033 ('MCCAMEY 1 1') and bus-2057 ('WICHITA FA\~4') are demonstrated here.

Figure (a) shows the terminal voltage magnitude (p.u.) of the two generators, Figure (b) shows relative rotor angle (degree) of the two generators with respect to the reference, and Figure (c) depicts the frequency (Hz) oscillations of generator buses.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-eff8b90b6b2764ca6f798bfe2bcb5fc23b093b51%2Fphasor20_TEXAS_1.png?alt=media" alt=""><figcaption><p>Simulation results for generators 'MCCAMEY 1 1' and 'WICHITA FA~4'. (a) Terminal voltage (p.u.) (b) Relative rotor angle (deg.) (c) Frequency (Hz)</p></figcaption></figure>

The in-port and out-port configurations are given in **phasor20\_TEXAS.xlsx** file.

{% file src="/files/s9FylGEg3itFxJFsi8lI" %}

In the "Pins" page of the Excel file the following outgoing and incoming pins are assigned:

<details>

<summary>Outgoing pins (measurements)</summary>

* Vmag: Bus voltage magnitude (p.u.)
* Vang: Bus voltage angle (degrees)
* ANGLE: Rotor angle (rad)
* SLIP: Synchronous machine frequency deviation (p.u.)
* EFD: Synchronous machine field voltage (p.u.)

</details>

<details>

<summary>Incoming pin (control command)</summary>

* Trip generator: Command to trip the generator
* Trip line: Command to trip the line

</details>

## References

\[1] A. B. Birchfield; T. Xu; K. M. Gegner; K. S. Shetye; T. J. Overbye, "Grid Structural Characteristics as Validation Criteria for Synthetic Networks," in IEEE Transactions on Power Systems, vol. 32, no. 4, pp. 3258-3265, July 2017.

\[2] [Electric Grid Test Case Repository](https://electricgrids.engr.tamu.edu/).

\[3] <https://gephi.org/>


---

# 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/example-models/ephasorsim-example-models/2000-bus-synthetic-grid-on-footprint-of-texas.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.
