Numeric Conversions
- Updated2023-02-17
- 1 minute(s) read
Numeric Conversions
When you wire numeric data to a node that expects a different numeric data type, the node coerces the data to the most precise type.
A red coercion dot appears on the node input where the coercion takes place.
In the following diagram, a red coercion dot appears on the Add node because the node expects two inputs of matching numeric data types but receives a double-precision, floating-point number and an integer. Because input 0 (a double-precision, floating-point number) is more precise than input 1 (an unsigned, 32-bit integer), the node coerces input 1 to a double-precision, floating-point number.
Related Information
- Addressing Issues with Numeric Conversions
When you wire numeric data to a node that expects a different numeric data type, the node coerces the data to the most precise type. A red coercion dot appears where the coercion takes place. Because numeric coercions can affect memory usage, performance of a VI, or cause a VI to generate inaccurate results, use one of the strategies in the following table to eliminate or reduce the impact of a problematic coercion.