Float Condition¶
Evaluates a comparison between two floating-point numbers and returns a boolean result. Supports standard comparison operators including equality, inequality, and relational checks. On invalid operations or runtime errors, it safely returns False.
Usage¶
Use this node when you need to branch or gate logic based on comparisons between two numeric (float) values. Typical workflows include threshold checks (e.g., score > 0.7), bounds validation (min <= value <= max using two nodes), or feature flags tied to numeric inputs. Chain its boolean output into downstream logic nodes (e.g., If/Bool Operation) to control flow.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| a | True | FLOAT | Left-hand operand for the comparison. Accepts floating-point values within the permitted range. | 0.75 |
| b | True | FLOAT | Right-hand operand for the comparison. Accepts floating-point values within the permitted range. | 0.7 |
| operation | True | STRING (enum) | Comparison operator to apply between a and b. Supported: '==', '!=', '<', '>', '<=', '>='. | > |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| result | BOOLEAN | The boolean result of the comparison between a and b using the selected operation. | True |
Important Notes¶
- Float equality caveat: Comparing floats with '==' can be sensitive to precision. Consider using '<='/'>=' or pre-rounding inputs if you expect small numeric noise.
- Input ranges: a and b accept values roughly in [-9.99999999999e11, 9.99999999999e11]. Values outside this range are not allowed.
- Step setting: Inputs use a step of 1 in the UI; you can still enter decimal values directly.
- Error handling: If an unknown operation is provided or an error occurs, the node returns False.
- NaN behavior: Standard float rules apply; for example, NaN == any value is False, and NaN != any value is True.
Troubleshooting¶
- Unexpected False for near-equal numbers: Floating-point precision may be the cause. Try rounding inputs before comparison or use '<='/'>=' instead of '=='.
- Result always False: Verify the 'operation' value is one of the supported options and that a and b are valid floats.
- Cannot set certain values: Ensure a and b are within the allowed numeric range.
- Intermittent errors with special values: Check for NaN or infinite values in inputs; sanitize or clamp inputs before passing them into the node.