> 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/ehs/model-in-schematic-editor/optimize-the-ehs-circuit/improve-performance-with-hscs/configure-hscs-iterations.md).

# Configure HSCS Iterations

## Overview

The **Number of Iterations** parameter specifies how many additional solver iterations are performed during each HSCS time step to determine switch and diode conduction states.

The total number of iterations equals: 1 + Number of Iterations

The default **Number of Iterations** value is `0`, so the total number of iterations is one.

## When additional iterations are not required

The default setting is typically sufficient for:

* Half Bridge Converter
* 3-Level NPC Arm
* 3-Level ANPC Arm
* 3-Level T-Type Arm

These blocks are optimized for accurate operation without additional iterations.

## When additional iterations can help

Additional iterations may improve accuracy for:

* Multilevel converters built from individual switching elements
* Circuits containing many diodes
* Weak DC-link applications
* Phase-shifted full-bridge converters

Additional iterations provide better resolution of switching-state transitions within a time step.

Increasing the number of iterations:

✅ Improves switching-state accuracy

❌ Increases the minimum achievable HSCS time step

Use additional iterations only when they provide a measurable improvement in model behavior.

## Recommendations

* Start with **0 iterations**
* Increase only when diode conduction behavior appears inaccurate
* Recheck the achievable time step after changing the iteration count


---

# 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/ehs/model-in-schematic-editor/optimize-the-ehs-circuit/improve-performance-with-hscs/configure-hscs-iterations.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.
