> 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/topology-analysis.md).

# Topology Analysis Tool

The **Topology Analysis** tool is available from the HYPERSIM ribbon and must be **run after** the model has been analyzed (**Analyse** command from the HYPERSIM ribbon).

{% hint style="danger" %}

### **Limitations**

A signal which has been fragmented by **Page Connectors** can only locate the first page, as they share the same name.

A bundle Breakout cannot be located as it is not a component which takes part in the topology of the model, it is an artifact for simplifying the schematic.
{% endhint %}

## Circuit overview <a href="#id-1.-circuit-overview" id="id-1.-circuit-overview"></a>

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

This section displays **general information and statistics** about the model's topology.

The entire report can be **exported to HTML** (top-right button).

The same report is also appended to the [model's diagnotic](https://www.opal-rt.com/docs/hypersim/model-and-simulation/prepare-the-simulation/run-the-simulation/diagnostic-tool.md).

## Warnings and errors <a href="#id-2.-warnings-and-errors" id="id-2.-warnings-and-errors"></a>

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

While **topology errors** prevent a simulation from being launched, **warnings** highlight potential issues or model configurations that may produce unexpected results but do not necessarily block simulation. Reviewing warnings can help identify and correct problems before they affect the simulation outcome.

Errors and warnings can be filtered by **severity level** and **keywords**, making it easier to locate and focus on specific issues within the model.

Right-click an error or warning to view additional details, and to locate the device on the circuit, if applicable.

## Fragmented Signals <a href="#fragmented-signals" id="fragmented-signals"></a>

A signal consists of one or more connected segments. If two segments cannot be linked through a continuous chain of connected segments, they are considered to belong to separate *roots* of the same signal.

While it can be useful to avoid lines crossing the circuit, it can also create confusion in tracing the signals.

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

**Click Search** to scan the model for signals with multiple roots. For each result, right-click the corresponding row to locate the signal or any pins connected to it.

{% hint style="info" %}
This process can take **several minutes** on larger models.
{% 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/model-and-simulation/prepare-the-simulation/run-the-simulation/topology-analysis.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.
