NinjaTrader Support Forum > Tips Floating-Point Arithmetic

 Tips Official NinjaScript tips and tricks

 11-06-2007, 06:05 PM #1 NinjaTrader_JoshP NinjaTrader Product Manager     Join Date: May 2007 Location: Denver, CO Posts: 17,459 Thanks: 1 Thanked 387 times in 108 posts Floating-Point Arithmetic Applies to NinjaTrader 7 and NinjaTrader 8 Some common problems that you may encounter when comparing different double values are the caveats involved with floating-point arithmetic. Because of the way computers store floating-point 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. Code: ```double x = 90.10; double y = 100 * 0.9010; Print(“double x: ” + x); Print(“double y: ” + y);``` Even the output of this code segment suggests they are the same: Code: ```double x = 90.1 double y = 90.1``` Unfortunately, as demonstrated by this code segment, they are not. Code: ```bool c = (x == y); Print(“x equals y: ” + c);``` This segment outputs the following: Code: `x equals y: False` This means when we try to check for equality it would never evaluate to true even if it does mathematically. Code: ```if (x == y) // Do something. This will never be true.``` Instead of comparing double x to y for an exact equality we will need to check a range. Code: ```if (Math.Abs(x – y) < 0.0001) // Do something``` The arbitrary constant you choose to compare the range with should match the precision and accuracy of the floating-point 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. Code: ```if (x – y < double.Epsilon) // Do something``` You can also use a Compare() method to accurately compare floating-point 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 floating-point situations. Code: ```double newPriceRange = Close[0] - Open[0]; double oldPriceRange = Close[1] - Open[1]; if (Instrument.MasterInstrument.Compare(newPriceRange, oldPriceRange) == 1) { // Do something }``` 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 floating-point arithmetic, there are many resources online: http://docs.sun.com/source/806-3568/ncg_goldberg.html http://www.codeproject.com/dotnet/Ex...int1.asp#terms JoshNinjaTrader Customer ServiceUse Kinetick, NinjaTrader’s preferred market data service - Learn MoreFree online training events - View Schedule Last edited by NinjaTrader_Jesse; 06-03-2015 at 12:49 PM.
 The following 6 users say thank you to NinjaTrader_JoshP for this post:

 Thread Tools Display Modes Linear Mode

 Posting Rules You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is On HTML code is Off Forum Rules
 Forum Jump User Control Panel Private Messages Subscriptions Who's Online Search Forums Forums Home News and Announcements     News and Announcements NinjaTrader 8     Platform Technical Support     Add-On Development     Indicator Development     Strategy Development NinjaTrader 7     Platform Technical Support     General Development     Indicator Development     Strategy Development NinjaScript File Sharing     NinjaScript File Sharing Discussion     Version 8 Add-Ons     Version 8 Indicators     Version 8 Strategies     Version 7 Indicators     Version 7 Strategies     Version 7 Miscellaneous NinjaScript Educational Resources     Reference Samples     Tips Suggestions and Feedback     Suggestions And Feedback Historical Beta Archive     Version 8 Beta

 Similar Threads Thread Thread Starter Forum Replies Last Post twas2007 Strategy Development 2 10-18-2007 12:51 PM sunnyrain Platform Technical Support 1 10-12-2007 01:10 PM cutter Indicator Development 10 09-17-2007 12:17 PM SigmaTrader Suggestions And Feedback 2 07-10-2007 01:15 PM

All times are GMT -6. The time now is 01:09 AM.

Futures, foreign currency and options trading contains substantial risk and is not for every investor. An investor could potentially lose all or more than the initial investment. Risk capital is money that can be lost without jeopardizing ones financial security or lifestyle. Only risk capital should be used for trading and only those with sufficient risk capital should consider trading. Past performance is not necessarily indicative of future results. View Full Risk Disclosure.

CFTC Rules 4.41 - Hypothetical or Simulated performance results have certain limitations, unlike an actual performance record, simulated results do not represent actual trading. Also, since the trades have not been executed, the results may have under-or-over compensated for the impact, if any, of certain market factors, such as lack of liquidity. Simulated trading programs in general are also subject to the fact that they are designed with the benefit of hindsight. No representation is being made that any account will or is likely to achieve profit or losses similar to those shown.