<?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: Exact logistic in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Exact-logistic/m-p/24159#M5454</link>
    <description>Thanks!  That's what I have come to find out.  But it was suggested that I use it anyway.&lt;BR /&gt;
&lt;BR /&gt;
Here is the feedback I got from SAS:&lt;BR /&gt;
&lt;BR /&gt;
The "accuracy was lost" warning means that in compiling the exact conditional distribution, some frequencies became extremely large.  See "Exact Conditional Logistic Regression" in the PROC LOGISTIC documentation:&lt;BR /&gt;
&lt;BR /&gt;
  &lt;A href="http://support.sas.com/91doc/getDoc/statug.hlp/logistic_sect42.htm" target="_blank"&gt;http://support.sas.com/91doc/getDoc/statug.hlp/logistic_sect42.htm&lt;/A&gt; &lt;BR /&gt;
&lt;BR /&gt;
See also the comments toward the end of the "Computational Resources for Exact Conditional Logistic Regression":&lt;BR /&gt;
&lt;BR /&gt;
  &lt;A href="http://support.sas.com/91doc/getDoc/statug.hlp/logistic_sect49.htm" target="_blank"&gt;http://support.sas.com/91doc/getDoc/statug.hlp/logistic_sect49.htm&lt;/A&gt; &lt;BR /&gt;
&lt;BR /&gt;
As noted there, this message isn't necessarily problematic.  It's just letting you know that the exact counts could not be maintained.  Given the complexity of the exact algorithm, it's not really possible to track the cause of this message back to some feature in the data or model, but this problem is increasingly likely as the data set size increases. For data sets which are too large for the exact method, the Monte Carlo method (available in SAS 9.1 by specifying METHOD=NETWORKMC in EXACTOPTIONS) produces estimates of the exact p-values.</description>
    <pubDate>Thu, 10 Dec 2009 05:35:09 GMT</pubDate>
    <dc:creator>deleted_user</dc:creator>
    <dc:date>2009-12-10T05:35:09Z</dc:date>
    <item>
      <title>Exact logistic</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Exact-logistic/m-p/24155#M5450</link>
      <description>I am peforming proc logistic with the exact option.  I keep getting an error message that reads....&lt;BR /&gt;
&lt;BR /&gt;
The exact distribution contains frequencies larger than 9.0071993E15; accuracy was lost.&lt;BR /&gt;
&lt;BR /&gt;
The model runs and get odds ratios and confidence intervals (which are comparable to logistic without the exact option).  I am just confused as to why I am getting this error and what it means.  I only have 528 people in my sample.&lt;BR /&gt;
&lt;BR /&gt;
Any insight would be much appreciated.</description>
      <pubDate>Wed, 02 Dec 2009 03:23:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Exact-logistic/m-p/24155#M5450</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-12-02T03:23:05Z</dc:date>
    </item>
    <item>
      <title>Re: Exact logistic</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Exact-logistic/m-p/24156#M5451</link>
      <description>From the 9.2 documentation "If a frequency in the exact distribution is larger than the largest integer that can be held in double precision, a warning is printed to the SAS log. But since inaccuracies due to adding small numbers to these large frequencies might have little or no effect on the statistics, the exact computations continue."</description>
      <pubDate>Wed, 02 Dec 2009 16:57:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Exact-logistic/m-p/24156#M5451</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2009-12-02T16:57:56Z</dc:date>
    </item>
    <item>
      <title>Re: Exact logistic</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Exact-logistic/m-p/24157#M5452</link>
      <description>Thanks for the response.  I don't really understand that either lol.  Maybe I'm just dense.  I called SAS Tech Support and one of their logistic gurus is supposed to be getting back to me.  I'll post what they tell me.</description>
      <pubDate>Thu, 03 Dec 2009 01:19:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Exact-logistic/m-p/24157#M5452</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-12-03T01:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: Exact logistic</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Exact-logistic/m-p/24158#M5453</link>
      <description>Not dense, I heard a different question.  The underlying reason for the message is that the counters have reached a floating point overflow condition (remember that SAS uses floating point for all arithmetic, even addition of whole numbers).  So SAS is just telling you that it can on longer exactly represent the whole number in it's floating point system.  Now, why does that happen with the EXACT statement when you have "only" 528 observations.&lt;BR /&gt;
&lt;BR /&gt;
Actually, 500 is a LOT for an exact computation.  The computation is described in&lt;BR /&gt;
&lt;A href="http://support.sas.com/documentation/cdl/en/statug/63033/HTML/default/statug_logistic_sect045.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/statug/63033/HTML/default/statug_logistic_sect045.htm&lt;/A&gt;&lt;BR /&gt;
It's very nasty arithmetic. This statement is where the action is ".. created by summing over all binary sequences...  ".  It is basically saying that it has to look at all possible combinations in your data in order to get the estimate.  If you did it with brute force, you would have 2 raised to the 528 (2^528) power possibilities to compute (my calculator just generated an error message when I tried to get the total).  There are computational efficiencies, but it is still a LOT of computation to do.</description>
      <pubDate>Thu, 03 Dec 2009 15:27:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Exact-logistic/m-p/24158#M5453</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2009-12-03T15:27:43Z</dc:date>
    </item>
    <item>
      <title>Re: Exact logistic</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Exact-logistic/m-p/24159#M5454</link>
      <description>Thanks!  That's what I have come to find out.  But it was suggested that I use it anyway.&lt;BR /&gt;
&lt;BR /&gt;
Here is the feedback I got from SAS:&lt;BR /&gt;
&lt;BR /&gt;
The "accuracy was lost" warning means that in compiling the exact conditional distribution, some frequencies became extremely large.  See "Exact Conditional Logistic Regression" in the PROC LOGISTIC documentation:&lt;BR /&gt;
&lt;BR /&gt;
  &lt;A href="http://support.sas.com/91doc/getDoc/statug.hlp/logistic_sect42.htm" target="_blank"&gt;http://support.sas.com/91doc/getDoc/statug.hlp/logistic_sect42.htm&lt;/A&gt; &lt;BR /&gt;
&lt;BR /&gt;
See also the comments toward the end of the "Computational Resources for Exact Conditional Logistic Regression":&lt;BR /&gt;
&lt;BR /&gt;
  &lt;A href="http://support.sas.com/91doc/getDoc/statug.hlp/logistic_sect49.htm" target="_blank"&gt;http://support.sas.com/91doc/getDoc/statug.hlp/logistic_sect49.htm&lt;/A&gt; &lt;BR /&gt;
&lt;BR /&gt;
As noted there, this message isn't necessarily problematic.  It's just letting you know that the exact counts could not be maintained.  Given the complexity of the exact algorithm, it's not really possible to track the cause of this message back to some feature in the data or model, but this problem is increasingly likely as the data set size increases. For data sets which are too large for the exact method, the Monte Carlo method (available in SAS 9.1 by specifying METHOD=NETWORKMC in EXACTOPTIONS) produces estimates of the exact p-values.</description>
      <pubDate>Thu, 10 Dec 2009 05:35:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Exact-logistic/m-p/24159#M5454</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-12-10T05:35:09Z</dc:date>
    </item>
  </channel>
</rss>

