<?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: Proc logistics warning: Ridging has failed in Statistical Procedures</title>
    <link>https://communities.sas.com/t5/Statistical-Procedures/Proc-logistics-warning-Ridging-has-failed/m-p/17713#M506</link>
    <description>Amit,&lt;BR /&gt;
&lt;BR /&gt;
The warning in the log is just indicating that the iterative maximum likelihood optimization method for fitting the model failed to find a solution.  As with any optimization program, this can happen for some models on some data sets.  The message suggests some ways you can change the optimizer which *may* allow the procedure to find a solution.  In fact, if the procedure does not converge, it presents the results based on the last iteration. This is not the maximum likelihood solution, so you may not even want to use the results.  To fix the problem, you can try the suggested options. If they don't work, you may have to change your model... probably by reducing the number of parameters in it.</description>
    <pubDate>Tue, 17 Nov 2009 04:33:11 GMT</pubDate>
    <dc:creator>jain</dc:creator>
    <dc:date>2009-11-17T04:33:11Z</dc:date>
    <item>
      <title>Proc logistics warning: Ridging has failed</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/Proc-logistics-warning-Ridging-has-failed/m-p/17712#M505</link>
      <description>Hi,&lt;BR /&gt;
       I am running  proc logistics with backward selection. I am getting warning that Ridging has failed.&lt;BR /&gt;
       Can anyone explain what the warning means and some solution.&lt;BR /&gt;
     &lt;BR /&gt;
       I appreciate all your help.&lt;BR /&gt;
&lt;BR /&gt;
 Thanks,&lt;BR /&gt;
&lt;BR /&gt;
Amit&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;CODE:&lt;/B&gt; &lt;BR /&gt;
&lt;BR /&gt;
  proc logistic data=out.train1 NAMELEN=32;&lt;BR /&gt;
    model del123_target (event = '1') = &amp;amp;VarName&lt;BR /&gt;
         / selection=backward fast sls=0.1;&lt;BR /&gt;
     run;&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;LOG:&lt;/B&gt; &lt;BR /&gt;
&lt;BR /&gt;
NOTE: PROC LOGISTIC is modeling the probability that del123_target=1.&lt;BR /&gt;
WARNING: Ridging has failed to improve the loglikelihood in Step 0. You may want to&lt;BR /&gt;
         use a different ridging technique (RIDGING= option), or switch to using&lt;BR /&gt;
         linesearch to reduce the step size (RIDGING=NONE), or specify a new set of&lt;BR /&gt;
         initial estimates (INEST= option).&lt;BR /&gt;
WARNING: The LOGISTIC procedure continues in spite of the above warning. Results&lt;BR /&gt;
         shown are based on the last maximum likelihood iteration. Validity of the&lt;BR /&gt;
         model fit is questionable.&lt;BR /&gt;
NOTE: Convergence criterion (GCONV=1E-8) satisfied in Step 1.&lt;BR /&gt;
NOTE: There were 1315176 observations read from the data set OUT.TRAIN1.&lt;BR /&gt;
NOTE: PROCEDURE LOGISTIC used (Total process time):&lt;BR /&gt;
      real time           8:19.57&lt;BR /&gt;
      cpu time            4:52.89</description>
      <pubDate>Mon, 16 Nov 2009 21:44:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/Proc-logistics-warning-Ridging-has-failed/m-p/17712#M505</guid>
      <dc:creator>AmitKB</dc:creator>
      <dc:date>2009-11-16T21:44:22Z</dc:date>
    </item>
    <item>
      <title>Re: Proc logistics warning: Ridging has failed</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/Proc-logistics-warning-Ridging-has-failed/m-p/17713#M506</link>
      <description>Amit,&lt;BR /&gt;
&lt;BR /&gt;
The warning in the log is just indicating that the iterative maximum likelihood optimization method for fitting the model failed to find a solution.  As with any optimization program, this can happen for some models on some data sets.  The message suggests some ways you can change the optimizer which *may* allow the procedure to find a solution.  In fact, if the procedure does not converge, it presents the results based on the last iteration. This is not the maximum likelihood solution, so you may not even want to use the results.  To fix the problem, you can try the suggested options. If they don't work, you may have to change your model... probably by reducing the number of parameters in it.</description>
      <pubDate>Tue, 17 Nov 2009 04:33:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/Proc-logistics-warning-Ridging-has-failed/m-p/17713#M506</guid>
      <dc:creator>jain</dc:creator>
      <dc:date>2009-11-17T04:33:11Z</dc:date>
    </item>
    <item>
      <title>Re: Proc logistics warning: Ridging has failed</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/Proc-logistics-warning-Ridging-has-failed/m-p/17714#M507</link>
      <description>SELECTION=BACKWARD is usually a bad idea when there are many candidate effects in the model.  The reason it is a bad idea is that the method starts with the most complex model which includes all of the candidate effects.  This model is usually so complex and makes the data so sparse that the maximum likelihood solution does not exist.  Better to use SELECTION=FORWARD or STEPWISE which starts with no effects (or only those forced by the INCLUDE= option) and built up a model.</description>
      <pubDate>Mon, 23 Nov 2009 20:28:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/Proc-logistics-warning-Ridging-has-failed/m-p/17714#M507</guid>
      <dc:creator>StatDave</dc:creator>
      <dc:date>2009-11-23T20:28:56Z</dc:date>
    </item>
  </channel>
</rss>

