NinjaScript > Educational Resources > Tips > FloatingPoint Arithmetic 

Some common problems that you may encounter when comparing different double values are the caveats involved with floatingpoint arithmetic. Because of the way computers store floatingpoint numbers, under certain conditions your value will be an approximate of the actual decimal number you wanted. If this situation arises in your code, your comparison logic may not execute as you had intended even if your logic was mathematically sound on paper. To address this issue you will need to use a range comparison that takes into account the slight differences in the least significant digits of the floats.
For example, under normal mathematics we would assume double x is equivalent to double y.
Even the output of this code segment suggests they are the same:
Unfortunately, as demonstrated by this code segment, they are not.
This segment outputs the following:
This means when we try to check for equality it would never evaluate to true even if it does mathematically.
Instead of comparing double x to y for an exact equality we will need to check a range.
The arbitrary constant you choose to compare the range with should match the precision and accuracy of the floatingpoint numbers you are comparing.
Alternatively, you can check the difference between the two variables against the double.Epsilon field. double.Epsilon field represents the smallest possible double value.
You can also use a Compare() method to accurately compare floatingpoint numbers. Take note that this method should only be used to compare price values since its precision is based on the instrument’s tick size and may be unsuited for use in other floatingpoint situations.
The Compare() method returns a value of “1” if the first parameter is greater than the second, “1” if the first parameter is less than the second, and “0” if the first parameter is equal to the second.
For a more formal analysis of floatingpoint arithmetic, there are many resources online: http://docs.sun.com/source/8063568/ncg_goldberg.html http://www.codeproject.com/dotnet/ExtremeFloatingPoint1.asp#terms 