> 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/automation-api-and-scripting/automate-using-testview/test-commands-reference/main/processing.md).

# Processing

## Description

The Processing command makes the bridge between the TestView engine and the HYPERSIM engine for a test. This command is the one that runs acquisitions. Therefore, if several iterations must be done, this command should be placed inside a loop.

## Parameters

### General tab

Defines the different settings for the acquisition and what shall be generated in the data folder.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-1cd52409e29bfcc7d6447dd24a773625ab6deeaf%2Fimage%20(1265).png?alt=media" alt=""><figcaption></figcaption></figure>

**Acquisition section:** Define the duration of one test (similarly to ScopeView). Make sure the sampling rate is coherent with the time step in the HYPERSIM Settings to avoid linear interpolation between samples. The 'Starting time (s)’ allows offsetting the time at which data starts being saved in relation to the t=0 of the acquisition command. The ‘Synchronization’ and ‘Operation sequence’ operate in the same way respectively as ‘Sync’ and ‘Trig’ do in ScopeView. If ‘Synchronization’ is checked, it will synchronize the beginning of the acquisition with the Point-On-Wave command in the model. If ‘Operation sequence’ is checked, it will enable the events to occur (e.g. the operation of breakers). The signals key is used to select the relevant signals for the acquisition.

The supported formats to export the data are: Joint Photographic Expert Group (*.jpg), MATLAB Binary (*.mat), Portable Network Graphic (*.png), PostScript (*.ps) and Text (tab separator) (\*.txt).

**Processing and Post-Processing sections:** These two sections have the same options that are available in the ‘View’ tab of the main TestView window. Both options (i.e. the one in the Processing command and the one in the ‘View’ tab) must be checked to be activated. This way, each test sequence has local parameters that can be either activated or overridden through the 'View' tab.

The ‘Title’ option does not change the name of the file but rather adds a line of regular-size text in the upper left corner of the generated document. It supports variable analysis, it is thus possible to write a title such as ‘Waveforms for Fault Time: %{Fault\_time} s’, where ‘Fault\_time’ is a variable in the test.

The ‘Data Integrity’ option is not in the ‘View’ tab for processing. If checked, the data will be saved immediately during the test; if unchecked, the data will be saved to the disk only at the end of the loop. In this case, saving to the disk means writing the ‘.cfg’ file in \[root directory]/data/\[Name of test]-\[0-9]. It works in combination with the ‘Saving Mode’ tab. If ‘Save nothing’ is checked, no ‘.cfg’ files will be written.

The PDF files are saved in the TestView project directory.

{% hint style="danger" %}
The print graphics option is not supported.
{% endhint %}

### Processing tab

Used to run the calculation on the values acquired in a single test.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9bbf07203a4ab67a73e16165107f6f704216aead%2Fimage%20(1266).png?alt=media" alt=""><figcaption></figcaption></figure>

Signals available in the **Processing** tab come from the **Signals Key** selected in the **General** tab of the Processing command.

To define or edit a Signals Key:

* Open the **Signals Manager**, accessible either through:
  * the **Signals Key** button in the **General** tab of the Processing command, or
  * **Tools → Signals Manager** from the main TestView window.

A Signals Key is simply a list of signals that TestView will acquire during each test iteration. Only the signals included in the selected key will appear in the Processing tab.

### Post‑Processing Tab

Used to compare results from several tests.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-cda76074fd0cad961a7c3efce6e1eb070801e19b%2Fimage%20(1267).png?alt=media" alt=""><figcaption></figcaption></figure>

Signals available in the **Post‑Processing** tab must be **scalar values produced in the Processing tab**. For example, in the **Processing** tab you might define:

* `Imax_phaseA = max(EST7_Va)` → **scalar** → *available in Post‑Processing*
* `Fault_CMDa` → **not scalar** → *not available in Post‑Processing*

Only scalar results—variables assigned a single numeric value per iteration—can be used in Post‑Processing operations such as comparisons, filtering, and criteria evaluation.

{% hint style="info" %}
When a test is running, if the **Post-Processing** pop-up window displays only the last result (i.e. just one point instead of four when four tests were executed), it is because of the ‘Operation’ option in the **Loop** command.
{% endhint %}

### Saving Mode Tab

Defines criteria for saving waveforms in COMTRADE format. By default, all results generated in the **Processing** and **Post‑Processing** tabs are saved, but you can use criteria to reduce disk usage and skip storing unnecessary data.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-29d7ef32df4e24896b299c31ad931f1a64685edb%2Fimage%20(1268).png?alt=media" alt=""><figcaption></figcaption></figure>

**Criteria View**

<table data-header-hidden><thead><tr><th width="143.09088134765625"></th><th></th></tr></thead><tbody><tr><td><strong>&#x3C;none></strong></td><td>ignore the criteria line, the criteria is never met</td></tr><tr><td><strong>Min</strong></td><td>keep the test with the minimum value of the expression</td></tr><tr><td><strong>Maxf</strong></td><td>keep the test with the maximum value of the expression</td></tr><tr><td><strong>Minf</strong></td><td>keep the test with the finite minimum value of the expression</td></tr><tr><td><strong>Maxf</strong></td><td>keep the test with the finite maximum value of the expression</td></tr><tr><td><strong>First</strong></td><td>keep the first test of the loop sequence</td></tr><tr><td><strong>Last</strong></td><td>keep the last test of the loop sequence</td></tr><tr><td><strong>Save</strong></td><td>keep the test if the expression is true</td></tr></tbody></table>

For example, in the Figure below, TestView keeps all the tests that meet one or many of the following criteria:

1. The test with the maximum value of “Ia”
2. The test with the finite minimum value of “Ia”
3. The last test of the sequence
4. All tests where “a” is greater than 616900

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8952f185d3b156998a88fa055020df1bd301577f%2Fimage%20(1269).png?alt=media" 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/hypersim/automation-api-and-scripting/automate-using-testview/test-commands-reference/main/processing.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.
