> 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/model-entities/toc161394020/toc161394025.md).

# Supports

Learn how supports impose rigid restraints on node degrees of freedom and produce support reactions.

By default, a node is unrestrained, that is, it is free to move in any of the six available DOFs. However, for a model to be stable, restraints on one or more DOFs must be imposed on some nodes. Restraints may be rigid or flexible. Rigid restraints are referred to as supports while flexible restraints are referred to as springs. You may regard supports as springs with infinite spring constants.

You may assign a support with one or more DOFs (Dx, Dy, Dz, Dox, Doy and Doz) restrained to a node. The program uses a six-character code to represent restraint conditions of a support in six DOFs. For example, “111111” represents a fixed a support while “111000” represents a pinned support. By default, restrained DOFs have zero enforced displacements. You may specify non-zero enforced displacements to any or all of restrained DOFs. The enforced displacements are discarded if they are assigned to unrestrained DOFs. You may regard these enforced displacements as special kinds of loads. They participate in all load combinations but always with a load factor of 1.0.

The forces or moments required to enforce rigid restraints are called support reactions. They are computed by the program.


---

# 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/model-entities/toc161394020/toc161394025.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.
