Fix floating point precision issue in step_size validation #4604
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
Python's modulo operation with floating point numbers produces inaccurate results due to binary representation limitations (e.g., 1.0 % 0.1 returns ~0.1 instead of 0). This caused valid fractional step sizes to incorrectly fail validation.
The fix uses np.isclose() for tolerance-based comparison when checking if a range is evenly divisible by the step size.
see #4599
Reviewed By: saitcakmak
Differential Revision: D88077995