<?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: Alert: Failed to converge(step-halving-limit) error. What am I missing? in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/Alert-Failed-to-converge-step-halving-limit-error-What-am-I/m-p/37100#M21781</link>
    <description>&lt;P&gt;The error you are encountering in the Stepwise platform indicates that there is complete or quasi-complete separation. This is a phenomenon that can occur for binary responses, when one predictor (or a combination of predictors) can perfectly predict the outcome. In this case the maximum likelihood estimates don't exist. There is a SAS note that addresses this issue with logistic models on our website at &lt;A href="http://support.sas.com/kb/22/599.html" target="_blank"&gt;&lt;U&gt;&lt;FONT color="#0000ff"&gt;http://support.sas.com/kb/22/599.html&lt;/FONT&gt;&lt;/U&gt;&lt;/A&gt;. Although the note addresses SAS, the concepts discussed there are applicable to any software. &lt;/P&gt;</description>
    <pubDate>Mon, 13 Mar 2017 17:09:14 GMT</pubDate>
    <dc:creator>susan_walsh1</dc:creator>
    <dc:date>2017-03-13T17:09:14Z</dc:date>
    <item>
      <title>Alert: Failed to converge(step-halving-limit) error. What am I missing?</title>
      <link>https://community.jmp.com/t5/Discussions/Alert-Failed-to-converge-step-halving-limit-error-What-am-I/m-p/36389#M21377</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;When I do the below steps with a &lt;STRONG&gt;categorical Y&lt;/STRONG&gt; variable:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Select Analyze &amp;gt; Fit Model.&lt;/P&gt;&lt;P&gt;Select the response column and click Y, Response.&lt;/P&gt;&lt;P&gt;Select the predictor colulmns and click Add or use one of the Macros if you want to include higher order effects.&lt;/P&gt;&lt;P&gt;Click the button next to Personality and select Stepwise.&lt;/P&gt;&lt;P&gt;Click Run.&lt;/P&gt;&lt;P&gt;Click Minimum BIC and select P-Value Threshold.&lt;/P&gt;&lt;P&gt;Click Forward and select Mixed.&lt;/P&gt;&lt;P&gt;Click Go.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I get&amp;nbsp;Alert: Failed to converge(step-halving-limit) error&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I want to have a mixed stepwise regression.&lt;/P&gt;&lt;P&gt;What am I missing?&lt;/P&gt;</description>
      <pubDate>Sun, 26 Feb 2017 17:48:13 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Alert-Failed-to-converge-step-halving-limit-error-What-am-I/m-p/36389#M21377</guid>
      <dc:creator>ShriHanuman</dc:creator>
      <dc:date>2017-02-26T17:48:13Z</dc:date>
    </item>
    <item>
      <title>Re: Alert: Failed to converge(step-halving-limit) error. What am I missing?</title>
      <link>https://community.jmp.com/t5/Discussions/Alert-Failed-to-converge-step-halving-limit-error-What-am-I/m-p/37100#M21781</link>
      <description>&lt;P&gt;The error you are encountering in the Stepwise platform indicates that there is complete or quasi-complete separation. This is a phenomenon that can occur for binary responses, when one predictor (or a combination of predictors) can perfectly predict the outcome. In this case the maximum likelihood estimates don't exist. There is a SAS note that addresses this issue with logistic models on our website at &lt;A href="http://support.sas.com/kb/22/599.html" target="_blank"&gt;&lt;U&gt;&lt;FONT color="#0000ff"&gt;http://support.sas.com/kb/22/599.html&lt;/FONT&gt;&lt;/U&gt;&lt;/A&gt;. Although the note addresses SAS, the concepts discussed there are applicable to any software. &lt;/P&gt;</description>
      <pubDate>Mon, 13 Mar 2017 17:09:14 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Alert-Failed-to-converge-step-halving-limit-error-What-am-I/m-p/37100#M21781</guid>
      <dc:creator>susan_walsh1</dc:creator>
      <dc:date>2017-03-13T17:09:14Z</dc:date>
    </item>
  </channel>
</rss>

