> 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/hyperlab/simulation-control-monitoring-and-logging/log-simulation-data/select-signals-to-log.md).

# Select Signals to Log

There are different ways to select the signals to be recorded, which the user can choose according to their preferences.

## From the Recorder View

1. Open the Recorder View.
2. Click on **+ Add** at the right of the screen.
3. From the Data Points list, click once on the signals you want to record. Clicking on a selected signal would deselect it.
4. Click on **Add**.

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2FScOwd2s6Tkym1X2JKfo2%2FRecorders_add.png?alt=media&amp;token=dac52b08-5afd-4e5f-a139-e3317c2978a1" alt=""><figcaption></figcaption></figure>

## With drag-and-drop

1. Open the Model View.
2. Double click on the model block from which the signal to be recorded comes.
3. In the side bar, **click** on the signal to be recorded.
4. Drag-and-drop the signal into the Recorder item.

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2FchLlS0gjGorRzu7XicRe%2FRecorder_drag_drop.png?alt=media&amp;token=cbc5dbf0-c920-4ac0-838f-92ffdc45cddb" alt=""><figcaption></figcaption></figure>

## With the contextual menu

* Open the Model View.
* Double click on the model block from which the signal to be recorded comes.
* In the side bar, **right-click** on the signal to be recorded.
* Select menu **Add to Recorder** -> **Recorder File**.

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2Fi8w7IHvIMeDwLpBOoVdf%2FRecorder_contextual.png?alt=media&amp;token=1a65ebb7-0691-45d7-9973-e766adbfdb76" alt=""><figcaption></figcaption></figure>

## Recording list

No matter what method you chose to select the signals, they are added to the recording list. From there, they can be **renamed** or **deleted**, or their order **rearranged.**

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2FEVVovCZ3EmqqbBQr9ZIZ%2FRecorders_rearrange.png?alt=media&amp;token=b6fed0c2-1456-4f15-b21a-63e7ae29c580" alt=""><figcaption></figcaption></figure>


---

# 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/hyperlab/simulation-control-monitoring-and-logging/log-simulation-data/select-signals-to-log.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.
