> 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/overview/navigate-the-rt-lab-environment.md).

# Navigate the RT-LAB Environment

The RT-LAB Workbench is the main user interface for creating, configuring, and executing real-time simulations. It is organized into **perspectives**, **views**, and **editors**, which together provide access to all RT-LAB functionality.

* **Perspectives**: Organize editors and views for a specific task or workflow.
* **Views**: Display information, navigation tools, model properties, compilation results, and monitoring data.
* **Editors**: Configure, edit, and manage models, targets, and project resources.

When RT-LAB starts, it opens a workspace containing the **RT-LAB Edition perspective**. By default, users have access to several key views, including **Project Explorer**, **Compilation**, **Display**, **Properties**, **MATLAB**, **Progress**, and **Console**.

## Wizards

RT-LAB provides a collection of **Wizards** that guide users through common tasks, simplifying the creation and configuration of workspace resources. Wizards help ensure that projects, models, and targets are created with the required settings and structure.

Wizards can be accessed from:

**File > New** or by right-clicking within the **Project Explorer** and selecting **New**.

Common RT-LAB wizards include:

| Wizard             | Purpose                                                          |
| ------------------ | ---------------------------------------------------------------- |
| **Project Wizard** | Create a new RT-LAB project and its initial workspace structure. |
| **Target Wizard**  | Add and configure a new target node for simulation deployment.   |
| **Model Wizard**   | Create a new RT-LAB model and configure its basic properties.    |
| **File Wizard**    | Create new files within a project.                               |

## Model editors

The **Model Editor** is the primary configuration tool for RT-LAB models. To open it, double-click a model in the **Project Explorer**

The editor provides several configuration pages:

| Page                      | Purpose                                                                                        |
| ------------------------- | ---------------------------------------------------------------------------------------------- |
| **Overview**              | Displays model information such as name, location, state, and description.                     |
| **Development**           | Configure target platform, compiler options, source files, libraries, and include paths.       |
| **Execution**             | Define execution settings and control model loading, execution, pausing, and reset operations. |
| **Environment Variables** | Create and manage model-specific environment variables.                                        |
| **Files**                 | Manage additional files associated with the model.                                             |
| **Assignation**           | Assign model subsystems to target nodes and configure execution distribution.                  |

## Target editor

The **Target Editor** is used to configure, monitor, and manage RT-LAB target nodes. It provides a centralized interface for target administration, communication settings, licensing, hardware information, and simulation management.

To open the Target Editor:

* In the **Project Explorer** or **Target Explorer**, double-click a target node.
* Alternatively, right-click a target and select **Open**.

The Target Editor includes several configuration pages:

| Page                     | Purpose                                                                                                                       |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| **Overview**             | Displays general information about the target, including its name, operating system, connection status, and hardware details. |
| **Properties**           | Configure network communication and target-specific settings.                                                                 |
| **License**              | Request, install, and manage RT-LAB licenses on the target.                                                                   |
| **Monitoring**           | View the status and health of the target during operation.                                                                    |
| **Hardware Information** | Access detailed information about the target hardware and installed components.                                               |

## Preferences

The **Preferences** pages in **Window > Preferences** allow users to configure global RT-LAB settings that apply across the workspace. Preferences control the default behavior of the application, including project creation, model development, execution, compilation, communication settings, and user interface options.

Common preference categories include:

<table data-search="false"><thead><tr><th>Preference category</th><th>Description</th></tr></thead><tbody><tr><td><strong>RT-LAB</strong></td><td>Configure default project and model settings.</td></tr><tr><td><strong>Compilation</strong></td><td>Define default compiler and build options.</td></tr><tr><td><strong>Execution</strong></td><td>Configure simulation execution behavior.</td></tr><tr><td><strong>Target communication</strong></td><td>Manage communication settings between the host and target nodes.</td></tr><tr><td><strong>MATLAB/Simulink integration</strong></td><td>Configure MATLAB-related settings and paths.</td></tr><tr><td><strong>Editors and perspectives</strong></td><td>Customize the Workbench appearance and editing behavior.</td></tr><tr><td><strong>File associations</strong></td><td>Define which editor opens specific file types.</td></tr></tbody></table>

Changes made in the Preferences dialog become the default settings for new projects and models. Model-specific settings can still be customized independently through the corresponding editors.

## Search

RT-LAB provides search capabilities to help users quickly locate files and resources within the workspace. The **File Search** tool allows users to search for text within files, making it easier to find model configurations, source code, scripts, and project resources.

To open the search dialog:

**Search > File...** or use the keyboard shortcut **Ctrl + H**.

The File Search tool allows users to:

* Search for specific text across the workspace.
* Restrict searches to selected projects, folders, or files.
* Use wildcard patterns to filter file names (for example, `*.c`, `*.cpp`, `*.py`, or `*.mdl`).
* Perform case-sensitive searches when needed.
* View all matching results in a dedicated **Search Results** view.
* Navigate directly to the matching lines by double-clicking a search result.


---

# 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/overview/navigate-the-rt-lab-environment.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.
