> 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/power-electronics/dc-to-ac-converters/introduction.md).

# Introduction

It consists of providing the students with theoretical background and real-time interactive tools to understand two-level inverters, followed by exercises to put the acquired knowledge into practice.\
It is noteworthy that this document is a level-one courseware in which the focus is on (i) the analysis of the circuit and (ii) the open-loop control.\
At the end of this courseware, the student will be capable of:

* Understanding the functionalities of Single-Phase Two-Level and Three-Phase Two-Level inverters.
* Computing the voltage levels at the output of the inverter as functions of input DC voltage.
* Observing the impact of changing PWM frequency and quantifying power losses.
* Observing the impact of changing PWM frequency on total harmonic distortion (THD).
* Understanding the impact of inductive load and capacitive load on currents, voltages; reversing the power flow.
* Understanding the benefits of filtering and its impact on THD at both the source and load sides.


---

# 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/power-electronics/dc-to-ac-converters/introduction.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.
