> 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/courseware/electric-courseware/renewable-energy/microgrid-system/references.md).

# References

1. <http://www.opal-rt.com/>
2. Mohammed Atta Abdulgalil, Muhammad Khalid, and Fahad Alismail. “Optimal sizing of battery energy storage for a grid-connected microgrid subjected to wind uncertainties”. In: *Energies* 12.12 (2019), page 2412.
3. Alejandra Tabares, Norberto Martinez, Lucas Ginez, José F Resende, Nierbeth Brito, and John Fredy Franco. “Optimal Capacity Sizing for the Integration of a Battery and Photovoltaic Microgrid to Supply Auxiliary Services in Substations under a Contingency”. In: *Energies* 13.22 (2020), page 6037.
4. M Kesraoui, N Korichi, and A Belkadi. “Maximum power point tracker of wind energy conversion system”. In: *Renewable energy* 36.10 (2011), pages 2655–2662.
5. Ali Reza Reisi, Mohammad Hassan Moradi, and Shahriar Jamasb. “Classification and comparison of maximum power point tracking techniques for photovoltaic system: A review”. In: *Renewable* *and sustainable energy reviews* 19 (2013), pages 433–443.


---

# 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/courseware/electric-courseware/renewable-energy/microgrid-system/references.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.
