> 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/training-c3-intermediate-layout-and-design/6.0-generating-component-designs/6.3-analyzing-trusses.md).

# 6.3 Analyzing Trusses

Estimated Completion Time: 4 minutes

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpGfM5RvazSdnXVojfoP2%2Fuploads%2FjWGuRVTZdCfFMqfNN9B1%2FDivider.png?alt=media&#x26;token=8dd5a410-5fa4-485b-952b-3888c8cce98b" alt="" height="12" width="1920"><figcaption></figcaption></figure>

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpGfM5RvazSdnXVojfoP2%2Fuploads%2FjWGuRVTZdCfFMqfNN9B1%2FDivider.png?alt=media&#x26;token=8dd5a410-5fa4-485b-952b-3888c8cce98b" alt="" height="12" width="1920"><figcaption></figcaption></figure>

## Description

This module demonstrates how to analyze all trusses within a project. Analyzing trusses applies loads and forces to chord and web members and also applies plating. The Explorer panel displays the analysis status to aid in the systematic review of all truss components.

{% hint style="success" %}
Tip

If you would like to perform a detailed analysis for all components, a best practice is to open a single component in Design Mode, enable Detailed Analysis, return to Layout Mode, and Analyze All Changed Components.
{% endhint %}

## Objectives

* Describe how to ensure a Detailed Analysis is performed on all trusses.
* Explain how to identify analysis status from the Explorer panel.
* Demonstrate how to analyze all components from Layout.

## Additional Resources

* Training Plan 3 accessible from Choose/Create Project > OPEN SAMPLE

## Learning Activity

Watch video and follow along within the Paragon Design App.

{% embed url="<https://youtu.be/4UdsIWt125g>" %}

<details>

<summary>Video Transcript:</summary>

In this video, we are going to analyze all of our trusses. After analyzing the trusses we will be able to then fine tune each truss where adjustments may be needed.

Let's analyze our trusses. From the project menu, select analyze all changed components. That'll bring up the analyzing components dialogue box. We can see here the software is systematically going through each design, one at a time. We can follow the process down as it works. Notice that the majority of these have green check marks and a few others have some red exclamations. That means we are finding a few issues with some of the designs. We will review each of these in a future video.

To view the item in question, you can click on the carrot to expand and see the error. We are prompted with the close option after each truss design has been analyzed. After we click to close the tool we can then view each truss design that is in question. As we see most are in Green that their checks passed. A few are in red as well. We will review these trusses and solve any issues that didn't pass in another video.

That will do it for this quick instruction on analyzing our trusses.

Thanks for watching!

</details>


---

# 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/training-c3-intermediate-layout-and-design/6.0-generating-component-designs/6.3-analyzing-trusses.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.
