> 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-probe-events.md).

# RTE Probe Events

## Description

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

The **RTE Probe Events** block, located in the **RT-EVENTS/Signal Attributes** library, outputs event attributes (time, state, initial condition, number of events, and status) from an RTE signal for the last calculation step. It displays the state and time of events that occur within a calculation step. Element indices specify which events to output; the resulting output is a vector whose length ranges from 1 to the maximum number of events contained in the RTE signal.

{% hint style="info" %}
Set Initial condition source to external, an additional input appears.
{% 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-5ee5caf27aea3a98a1c9a8fb28d97345c1d13407%2FRTE_probe_events_mask.png?alt=media" alt="" width="316"><figcaption></figcaption></figure>

<table><thead><tr><th width="279.60003662109375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Input data type</strong></td><td>Specifies if the input is an RTE Boolean or RTE Double signal.</td></tr><tr><td><strong>Source of element indices</strong></td><td>Determines whether the indices of output events are specified on the mask (internal) or provided as input signals (external).</td></tr><tr><td><strong>Element Indices</strong></td><td>Vector of the events to output. Only available when the source of the element is internal.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="280.4000244140625">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Inputs (RTE)</strong></td><td>RTE-type signal to convert into doubles.</td></tr><tr><td><strong>Element Indices (Double)</strong></td><td>Vector of the events to output. Only available when the source of the element is external.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="279.60003662109375">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Time Vector (Double)</strong></td><td>The times of each event relative to the last calculation step. The values of the time vector range from 0 to the mode sample time.</td></tr><tr><td><strong>State Vector(Double)</strong></td><td>The states of each event.</td></tr><tr><td><strong>Initial Condition (Double)</strong></td><td>The initial condition of the RTE signal at the beginning of the last calculation step.</td></tr><tr><td><strong>Number of events (Double)</strong></td><td>The number of events that occurred. This corresponds to the number of elements of the time and state vectors which are not undefined.</td></tr><tr><td><strong>Status (Double)</strong></td><td>The status of the RTE signal. See RT-EVENTS Status</td></tr></tbody></table>

## Characteristics and limitations

| Characteristic     | Value                         |
| ------------------ | ----------------------------- |
| Direct Feedthrough | Yes                           |
| Sample Time        | Inherited and fixed discrete. |
| Work offline       | Yes                           |
| Dimensionalized    | No                            |


---

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