-
Notifications
You must be signed in to change notification settings - Fork 54
Floating Point Numbers comparison #203 #496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
saikarna913
wants to merge
3
commits into
fortran-lang:main
Choose a base branch
from
saikarna913:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,76 @@ | ||
# Floating-Point Tolerance and Precision in Fortran | ||
|
||
Floating-point numbers like `0.1` cannot be represented exactly in binary because their binary form is infinite and repeating. Due to the limited precision of floating-point formats (like 32-bit or 64-bit), these numbers are rounded off to fit within the constrained number of bits. | ||
This rounding can lead to small errors in representation and calculations. | ||
|
||
To ensure reliable comparisons, it is better to use **tolerance** to check whether two numbers are close enough rather than comparing them directly. | ||
|
||
## Handling Floating-Point Comparisons | ||
|
||
Here’s an example of how to use a tolerance value in Fortran: | ||
|
||
### Example: Using Tolerance | ||
```fortran | ||
real(dp) :: tol | ||
tol = 10 * epsilon(1.0_dp) ! epsilon returns the smallest number such that 1.0 + epsilon > 1.0 | ||
|
||
if (abs(x - y) < tol) then | ||
print *, "Effectively Equal" | ||
else | ||
print *, "Not Equal" | ||
end if | ||
``` | ||
|
||
In this example: | ||
- The **tolerance** value is derived using either `epsilon()` or a manually defined small value. | ||
- Instead of checking `x == y`, we compare the absolute difference `abs(x - y)` to the tolerance. | ||
|
||
--- | ||
|
||
## Avoiding Floating-Point Precision Issues | ||
|
||
Sometimes, directly incrementing floating-point numbers can cause cumulative rounding errors. | ||
Instead, use **integer iterators** and convert them to floating-point values within the loop. | ||
|
||
### Example: Using Integer Iterators | ||
```fortran | ||
integer :: i | ||
real(dp) :: step, value | ||
step = 0.1_dp | ||
|
||
do i = 0, 10 | ||
value = i * step | ||
print *, value | ||
end do | ||
``` | ||
|
||
In this example: | ||
- The step size is defined as `0.1` in double precision. | ||
- The loop uses integers (`i`) to avoid compounding errors when iterating. | ||
|
||
--- | ||
|
||
## Why Use Tolerance? | ||
|
||
Due to rounding errors, numbers like `0.1 + 0.2` may not exactly equal `0.3`. Direct comparisons fail in such cases: | ||
```fortran | ||
if (a + b == c) then | ||
print *, "Equal" | ||
else | ||
print *, "Not Equal" | ||
end if | ||
``` | ||
Instead, use a tolerance to make approximate comparisons: | ||
```fortran | ||
if (abs((a + b) - c) < tol) then | ||
print *, "Approximately Equal" | ||
else | ||
print *, "Not Equal" | ||
end if | ||
``` | ||
|
||
--- | ||
|
||
|
||
|
||
|
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.
Uh oh!
There was an error while loading. Please reload this page.