> 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/rt-lab/simulink-blocks-reference/artemis-library/artemis-guide.md).

# ARTEMiS Guide

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-bc31f174ea05b62e4b76d64adcc4c66acfc81982%2FArtemis_giuide_block.png?alt=media" alt="" width="131"><figcaption></figcaption></figure>

The **ARTEMiS Guide** block, located in the **ARTEMiS** library, sets and controls general ARTEMiS and SSN simulation parameters and options.

{% hint style="info" %}
The SSN solver is used even if the model has no nodes (Nodal Interface Blocks or NIB).
{% endhint %}

{% hint style="danger" %}
This block requires a valid RT-LAB license on the simulator with the feature ARTEMiS enabled. Refer to [ARTEMiS Requirements](https://www.opal-rt.com/docs/rt-lab/model-and-simulation/power-systems-with-artemis/artemis-requirements.md) for details.
{% endhint %}

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-62f56a6ab263cda601db5e0bfbc3e945a927eaba%2FArtemis_guide_mask.png?alt=media" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="General" %}

<table><thead><tr><th width="250.39996337890625">Parameter</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Sample Time (s)</strong></td><td>Discretization sample time in seconds for ARTEMiS and SSN solvers.</td></tr><tr><td><strong>Enable State-Space-Nodal method (SSN)</strong></td><td>Select to use SSN solvers and methods. When cleared, the legacy state-space ARTEMiS solver is used. These legacy solvers (non-SSN) will be obsoleted in future versions. The SSN solver is used even if the model has no nodes (Nodal Interface Blocks or NIB).</td></tr></tbody></table>
{% endtab %}

{% tab title="SSN Options" %}

<table><thead><tr><th width="250.4000244140625">Parameter</th><th>Definition</th></tr></thead><tbody><tr><td><strong>SSN solver</strong></td><td><p>Discretization method of the SSN algorithm. Applies only to the main SSN network; UCB blocks have their own local discretization.<br>Available solvers are:</p><ul><li>Backward Euler: most stable solver of all, L-stable, order 1 (less precise than Trapezoidal)</li><li>Trapezoidal: classic trapezoidal (A-stable, order 2), prone to oscillations</li><li>Art5: order 5 L-stable solver with linear interpolation of the nodal interface voltage between the previous solution voltage and the current voltage solution.</li><li>Art5 with Backward-Euler Nodal Interface: same as Art5 but with fully implicit voltage solution. Often more stable than Art5 solver.</li><li>Art5 with balanced zero order hold Nodal Interface: same as Art5 but consider the nodal voltage solution as 2 half-steps (between previous step and current step) of constant value during nodal solution. Provided for challenging cases where other solvers would fail.</li></ul></td></tr><tr><td><strong>Iterations</strong></td><td><p>Selection of iteration type:</p><ul><li>iSWITCH and iMOV only (default): only the iSWITCH and iMOV are iterated; regular SSN groups are not. Faster option.</li><li>iSWITCH, iMOV and SSN group internal group iterations: SSN groups iterate internally without global admittance matrix refactorization, which can increase accuracy while limiting computation cost.</li><li>Global Iterations (slower): the complete SSN solution, including the global admittance matrix solution, is iterated when required. Note that UCB blocks do not iterate.</li></ul></td></tr><tr><td><strong>Maximum number of iterations</strong></td><td>Maximum number of iterations for all iteration options.</td></tr><tr><td><strong>Nodal factorization type</strong></td><td><p>Factorization method for the SSN nodal admittance matrix:</p><ul><li>LU (more robust): standard LU factorization.</li><li>LDL (quicker): uses matrix symmetry often found in power system models. Cannot be used with most SSN machine models because they do not produce a symmetric admittance matrix. Slightly more numerically sensitive than LU; some models may produce slightly unsymmetrical admittance due to numerical round-off errors.</li></ul></td></tr><tr><td><strong>Enable SSN node type verification</strong></td><td>AI subroutine that analyzes the V-type or I-type selection in the model and provides suggestions.</td></tr></tbody></table>

{% hint style="danger" %}
**LDL cannot be used with most SSN machine models** and is more numerically sensitive than LU when symmetry is not strictly satisfied.
{% endhint %}
{% endtab %}

{% tab title="Advanced" %}

<table><thead><tr><th width="250.39996337890625">Parameter</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Extinction angle computation (individual thyristor only)</strong></td><td>Modifies the outputs of individual thyristor blocks to provide the extinction delay from the last time step when the thyristor opens.</td></tr><tr><td><strong>Use ARTEMiS transformer saturation method</strong></td><td>Substitutes the standard SPS transformer saturation method with the ARTEMiS method, which uses core flux as a state variable to compute saturation accurately without an algebraic loop.</td></tr><tr><td><strong>Distributed Parameter Line model type</strong></td><td>Selects between ARTEMiS DPL (default) and SPS DPL models. Only the SPS DPL can be used for load-flow calculations.<br><strong>ARTEMiS DPL</strong> models are required to parallelize the simulation of subnetworks separated by DPLs in RT-LAB.<br><strong>SPS DPL</strong> use regular SimPowerSystems line models.</td></tr><tr><td><strong>SSN initial conditions</strong></td><td>Set the SSN initial conditions to either:<br><strong>Block</strong>: all states are set to zero except the ones directly set in the SPs blocks.<br><strong>Steady-state with block override</strong>: all states are set to start in steady-state conditions except if set directly in the SPS blocks.<br><strong>All zeros</strong>: all states are set to 0, without exceptions.</td></tr></tbody></table>

{% hint style="info" %}
The steady-state initialization is limited to topologically connected electric elements and does not support machines yet. For instance, if 2 subsystems are connected with an ARTEMiS PLD line, the steady-state initialization will be done separately for each subsystem at each end of the line.
{% endhint %}
{% endtab %}
{% endtabs %}

## Inputs

This block has no inputs.

## Outputs

This block has no outputs.

## Characteristics and limitations

| Item                   | Description                                                                                                     |
| ---------------------- | --------------------------------------------------------------------------------------------------------------- |
| Discretization scope   | SSN solver discretization applies only to the main SSN network; UCB blocks have their own local discretization. |
| Iteration limitation   | UCB blocks do not iterate under Global Iterations.                                                              |
| Extinction angle scope | Extinction angle computation applies to individual thyristor blocks only.                                       |


---

# 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/rt-lab/simulink-blocks-reference/artemis-library/artemis-guide.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.
