https://community.splunk.com/t5/Splunk-Search/Wrong-results-on-stats-sum-or-addcoltotals-upon-reaching-13th/m-p/517142#M145391 <P>So it seems it's really a 'magical'&nbsp; number then. Thank you sir for your reply.</P> Tue, 01 Sep 2020 02:01:56 GMT rajyah 2020-09-01T02:01:56Z https://community.splunk.com/t5/Splunk-Search/Wrong-results-on-stats-sum-or-addcoltotals-upon-reaching-13th/m-p/514395#M144365 <P>Hi,</P><P>The screenshot presented below shows that there are 2 pairs that negates each other which should equal to 0 on column1, same with column2. With that in mind, the total value should be 0, right? But upon rounding it up to 13th decimal value and beyond, it no longer equates to 0.</P><P> <span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Negative.PNG" style="width: 999px;"><img src="https://community.splunk.com/t5/image/serverpage/image-id/10303iECE6CF25FB3B1D2C/image-size/large?v=v2&amp;px=999" role="button" title="Negative.PNG" alt="Negative.PNG" /></span></P><P>&nbsp;</P><P>&nbsp;</P><P>I've attached a search query that will replicate the said issue stated above.</P><P>&nbsp;</P><P>&nbsp;</P><P>&nbsp;</P><LI-CODE lang="markup">| makeresults | eval column1=600.0000 | append [| makeresults | eval column1=390.0000] | append [| makeresults | eval column1=355.0000] | append [| makeresults | eval column1=575.0000] | append [| makeresults | eval column1=355.0000] | append [| makeresults | eval column1=590.0000] | append [| makeresults | eval column1=600.0000] | append [| makeresults | eval column1=355.0000] | append [| makeresults | eval column1=-600.0000] | append [| makeresults | eval column1=-590.0000] | append [| makeresults | eval column1=-355.0000] | append [| makeresults | eval column1=-575.0000] | append [| makeresults | eval column1=-355.0000] | append [| makeresults | eval column1=-390.0000] | append [| makeresults | eval column1=-600.0000] | append [| makeresults | eval column1=-355.0000] | eval column2=round(column1/1.12,20) , column1=round(column1,20) | addcoltotals</LI-CODE><P>&nbsp;</P><P>&nbsp;</P><P>Thank you.</P><P>&nbsp;</P><P>Regards,</P><P>Raj</P> Mon, 17 Aug 2020 07:11:12 GMT https://community.splunk.com/t5/Splunk-Search/Wrong-results-on-stats-sum-or-addcoltotals-upon-reaching-13th/m-p/514395#M144365 rajyah 2020-08-17T07:11:12Z https://community.splunk.com/t5/Splunk-Search/Wrong-results-on-stats-sum-or-addcoltotals-upon-reaching-13th/m-p/514440#M144384 <P>My first guess would be that this is the magic of floating point numbers at work. If you're having real life issues like the example you shared, you might want to look at using the sigfig() function:&nbsp;<A href="https://docs.splunk.com/Documentation/Splunk/8.0.5/SearchReference/MathematicalFunctions#sigfig.28X.29" target="_blank">https://docs.splunk.com/Documentation/Splunk/8.0.5/SearchReference/MathematicalFunctions#sigfig.28X.29</A></P> Mon, 17 Aug 2020 12:17:37 GMT https://community.splunk.com/t5/Splunk-Search/Wrong-results-on-stats-sum-or-addcoltotals-upon-reaching-13th/m-p/514440#M144384 FrankVl 2020-08-17T12:17:37Z https://community.splunk.com/t5/Splunk-Search/Wrong-results-on-stats-sum-or-addcoltotals-upon-reaching-13th/m-p/517142#M145391 <P>So it seems it's really a 'magical'&nbsp; number then. Thank you sir for your reply.</P> Tue, 01 Sep 2020 02:01:56 GMT https://community.splunk.com/t5/Splunk-Search/Wrong-results-on-stats-sum-or-addcoltotals-upon-reaching-13th/m-p/517142#M145391 rajyah 2020-09-01T02:01:56Z