> 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/toc442029162/toc161393986.md).

# Data Options

How to set distance tolerance, undo levels, round-off, stress reporting, and stiffness factors in Data Options.

Settings & Tools > Data Options 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-70b4c396b0ebb02c466f8d37f8845e46a79496a2%2FFASTFR~1_img215.png?alt=media)

Distance tolerance is used for distance comparisons in certain commands such as **Modify > Merge All Nodes & Elements** and **Modify > Split Members**. Distances less than distance tolerance are considered zero by the program.

The “Undo/redo levels” sets the maximum undo/redo levels which the program will perform. The program requires extra computer memory for each undo/redo level. The default undo levels setting is 100. Depending on your computer memory and model sizes, you may want to set undo levels to be smaller.

Round-off epsilon is used to truncate floating point numbers such as those found in results. For example, a fixed support may have a displacement of 1.077e-10 when in fact it should zero. A round-off epsilon of 1e-9 will do just that.

Stresses are computed at the center and at the nodes of finite elements such as shells or solids. However, you may request the program to show stresses at the finite element center only, nodes only, or both. The checkbox “Show only selected entities in spreadsheet” determines if all or selected nodes, elements and their dependents will be shown in the spreadsheet. By checking this checkbox, you may easily query selected entities in a large model. It is important to point out that data in some input spreadsheets may not be modified when this option is checked. The checkbox “Save results when the document is saved” gives you the option to save results (when available) to a file when the model input data is saved. The result file is a binary file and has the same file name as model input file, but with an extension of “rst” (static results) or “dyn” (dynamic results). The result file could be much larger than the model input file.

The fictitious oz stiffness factor is used to multiply the minimum of diagonal terms (excluding oz) in the shell stiffness matrix to construct the fictitious oz stiffness terms. The smaller this factor, the more accurate the solution, especially for very thin and doubly curved shells. The valid range for this factor is \[1e-12, 1e-3]. You normally do not need to change its default value (1e-7). Numerical difficulties may arise during solution if this value is set too small.

The diaphragm stiffness factor is used to control the diaphragm rigidity. The larger this factor, the more rigid the diaphragm action is. The valid range for this factor is \[0, 1e20]. The default value is 1e4. Numerical difficulties may be present during static or frequency analysis if the diaphragm stiffness factor is set too large (say 1e13 for 64-bit floating point solver). It is generally recommended to use 128-bit floating point solver to avoid the aforementioned problem.


---

# 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/toc442029162/toc161393986.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.
