> 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/decouple-model-topology-with-artemis-stubline.md).

# Decouple Model Topology with ARTEMiS Stubline

When transmission lines in a model are too short to introduce a sufficient natural propagation delay, they cannot be used for decoupling. In such cases, other methods such as SSN Nodal Interface Blocks (NIBs) or ARTEMiS Stublines can be applied.

The **ARTEMiS Stubline** block implements an *N-phase distributed parameter line model* with an **exactly one-time-step propagation delay**. This behavior allows the Stubline to be used between **computation subsystems**, just like the ARTEMiS DPL, effectively decoupling large systems and enabling parallel execution on multiple cores.

However, unlike the DPL, the ARTEMiS Stubline’s internal physical model introduces a **parasitic capacitance** that can affect simulation accuracy. It is therefore recommended to compare simulation results before and after introducing Stublines to ensure that results remain acceptable for the intended use case. **Use Stublines when computational performance is a priority**. If accuracy is critical and sufficient delay cannot be introduced, **SSN NIBs** are typically a better alternative.

## Use ARTEMiS Stubline to decouple large electrical systems

{% stepper %}
{% step %}

### Add ARTEMiS Stubline

Open the Simulink **Library Browser**, navigate to **Artemis > ARTEMIS**, and drag the **StubLine** block into the model.
{% endstep %}

{% step %}

### Leverage multiple ARTEMiS cores

Subcircuits can be assigned to separate computation subsystems to take advantage of parallel computation on multiple cores. The **ARTEMiS StubLine** is one of the few blocks that can be placed **outside a computation subsystems**.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-8e2c3696e2401efae8bebf310e8012cd35fa8b14%2Fartemis-stubline-multiple-cores-param.png?alt=media" alt="" width="455"><figcaption></figcaption></figure>

1. Select all blocks located on one side of the ARTEMiS Stubline and press **Ctrl-G** to create a new subsystem. Follow RT-LAB naming conventions: one subsystem must be named sm\_\<descriptive\_name>.
2. Select all blocks located on the other side of the ARTEMiS Stubline and press **Ctrl-G** to create a second subsystem. Name it according to RT-LAB naming conventions: ss\_\<descriptive\_name>.
3. Add **OpComm** blocks to **each** subsystem, leaving them **unconnected**. Set the **Number of Inports** to **0**, since electrical data-type signals do not need to be connected to OpComm blocks. Only double-type signals can be connected to OpComm blocks.

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

{% hint style="danger" %}
Your simulator license must include one core for each 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 %}
{% 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/decouple-model-topology-with-artemis-stubline.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.
