> 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/general/assign.md).

# Assign

## Description

The command Assign is used, as the name implies, to assign values to variables. It is necessary to initialize variables in many cases:

* For the if expression in a loop to function
* To evaluate expressions before using them in other commands such as Miscellaneous or Pause/message (which does not support expression evaluation)
* To output signal values or component parameter values in a tableOut report

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

If a variable is not initialized before being used in the **Processing** command or **Expression** command for instance, it will cause an error and the test sequence will abort.

{% hint style="info" %}
The **Assign** command uses the ScopeView calculation engine, which means it supports all ScopeView functions (e.g., `max`). Functionally, **Eval**, **Expression**, and **Assign** produce the same results. The differences lie only in their dialog layout and whether they allow defining one or multiple expressions at a time:

**Eval:** Evaluates a single expression.

**Expression:** Evaluates one or multiple expressions.

**Assign:** Evaluates one or multiple expressions. Has a **multi-param** mode.
{% endhint %}


---

# 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/general/assign.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.
