> 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/rt-lab-library/opsignalcompression.md).

# OpSignalCompression

## Description

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

The **OpSignalCompression** block, located in the **RT-LAB/Miscellaneous** library, compresses one or more input signals into a double vector output. Inputs can be real or complex signals or vectors of any type. Use the OpSignalCompression and OpSignalUncompression blocks together to minimize the number of signals transferred between two systems.

## Mask parameters

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

<table><thead><tr><th width="220.99993896484375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Tag</strong></td><td>Identifier used by the corresponding OpSignalUncompression block.</td></tr><tr><td><strong>Number of inputs</strong></td><td>Number of inputs.</td></tr><tr><td><strong>Number of outputs</strong></td><td>Number of outputs required to compress the input signals.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="218.5999755859375">Input</th><th>Descrption</th></tr></thead><tbody><tr><td><strong>Input(s)</strong></td><td>Signal(s) to compress.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="221">Output</th><th>Descrption</th></tr></thead><tbody><tr><td><strong>Compressed signal</strong></td><td>Compressed double vector. This signal cannot be read by other Simulink blocks and must be connected to an OpSignalUncompression block with the same Tag.</td></tr></tbody></table>

## Characteristics and limitations

<table><thead><tr><th width="220.20001220703125">Characteristic</th><th>Value</th></tr></thead><tbody><tr><td>Direct Feedthrough</td><td>Yes</td></tr><tr><td>Discrete sample time</td><td>Yes</td></tr><tr><td>XHP support</td><td>Yes</td></tr><tr><td>Work offline</td><td>Yes</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/rt-lab/simulink-blocks-reference/rt-lab-library/opsignalcompression.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.
