> 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/pe-add-on-opal-rt/model-in-schematic-editor/optimize-the-ehs-circuit/improve-performance-with-hscs/select-the-hscs-discretization-method.md).

# Select the HSCS Discretization Method

## Overview

HSCS supports two discretization methods:

* **Backward Euler**
* **PADE5**

The chosen method affects numerical stability and simulation accuracy.

## Backward Euler

**Backward Euler** is the default method and is recommended for most applications.

Advantages:

* Highest numerical robustness
* Better tolerance to difficult topologies
* Better tolerance to aggressive component values

Limitations:

* Introduces additional numerical damping
* May reduce accuracy in highly resonant circuits

## PADE5

**PADE5** is a higher-order discretization method designed to improve the representation of resonant dynamics.

Advantages:

* Reduced numerical damping
* Improved resonant behavior
* Improved accuracy for high-frequency converters

Typical applications:

* LLC converters
* CLLC converters
* Resonant converters operating above 100 kHz

## Recommendations

Use:

* **Backward Euler** for most applications
* **PADE5** when resonant behavior is critical

If numerical instability occurs with PADE5, revert to Backward Euler.


---

# 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/pe-add-on-opal-rt/model-in-schematic-editor/optimize-the-ehs-circuit/improve-performance-with-hscs/select-the-hscs-discretization-method.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.
