> 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/smart-power-simulation-software-sps/overview/acknowledgments.md).

# Acknowledgments

SPS Software™, Simscape™ Electrical™ Specialized Power Systems, Simscape Power Systems™ Specialized Technology, and SimPowerSystems™ First Generation were developed by the following people and organizations.

**Gilbert Sybille**\
Hydro-Québec Research Institute (IREQ), Varennes, Québec. Original author of SPS software, technical coordinator, author of phasor simulation, discretization techniques, and documentation. Technical supervision and design of the FACTS and Renewable Energy libraries, and documentation.

**Louis-A. Dessaint**\
École de Technologie Supérieure (ETS), Montréal, Québec. Author of machine models. Technical supervision and design of the electric drive library contents and documentation.

**Bruno DeKelper**\
École de Technologie Supérieure (ETS), Montréal, Québec. Author of TLC functions associated with the simulation of the state space equations.

**Olivier Tremblay, Jean-Roch Cossa**\
École de Technologie Supérieure (ETS), Montréal, Québec. Validations and tests.

**Patrice Brunelle**\
Hydro-Québec Research Institute (IREQ), Varennes, Québec. Main software engineer. Author of graphical user interfaces, model integration into Simulink® and Physical Modeling, and documentation.

**Roger Champagne**\
École de Technologie Supérieure (ETS), Montréal, Québec. Author of machine models, of revised state space formulation.

**Pierre Giroux, Richard Gagnon, Silvano Casoria**\
Hydro-Québec Research Institute (IREQ), Varennes, Québec. Development of the FACTS and Renewable Energy libraries. Key beta testers and developers of several SPS blocks, demos, and documentation.

**Hoang Lehuy**\
Université Laval, Québec City. Validation tests and author of several models, functions, and documentation. Validation of the electric drives models.

**Handy Fortin-Blanchette, Olivier Tremblay, Christophe Semaille**\
École de Technologie Supérieure (ETS), Montréal, Québec. Development of the AC and DC drives models.

**Hassan Ouquelle, Jean-Nicolas Paquin**\
École de Technologie Supérieure (ETS), Montréal, Québec. Development of the Single-Phase Asynchronous Machine model and Saturation in Asynchronous Machine model.

**Pierre Mercier**\
iOMEGAt. Project manager for the Power System Blockset™ software versions 1 and 2 and for the Simulink electric drives library.

The authors acknowledge the contributions of the following people:

*Innocent Kamwa, Raymond Roussel, Kamal Al-Haddad, Mohamed Tou, Christian Dufour, Momcilo Gavrilovic, Christian Larose, David McCallum, Bahram Khodabakhchian, Manuel Alvarado Sandoval, and Stéphane Desjardins*


---

# 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/smart-power-simulation-software-sps/overview/acknowledgments.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.
