> 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/hypersim/library-blocks-reference/network-tools/half-line.md).

# Half Line

## Description

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-577edcd1e6b10b29d38909b1f9b85d36e3c470fe%2Fimage%20(456).png?alt=media" alt="" width="232"><figcaption></figcaption></figure>

The **Half Line** block, located in the **Network Tools** library, decouples two discretized systems using an inductor. Its equations are similar to a PI-line section, where the shunt capacitance is determined by the discretization sampling time and the inductor value. When the sampling time is very small and the inductor is large, the introduced parasitic capacitance can be neglected.

$$
C\_{parasitic}=\frac{Ts^2}{L}
$$

Two Half Line components must be connected through transceiver elements (or real-time simulator I/O) to represent a stubline. Parameters must be identical in both components. The “round trip latency” is the number of sampling periods required for a signal to travel to the other Half Line and return.

## Mask parameters

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-63a18215e58b8581aa3dc1066db25c4fa789bf78%2Fimage%20(457).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

<table><thead><tr><th width="239.5999755859375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Half line model</strong></td><td>Select the mode: “Use inductance only” (series inductance branch) or “Use capacitance only” (shunt capacitance branch).</td></tr><tr><td><strong>Inductance</strong></td><td>Total inductance of the stubline (mH) (edit when “Use inductance only”).</td></tr><tr><td><strong>Capacitance</strong></td><td>Total capacitance of the stubline (F) (edit when “Use capacitance only”).</td></tr><tr><td><strong>Round trip latency</strong></td><td>Time for a signal to travel from one Half Line to the other and return (µs).</td></tr></tbody></table>

## Conservating ports

<table><thead><tr><th width="239.5999755859375">Port</th><th>Description</th></tr></thead><tbody><tr><td><strong>P</strong></td><td>Network connection of the positive terminal</td></tr><tr><td><strong>N</strong></td><td>Network connection of the <strong>negative</strong> terminal.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="239.5999755859375">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>In</strong></td><td>Current injection signal received from another Half Line (A)</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="239.5999755859375">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Out</strong></td><td>Current injection signal sent to another Half Line (A)</td></tr></tbody></table>


---

# 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/hypersim/library-blocks-reference/network-tools/half-line.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.
