> 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/model-and-simulation/edit-a-model-schematic/navigate-around-a-schematic/define-the-system-unit/set-the-system-unit.md).

# Set the System Unit

## Set the system unit of a block

To temporarily display a parameter using a different unit system—for example, to view a value in **SI** units—right-click the unit label next to the parameter and select the desired unit system from the context menu.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9150f481c8b6db2ed02c71aa7196e1fc002313ee%2Fcase-change-unit.png?alt=media" alt=""><figcaption></figcaption></figure>

To permanently change the default unit system for a block category, use the same context menu to access the **Open data input panel**.

## Set the system unit of the project

In the **HYPERSIM** ribbon, click **Preferences** to open the **Preferences** dialog box, then select the **Data Input** tab. The preferences in this panel determine the default unit system used to display parameters for selected block categories. For each parameter, select either the **SI** or **PU** unit system.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-fccfb959436909c46fda4b56719c9ef786974546%2Fpreferene-data-input.png?alt=media" alt=""><figcaption></figcaption></figure>

For example, the **Network Sources** category is configured to display **General parameters** in **PU** units. As a result, when a source parameter dialog box is opened, the parameters associated with these settings are displayed in per-unit values.


---

# 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/model-and-simulation/edit-a-model-schematic/navigate-around-a-schematic/define-the-system-unit/set-the-system-unit.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.
