> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/e3d-user-manual/interface/toc175916526/toc175916652/generate-loads2/toc161393894.md).

# Additional Masses

How to assign additional masses and mass moments of inertia to selected nodes for frequency analysis.

Create > Generate Loads > Additional Masses prompts you with the dialog below.

![](https://560001759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWNe8U6EBBBdUJHdb2X9G%2Fuploads%2Fgit-blob-340cd87da910a69e92b84ca0ebaa1cc607462f89%2FFASTFR~1_img135.png?alt=media)

It allows you to assign additional masses and mass moment of inertia to selected nodes. The mass can be applied to X, Y and/or Z directions while the mass moment of inertia can be applied to OX, OY and/or OZ directions. Additional Masses are added to the mass calculated from the load combination for frequency analysis (see the command: Analysis > Frequency Analysis). Mass moment of inertia values can only be input using the Additional Masses command.

The mass unit is a force unit divided by the acceleration of gravity, while the mass moment of inertia has units of mass times length squared. The acceleration of gravity is taken as 386.09 in/sec^2 or 9.8 m/sec^2.


---

# 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://enercalc.com/docs/e3d-user-manual/interface/toc175916526/toc175916652/generate-loads2/toc161393894.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.
