<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Compare statement in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Compare-statement/m-p/298706#M20378</link>
    <description>&lt;P&gt;The Proc Compare option FUZZ allows you to tune how close values may be to consider equal and not make into the report.&lt;/P&gt;
&lt;P&gt;Try adding (or selecting the option) to set Fuzz=1e-10. That would consider values within 0.0000000001 to be equal. Since 1e-10 is larger than your shown e-14 range then likely most or your issue would be resolved.&lt;/P&gt;</description>
    <pubDate>Thu, 15 Sep 2016 16:00:58 GMT</pubDate>
    <dc:creator>ballardw</dc:creator>
    <dc:date>2016-09-15T16:00:58Z</dc:date>
    <item>
      <title>Compare statement</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Compare-statement/m-p/298672#M20373</link>
      <description>&lt;P&gt;Can anyone tell me why EG compare datasets will show a very small difference for an exact match and if there is a setting that might be doing this that I should change? I have attached a snapshot of the results. The Base plot variable is a calculated field BUT it is only created by adding .01 NOT multiplication.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BR /&gt;&lt;IMG src="https://communities.sas.com/t5/image/serverpage/image-id/12983iEB801603D2F655E8/image-size/large?v=1.0&amp;amp;px=600" border="0" alt="CompareExample.PNG" title="CompareExample.PNG" /&gt;</description>
      <pubDate>Thu, 15 Sep 2016 15:03:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Compare-statement/m-p/298672#M20373</guid>
      <dc:creator>CP2</dc:creator>
      <dc:date>2016-09-15T15:03:48Z</dc:date>
    </item>
    <item>
      <title>Re: Compare statement</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Compare-statement/m-p/298677#M20374</link>
      <description>&lt;P&gt;Hi CP2,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Seems a&amp;nbsp;Machine-Precision probleme. It's related with how number are saved in base 2 in a compute, for example 0.1 could not be represented without error in a compute.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It's happen in all compute with all numbers, a way to solve it could be a round(var,0.0000000000001). Since you are working with not many decimals, this should not affect your calcs and solve the problems with EG.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2016 15:10:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Compare-statement/m-p/298677#M20374</guid>
      <dc:creator>arodriguez</dc:creator>
      <dc:date>2016-09-15T15:10:24Z</dc:date>
    </item>
    <item>
      <title>Re: Compare statement</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Compare-statement/m-p/298706#M20378</link>
      <description>&lt;P&gt;The Proc Compare option FUZZ allows you to tune how close values may be to consider equal and not make into the report.&lt;/P&gt;
&lt;P&gt;Try adding (or selecting the option) to set Fuzz=1e-10. That would consider values within 0.0000000001 to be equal. Since 1e-10 is larger than your shown e-14 range then likely most or your issue would be resolved.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Sep 2016 16:00:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Compare-statement/m-p/298706#M20378</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2016-09-15T16:00:58Z</dc:date>
    </item>
  </channel>
</rss>

