> 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-stubline.md).

# Stubline

## Description

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

The **ARTEMiS Stubline** block, located in the **ARTEMiS** library, implements an N‑phase distributed-parameter transmission line with exactly one time‑step propagation delay, optimized for real‑time simulation. It decouples the state‑space equations of the networks on both sides of the line.

ARTEMiS line blocks (Distributed Parameters Lines and Stublines) decouple the electric circuit into smaller subnetworks. ARTEMiS caches state‑space matrices for selected topologies and reuses them to avoid recomputation on switching events. Using line‑based decoupling reduces matrix size and the number of required topologies, improving real‑time performance in circuits with many switching elements.

The model is based on Bergeron’s travelling‑wave method used by EMTP. It is similar to the SPS Distributed Parameters Line block, but optimized for discrete real‑time simulation and designed to support network decoupling and multi‑CPU simulation on an RT‑LAB simulator.

Refer to the SPS Distributed Parameter Line block Reference page for more details on the mathematical model of the distributed‑parameter line.

{% hint style="info" %}
**Guidelines for Stubline Blocks in Simulink Models**

Place ARTEMiS Stubline blocks at the top level of the RT‑LAB‑compatible Simulink model.

Each ARTEMiS Stubline output can connect only to Simscape Electrical Specialized Power Systems (SPS) components located inside an RT‑LAB top‑level subsystem (names beginning with ‘SS’ or ‘SM’).

Do not connect Stublines together at the top level. If a connection is required (for example, a star‑connection neutral), route each Stubline inside the appropriate subsystem and perform the connection there.

RT‑LAB OpComm supports basic Simulink signals and cannot transmit physical modeling signals. The ARTEMiS Distributed Parameters Line and ARTEMiS Stubline blocks are exceptions: you can place them at the root of the model and connect their physical modeling ports directly to real‑time subsystems. Physical modeling signals and ports connected to these blocks do not need to pass through the OpComm block.
{% 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-3edf5c492ea5cce37aa668e234fba9603e165a16%2FArtemis_stubline_mask.png?alt=media" alt="" width="392"><figcaption></figcaption></figure>

<table data-search="false"><thead><tr><th width="250">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Number of phases N</strong></td><td>Specifies the number of phases, N. The block updates the number of inputs and outputs when you apply parameters or close the dialog. Available options are 1 to 6 and ‘2 (differential input)’. The ‘differential input’ option is useful when the Stubline is not referenced to ground, such as in Stubline transformer applications.</td></tr><tr><td><strong>Per-Unit value specification</strong></td><td>Specifies whether resistance and inductance are entered in per‑unit.</td></tr><tr><td><strong>Inductance (H)</strong></td><td>Total inductance, in Henry (H) or pu.</td></tr><tr><td><strong>Resistance (Ohms)</strong></td><td>Total resistance, in ohms or pu.</td></tr><tr><td><strong>Sample Time</strong></td><td>Block sample time, in seconds.</td></tr><tr><td><strong>Nominal power (VA)</strong></td><td>Nominal power base (for per‑unit values only).</td></tr><tr><td><strong>Nominal voltage(V)</strong></td><td>Nominal voltage base (for per‑unit values only).</td></tr><tr><td><strong>Nominal frequency (Hz)</strong></td><td>Nominal frequency base (for per‑unit values only).</td></tr></tbody></table>

{% hint style="danger" %}
RT‑LAB supports distributing complex models across a cluster of simulator nodes using low‑latency interconnects. Directly partitioning electrical circuits can degrade dynamics due to communication delays. ARTEMiS lines exploit their intrinsic propagation delay to split circuits without altering dynamic behavior.
{% endhint %}

## Conserving ports

<table><thead><tr><th width="250.79998779296875">port</th><th>Description</th></tr></thead><tbody><tr><td><strong>N‑phase physical connection</strong></td><td>Voltage–current physical domain connection.</td></tr></tbody></table>

## Inputs

This block has no inputs.

## Outputs

This block has no outputs.

## Characteristics and limitations

| Characteristic              | Value                                                                                                       |
| --------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Steady‑state initialization | No. The block does not initialize in steady state; initial transients may occur at the start of simulation. |
| Direct Feedthrough          | No                                                                                                          |
| Discrete Sample Time        | Yes                                                                                                         |
| XHP Support                 | Yes                                                                                                         |
| Work Offline                | Yes                                                                                                         |


---

# 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-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.
