> 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/hypersim/simulation-control-monitoring-and-logging/log-simulation-data-with-datalogger/review-logged-data.md).

# Review Logged Data

Once the simulation has finished, all recorded files are saved to the **Recordings** folder within the project directory.

## Visualize data in ScopeView

To visualize logged data in ScopeView, simply double-click an **OPREC** file directly in HYPERSIM Project Explorer. ScopeView will launch automatically with the correct data source and signals pre-selected for immediate viewing.

If the file contains multiple frames, ScopeView provides access to all of them. Files with the extensions `.mat`, `.csv`, and `.oprec` can also be opened manually in ScopeView.

## Visualize data in MATLAB

To work with OPREC files in MATLAB, use the function `OpRecInfo` for metadata, and the function `OpRecRead` for recorded signals.

### Setup

1. Open your MATLAB version.

2) Go to C:\OPAL-RT\HYPERSIM\\\<HYPERSIM\_version>\Windows\hyperlink\datalogger folder, where all the required `.m` scripts are located.

### OpRecInfo

Use `OpRecInfo` with the full path to the `.oprec` file as an argument to retrieve the following metadata:

* Time step (in seconds)
* Minimal timestamp (first recorded simulation step)
* Maximum timestamp (last recorded simulation step)
* Count and list of all recorded signals

{% code overflow="wrap" lineNumbers="true" %}

```matlab
OpRecInfo('C:\Data\SignalGroup_1.oprec');
```

{% endcode %}

Example:

![](https://opal-rt.atlassian.net/wiki/download/thumbnails/143463923/image2022-8-19_16-15-36.png?version=1\&modificationDate=1737731770148\&cacheVersion=1\&api=v2\&width=451\&height=250)

### OpRecRead

Use `OpRecRead` with the full path to the `.oprec` file as an argument to read all recorded signal data.

{% hint style="info" %}
Optional arguments include the first and last timestamps to read. The first timestamp defaults to the first recorded step and is adjusted if it is lower than the earliest recorded timestamp; it becomes mandatory when specifying a last timestamp. The last timestamp defaults to the final recorded step and is adjusted if it exceeds the latest recorded timestamp.
{% endhint %}

{% code overflow="wrap" lineNumbers="true" %}

```matlab
[header, data] = OpRecRead('C:\Data\SignalGroup_1.oprec');
```

{% endcode %}

Provide two output parameters to store the data read from the .oprec file:

* The first parameter will store the signal names and types.
* The second parameter will store all the step data for the signals in the exact same order as in the first parameter.

Example:

<div align="left"><figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8a6cca3eeb1f9c8559c4c78299fdc2c7a3815c09%2Fdatalogger-ex2.png?alt=media" alt="" width="438"><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c300888bbb4837257dd87e40d317e5e8d34847c5%2Fdatalogger-ex3.png?alt=media" alt="" width="421"><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f07a2c247e1d1068ee89658e0939ad77969f3d3c%2Fdatalogger-ex4.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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/hypersim/simulation-control-monitoring-and-logging/log-simulation-data-with-datalogger/review-logged-data.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.
