Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
rhino:floating_point_faq [2025/04/03] dale |
rhino:floating_point_faq [2025/04/03] (current) maryfugier |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======Floating Point Issues in Rhino====== | ======Floating Point Issues in Rhino====== | ||
| - | ===== Background | + | ==== Background ==== |
| When you model is located far from the world origin, or you are using a unit that is too small for the physical size object you are modeling, then floating point issues can appear. | When you model is located far from the world origin, or you are using a unit that is too small for the physical size object you are modeling, then floating point issues can appear. | ||
| Line 11: | Line 11: | ||
| **In general, modeling a very large distance from the origin can cause problems and should be avoided.** | **In general, modeling a very large distance from the origin can cause problems and should be avoided.** | ||
| - | ===== Double-precision Floating-point Number===== | + | ==== Double-precision Floating-point Number==== |
| Rhino, like most CAD products, represents position in **double-precision floating-point numbers**. That means the x‑, y‑, or z-coordinate of any point can have a value ranging from as large as ±10308 to as small as ±10-308. | Rhino, like most CAD products, represents position in **double-precision floating-point numbers**. That means the x‑, y‑, or z-coordinate of any point can have a value ranging from as large as ±10308 to as small as ±10-308. | ||
| Line 24: | Line 24: | ||
| - | ===== Best Practices | + | ==== Best Practices ==== |
| Make2D and Clipping drawing rely on Rhino being able to calculate accurate intersections. If the intersections are “round off”, then the outcomes of these commands will look inaccurate. To get the accuracy desired, you need to: | Make2D and Clipping drawing rely on Rhino being able to calculate accurate intersections. If the intersections are “round off”, then the outcomes of these commands will look inaccurate. To get the accuracy desired, you need to: | ||
| Line 30: | Line 30: | ||
| * And model close to the origin. | * And model close to the origin. | ||
| - | The is the best approach to create metric architectural models in reasonable unit like Meters and **only dimension in mm**. | + | The is the best approach to create metric architectural models in reasonable unit like **Meters** and **only dimension in mm**. |
| + | While mm entirely is the correct choice for a small object like jewelry. For architecture where the objects are 10,000 or more times larger, a unit like Meters is a much better choice for precise calculations. | ||
| - Begin a new model with Meters Small template (this will give you .001 meters precision, you can increase it to .0001 but it you go beyond that, you will start to see round off errors.) | - Begin a new model with Meters Small template (this will give you .001 meters precision, you can increase it to .0001 but it you go beyond that, you will start to see round off errors.) | ||
| Line 36: | Line 37: | ||
| - Dimension in MM only | - Dimension in MM only | ||
| - There is an override on the Dimension to display the dimension in a unit/ | - There is an override on the Dimension to display the dimension in a unit/ | ||
| + | {{: | ||
| ===== More Information ===== | ===== More Information ===== | ||
| Line 74: | Line 76: | ||
| * [[https:// | * [[https:// | ||
| * Discourse Topic: [[https:// | * Discourse Topic: [[https:// | ||
| + | * | ||
| + | | ||
rhino/floating_point_faq.1743701237.txt.gz · Last modified: 2025/04/03 by dale
