> 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/prepare-the-simulation/run-the-simulation/netlist-tool.md).

# Netlist Tool

In the HYPERSIM workflow, the **netlist** is generated during the **Analyze** step. The file is stored as **netlist.txt** in the project's **\_hyp** folder and is updated each time an analysis is performed.

Devices with the **Exclude** attribute enabled are temporarily excluded from the generated netlist. To exclude a device, select **Exclude Devices** on the **Design** ribbon or use the **Include/Exclude** command from the block's shortcut menu. This feature is commonly used for debugging and model validation.

To open the **Netlist** tool, first run the **Analyze**. Once the analysis is complete, click **Netlist** on the **HYPERSIM** ribbon.

The **Netlist** tool allows users to:

* Inspect block information, including names, types, and parameter values.
* Modify block parameters directly in the netlist.
* Locate a block in the schematic by right-clicking it in the Netlist tool and selecting **Locate Selection**.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-85a96628ded2e9f9656e71d9858b9d48fbfd58ec%2Fnetlist-example.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/model-and-simulation/prepare-the-simulation/run-the-simulation/netlist-tool.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.
