> 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/model-and-simulation/power-systems-with-artemis/model-optimization/run-ssn-on-multi-cores.md).

# Run SSN on Multi-Cores

The primary purpose of using decoupling ARTEMiS blocks is to enable real-time simulation of larger systems with more switching elements. Unlike the ARTEMiS DPL or StubLine, the SSN NIB block does not introduce any artificial delay, which allows for more precise computation. However, this lack of delay also prevents full parallelization across multiple subsystems.

To leverage multiple cores with SSN NIBs, a different technic is used: assign additional cores to a single computation subsystem in **RT-LAB**. This allows the solver to distribute the workload internally, improving simulation performance while maintaining accuracy.

{% stepper %}
{% step %}

### Open the model in RT-LAB

In the **Project Explorer**, double-click your model. Ensure the model has been compiled; if not, compile it first.
{% endstep %}

{% step %}

### Enable advanced assignations

Navigate to the **Assignation** tab and click **Advanced** to display the **Cores** column.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-f839b8491b5d3e72fa58993a6d6db9ef137a9fbe%2Fartemis-enable-advanced-assign.png?alt=media" alt="" width="533"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Increase the allocated cores

In the **Cores** column, click the ellipsis (**...**) and set the **Total Number of Allocates Cores** to 2 or more, depending on your available cores and desired performance.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-9f474fc667c1d7e7984ffb621308db81c5a944bb%2Fartemis-increase-allocated-cores.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="danger" %}
Your simulator license must include enough cores to assign multiple cores to a single computation subsystem. To verify availability, [check the value of *ARTEMIS\_NUM\_CORES* in your license](https://www.opal-rt.com/docs/rt-lab/licensing-reference/simulator-license.md).
{% endhint %}
{% endstep %}

{% step %}

### Load and execute a model

Although state-space matrices are precomputed before real-time execution, **the nodal matrix is still solved at the second stage of each time step on a single core**. As a result, using a small number of cores often yields better performance than attempting to parallelize across many. It is generally recommended to test configurations using one, two, or three cores to identify the optimal setup.
{% endstep %}
{% endstepper %}


---

# 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/model-and-simulation/power-systems-with-artemis/model-optimization/run-ssn-on-multi-cores.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.
