> 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/toc161393755/toc161393772.md).

# Sub-Mesh Shells

How to sub-mesh selected shells into multiple segments with automatic load transfer and node merging.

Modify > Sub-Mesh Shells prompts you with the following dialog.

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

It allows you to sub-mesh selected shells by specifying 2 or more segments along sides 1-2 & 4-3 and sides 2-3 & 1-4. Loads on the original shells are assigned automatically to the generated shells after sub-meshing. You have the option to merge nodes and elements after sub-meshing. You should check this option unless duplicate nodes are explicitly permitted.

The input in the dialog above is applied to the shells in screen capture below\...

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

shells before sub-meshing

...to generate the shells in the screen capture below by meshing.

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

shells after sub-meshing


---

# 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/toc161393755/toc161393772.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.
