> For the complete documentation index, see [llms.txt](https://docs.enercalc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enercalc.com/e3d-training-manual/building-the-model/general-modeling-theory/understanding-model-geometry/shells/mesh-density.md). # Mesh Density How to choose a suitable shell mesh density that balances result accuracy against run time and output volume. Determining a suitable mesh density is more of an art than a science. There are no hard and fast rules to apply here, only general guidelines. The important thing to understand is that deflections are only reported at node locations, and shell stresses are only accurately reported at shell centers. So it is important to have nodes and shell centers relatively close to the locations of interest. Mesh density becomes a tradeoff between having too few results locations and having too many results locations. It helps to understand what happens at the extremes; that is when meshes are way too coarse and when meshes are way finer than they need to be. Extremely coarse meshes will run more quickly than fine meshes, because of the significant reduction in the number of required calculations. But this can come at a cost of accuracy. For example, if a beam is known to have reverse curvature, we would never be able to sketch a reasonable guess for the deflected shape if we only had data for the endpoints and for one or two interior points. By sketching an assumed deflected shape and observing maxima, minima and points of inflection, you can start to establish a bare minimum number of data points that would be desirable for sketching a deflected shape. It stands to reason that you probably wouldn't want to create a mesh that is any more coarse than this, or it might not be useful in terms of quantifying the extremes. On the other hand, extremely fine meshes will result in long run times and will produce reams and reams of data that may be difficult to sort through. There is also a risk of inaccuracies when meshes are excessively fine. So the key is to balance the need for accurate results with the time it takes to process and the complexity of the output. Fortunately modern computers are extremely powerful and current finite element formulations are very efficient, so run times for average models may not be a big problem. And thanks for the sorting and postprocessing features in ENERCALC 3D, the process of reviewing reams of data is often reduced to a trivial task through efficient reporting and onscreen display tools. So when determining an adequate mesh density, it is generally advisable to err to the side of making it finer than it needs to be, rather than using a mesh that is too coarse. For those who are not yet comfortable with establishing a suitable mesh density, here is a suggested procedure for helping to calibrate your judgment. Create a mesh that is obviously too coarse, and apply realistic loads so that analysis results can be obtained. Make note of some result of interest, such as the deflection or moment at a particular location. Modify the mesh density by making it more dense, and observe the effect in the result of interest. Then keep repeating the process until a break point is reached where further subdivision of the mesh no longer produces a change in the value of interest. This will ultimately lead to a mesh density that is optimized for the current conditions. ![](https://3750289988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRZtG5Ynp58kYzLHYbR7%2Fuploads%2Fgit-blob-e81c4efd83b976d646698e9654497f6b6ede6a42%2FMesh%20too%20coarse.jpg?alt=media) Mesh too coarse. ![](https://3750289988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRZtG5Ynp58kYzLHYbR7%2Fuploads%2Fgit-blob-621e49d52a925eb0edc0319507d239c924f6343e%2FMesh%20still%20too%20coarse.jpg?alt=media) Mesh still too coarse. ![](https://3750289988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRZtG5Ynp58kYzLHYbR7%2Fuploads%2Fgit-blob-abebe3f0a09f2dadaa98ecf5da7f718c28ac26af%2FMesh%20getting%20better.jpg?alt=media) Mesh getting better. ![](https://3750289988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRZtG5Ynp58kYzLHYbR7%2Fuploads%2Fgit-blob-a0850f67b4a6a609960067ab59010979b3e0af40%2FMesh%20getting%20much%20better.jpg?alt=media) Mesh getting much better. ![](https://3750289988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRZtG5Ynp58kYzLHYbR7%2Fuploads%2Fgit-blob-c3fe1fe88772d20333b451c744d228318ad0db65%2FCould%20be%20ideal%20mesh.jpg?alt=media) Could be ideal. ![](https://3750289988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRZtG5Ynp58kYzLHYbR7%2Fuploads%2Fgit-blob-bad6f27a21af33caed3665f16a25fa0a1336ec8f%2FProbably%20finer%20mesh%20than%20necessary.jpg?alt=media) Probably finer mesh than necessary. ![](https://3750289988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRZtG5Ynp58kYzLHYbR7%2Fuploads%2Fgit-blob-aabb0a8ad67513972af157952556c08b80475067%2FMuch%20too%20fine%20mesh.jpg?alt=media) Mesh much too fine. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enercalc.com/e3d-training-manual/building-the-model/general-modeling-theory/understanding-model-geometry/shells/mesh-density.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.