> 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/power-systems-with-artemis/performance-benchmarks/ghost-microgrid-with-protection.md).

# GHOST Microgrid with Protection

<table><thead><tr><th width="241.27276611328125">Model name</th><th>GHOST microgrid with protection</th></tr></thead><tbody><tr><td><strong>Highlights</strong></td><td><ul><li>Includes all protection models: 25, 27, 50P, 51P, 59, 81O, 81R and 81U</li><li>Multi-relay component optimizing performance and facilitating protection configuration</li></ul><p>Known distributed energy resources benchmark originally published by the MIT and NREL. Few alterations were made to remove the need for an external controller for the purpose of this benchmark.</p></td></tr><tr><td><strong>Model diagram</strong></td><td><img src="https://opal-rt.atlassian.net/wiki/download/thumbnails/496730279/Ghost_complete_top_level.PNG?version=1&#x26;modificationDate=1702321712057&#x26;cacheVersion=1&#x26;api=v2&#x26;width=228&#x26;height=250" alt=""></td></tr><tr><td><strong>Single-phase nodes</strong></td><td>1277</td></tr><tr><td><strong>States (L, C, ...)</strong></td><td>402</td></tr><tr><td><strong>Sources (3φ)</strong></td><td>1</td></tr><tr><td><strong>PV plants</strong></td><td>2</td></tr><tr><td><strong>BESS</strong></td><td>2</td></tr><tr><td><strong>CHP</strong></td><td>1</td></tr><tr><td><strong>Transformers (3φ)</strong></td><td>27</td></tr><tr><td><strong>Distributed parameter lines</strong></td><td>20</td></tr><tr><td><strong>Lines (coupled RL)</strong></td><td>41</td></tr><tr><td><strong>Induction motors</strong></td><td>2</td></tr><tr><td><strong>Loads (3φ)</strong></td><td>39</td></tr><tr><td><strong>Breakers (3φ)</strong></td><td>63</td></tr><tr><td><strong>Hardware</strong></td><td><p><strong>OP5707XG</strong></p><ul><li><strong>Motherboard:</strong> X11DPL-i</li><li><strong>Processor:</strong> Intel(R) Xeon(R) Gold 5222 CPU @ 3.80GHz; 8 cores</li><li><strong>RAM:</strong> 32 GB</li></ul></td></tr><tr><td><strong>Software</strong></td><td><ul><li><strong>Platform:</strong> RT-LAB</li><li><strong>Compiler:</strong> Intel 2019 (19.03.199)</li></ul></td></tr><tr><td><strong>Minimum license required</strong></td><td>FXG Max (6 cores)</td></tr><tr><td><strong>Results</strong></td><td><ul><li><strong>Number of core(s):</strong> 6</li><li><strong>Minimum time-step:</strong> 73 us *</li></ul><p>* Performance under transient conditions varying considerably depending on the study type, this benchmark measures the minimum achievable time-step without overruns in steady-state conditions. A rule of thumb is to consider 10 to 20 % buffer time for calculations under transient conditions.</p></td></tr></tbody></table>


---

# 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/power-systems-with-artemis/performance-benchmarks/ghost-microgrid-with-protection.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.
