> For the complete documentation index, see [llms.txt](https://docs.paragontruss.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paragontruss.com/design/how-to/general/run-and-view-component-analysis.md).

# Run & View Component Analysis

## Analyze a Truss and View the Results

Before you begin, select a component, such as a `Common` truss.

### Step 1 - Insert or Select a Component and Click `Analyze`

To insert a component, see [Create Projects and Components](/design/how-to/general/create-projects-and-components.md). The [Analyze](/design/getting-started/interface-overview/actions-toolbar.md#analyze) button is in the Actions Toolbar.

### Step 2 - Click `Analysis and History` to open its subpanel

See [Analysis and History](/design/getting-started/interface-overview/actions-toolbar.md#analysis-and-history) and the [Analysis and History Subpanel](/design/getting-started/interface-overview/actions-toolbar.md#analysis-and-history-subpanel).

### Step 3 - Select a Load Case to Visualize it on the Truss or Scroll Down to See Calculations for Members, Plates, and Joints

{% hint style="success" %}
Tip

Load Case visuals can also be toggled from the `Component Subpanel` in the `Right Sidebar`.
{% endhint %}

<figure><img src="https://2598702589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIkcl8vW0QKiqUIx7Xdc%2Fuploads%2Fgit-blob-ad20527acaf92c8a8cf9bc13cbd6b7d1207b6460%2Fcomponent_analysis.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Restore Component Analysis

### Step 1 - Access the `Analysis and History` subpanel

### Step 2 - Click the Restore Component Button for the Desired Component to make the version of the truss from that analysis current

The Restore Component button is next to each analysis in the list. It is available for every analysis except the active one.

### Step 3 - Click `Analyze` to view the results

<figure><img src="https://2598702589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIkcl8vW0QKiqUIx7Xdc%2Fuploads%2Fgit-blob-9a73595e5baf4284f4d7aaf64bac46d524a57147%2Frestore_component.gif?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Tip

You can rename items in the Analysis History Subpanel.
{% endhint %}

## Run a Detailed Analysis to Access Force Visuals

### Step 1 - Click `Analysis Options` and Check `Detailed`

The [Analysis Options](/design/getting-started/interface-overview/actions-toolbar.md#analysis-options) button is next to the Analyze button.

### Step 2 - Close the Options and Click `Analyze`

### Step 3 - Access the `Analysis and History` subpanel

### Step 4 - Select a load case and use the `Display Forces` menu

Expand the list of load cases in the Analysis and History subpanel and click on one to select it. Open the Display Forces menu to toggle the forces you wish to see displayed on the truss.

<figure><img src="https://2598702589-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzIkcl8vW0QKiqUIx7Xdc%2Fuploads%2Fgit-blob-54915dc9da0b6e0b2d6403ba3ba3e989b9a19d68%2Fdetailed_analysis.gif?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://docs.paragontruss.com/design/how-to/general/run-and-view-component-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.