> 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/input-data/toc161393900.md).

# Nodes

How to enter and edit node coordinates in a spreadsheet and round off tiny coordinate values.

Tables > Nodes 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-b395fac9a1930ebb87ac39064c61ff01dae7060e%2FFASTFR~1_img146.png?alt=media)

It allows you to enter nodes in a spreadsheet. Each node includes the nodal coordinates and the selection status. You may not modify the node IDs.

An empty row is allowed if all rows below it are empty (except the node ID and status fields). You may not delete the existing nodes in the dialog. To delete the existing nodes, you must dismiss this dialog and click Modify > Delete.

Due to machine inaccuracy of floating point values, some commands (such as Modify > Rotate) may cause the presence of very small numerical coordinate values. You may round off these tiny values to be zeros by clicking the Round-off Coordinates button. The epsilon used for the round-off may be set from Settings & Tools > Data Options. The default epsilon value is 1e-10 and must be less than or equal to 1e-6.


---

# 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/input-data/toc161393900.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.
