> 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-events-library/rte-remove.md).

# RTE Remove

## Description

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

The **RTE Remove** block, located in the **RT-EVENTS Math operations** library, removes N pulses from an RTE Boolean signal. The deletion repeats every cycle of M pulses.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-aa893b67a091693981020296b6497a6e925f9dbe%2FRTE_remove_curve.png?alt=media" alt=""><figcaption><p>Example with N=2 and M=4</p></figcaption></figure>

The block counts pulses each time an edge of the selected type occurs. With a rising trigger, it removes high pulses from the input; with a falling trigger, it removes low pulses.

The Offset parameter specifies the number of pulses from the beginning of the cycle at which pulse removal starts.

An external reset can restart the cycle. Each time the specified edge occurs on the External Reset signal, the internal counter that defines the beginning of a cycle resets to zero. The reset can be performed on the rising edge, falling edge, or either.

## Mask parameters

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

<table><thead><tr><th width="250.800048828125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Trigger type</strong></td><td>Determines the edge type used to count pulses</td></tr><tr><td><strong>Number of pulses to remove</strong></td><td>Number of pulses to remove at each cycle</td></tr><tr><td><strong>Number of pulses by cycle</strong></td><td>Number of pulses that define a complete cycle</td></tr><tr><td><strong>Offset</strong></td><td>Relative offset, in pulses from the start of the cycle, where pulses are removed</td></tr><tr><td><strong>External Reset</strong></td><td>Edge type used to reset the cycle</td></tr><tr><td><strong>Maximum Number of events</strong></td><td>Maximum number of events (transitions) allowed during a single step; events beyond this number are skipped</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="250">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Inputs (RTE Boolean)</strong></td><td>RTE Boolean signal (pulse waveform) to modify</td></tr><tr><td><strong>External Reset (Double)</strong></td><td>Signal used to reset the cycle</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="250">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Output (RTE Boolean)</strong></td><td>Modified RTE Boolean signal</td></tr></tbody></table>

## Characteristics and limitations

| Characteristic     | Value                        |
| ------------------ | ---------------------------- |
| Direct Feedthrough | Yes                          |
| Sample time        | Inherited and fixed discrete |
| Work offline       | Yes                          |
| Dimensionalized    | 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/rt-events-library/rte-remove.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.
