> 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/define-the-solver-settings/how-to-choose-solver-strategy-smallest-time-step-vs-lowest-latency.md).

# eHS Solver Strategies

## Overview

In eHS Gen 5 (State Space Analysis Method), switches introduced a **delay in order to support interpolation**. There can be one or two delays introduced depending on the solver strategy adopted. Furthermore, to mitigate this latency, a prediction is made on the measurements needed to compute the switches. Coupling of the switches model is done through voltage, and current injection, therefore depending on the stiffness of the circuit, a relaxation need to be applied to the injection to ensure model stability.

{% hint style="danger" %}
Both **High Performance** modes require a simulator license that includes the **EHS\_HIGH\_PERFORMANCE\_TOKEN** feature with a sufficient number of tokens.
{% endhint %}

## High Performance – Lowest Latency (Recommended) <a href="#lowest-latency-recommended-default" id="lowest-latency-recommended-default"></a>

Optimizes the solver to minimize **interaction latency** with other system components. This mode introduces a single delay in switch computation, where the state-space equations and switching elements are solved sequentially. It provides stable and efficient performance for a wide range of circuit topologies.

The time step is constrained only by a **lower bound**, with no upper limit. This relaxes time step constraints and improves compatibility with components that impose their own timing requirements (e.g., machine models).

As a result, this mode is generally the most robust and widely applicable, particularly for complex systems or mixed-component simulations.

## High Performance – Smallest Time Step

Optimizes the solver to use the **smallest achievable time step**. This mode improves accuracy for high-frequency and resonant circuits by enabling more precise detection of current zero-crossings compared to the *Lowest Latency* option.

As a trade-off, this mode introduces additional delays in switch computation and constrains the time step within a limited range (minimum and maximum values). This may restrict compatibility with other components that impose time step constraints (e.g., machine models).

In some cases, certain circuit topologies may not support this mode. When this occurs, the following error is generated at load time:

**Error (145):** The Solver Strategy *"Smallest Time Step"* cannot be applied to this circuit. Using the *"Lowest Latency"* strategy in the Schematic Editor resolves this limitation but may increase the circuit time step.

In such cases, use the **Lowest Latency** option instead.


---

# 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/define-the-solver-settings/how-to-choose-solver-strategy-smallest-time-step-vs-lowest-latency.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.
