<?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 Follow up--&amp;gt;Re: nominal logistic fit in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/335466#M58289</link>
    <description>&lt;P&gt;Just want to clarify this response that is in the link below.&amp;nbsp; The original question relates to unstable parameter estimates in nominal logistic regression.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;"&lt;EM&gt;This is a common issue. It is caused by some parameters of the model becoming theoretically infinite. This can happen when the model perfectly predicts the response or if there are more parameters in the model than can be estimated by the data (that is, with sparse data, where "sparse" means that there are few or no repeats of each setting of the covariates). One solution is to reduce the number of variables and/or change continuous variables to categorical. There is no way to know which variable to eliminate or categorize because all are involved simultaneously. The resulting model is usually good at classifying observations, but inferences about the parameters should be avoided."&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do I take it that even with unstable, biased or zeroed parameter estimates, the model may still be used if only for classifying?&lt;/P&gt;</description>
    <pubDate>Thu, 19 Nov 2020 06:17:54 GMT</pubDate>
    <dc:creator>TCM</dc:creator>
    <dc:date>2020-11-19T06:17:54Z</dc:date>
    <item>
      <title>nominal logistic fit</title>
      <link>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18840#M17168</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi , In nominal logistic fit. I get a significant model, all parameters are significant by the effect LRT. but all the parameters estimations are not significant.&amp;nbsp; how can it be??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jun 2016 08:25:30 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18840#M17168</guid>
      <dc:creator>eldad_galili</dc:creator>
      <dc:date>2016-06-02T08:25:30Z</dc:date>
    </item>
    <item>
      <title>Re: nominal logistic fit</title>
      <link>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18841#M17169</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The cause is collinearity among the independent variables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The overall test just says that the model including all the variables is better than the mean of the response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The test for significance of the individual parameters is conditioned on all the other parameters in the model.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there is substantial correlation between two independent variables, both important in explaining the response, then neither will be significant with the other in the model.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Collinearity can be more complicated than just two variables being correlated.&amp;nbsp; It can happened if one variable is correlated with a linear combination of several other variables which is common when one has many independent variables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The solution in general is to identify the subsets of variables that are highly correlated among each other and use a subset that is not too correlated.&lt;/P&gt;&lt;P&gt;Not being a JMP expert, more SAS, I will leave it to others to give you more specific advice on how do identify the highly correlated subsets&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some ideas that come to mind are looking at pairwise correlations.&amp;nbsp; Another idea is to use the partition platform to pick candidate independent variables.&lt;/P&gt;&lt;P&gt;If your goal is prediction, then using recursive partitioning is fine.&amp;nbsp; If you goal is inference, using recursive partitioning to select variables will bias the p-values small and make any inference suspect.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jun 2016 17:34:33 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18841#M17169</guid>
      <dc:creator>robertlucas1972</dc:creator>
      <dc:date>2016-06-02T17:34:33Z</dc:date>
    </item>
    <item>
      <title>Re: nominal logistic fit</title>
      <link>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18842#M17170</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are your parameter estimates labeled "unstable"? If so, you might want to take a look at this JMP note:&lt;A href="http://www.jmp.com/support/notes/36/686.html" title="http://www.jmp.com/support/notes/36/686.html"&gt;36686 - When I run nominal or ordinal logistic regression in JMP®, I receive parameter estimates labelled as "Unstable."…&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Jun 2016 12:43:56 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18842#M17170</guid>
      <dc:creator>susan_walsh1</dc:creator>
      <dc:date>2016-06-03T12:43:56Z</dc:date>
    </item>
    <item>
      <title>Re: nominal logistic fit</title>
      <link>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18843#M17171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Another potential approach if multicollinearity among your predictor variables is an issue is, if you are running JMP Pro, the Generalized Regression Lasso/Elastic Net personalities are viable modeling options as well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Jun 2016 17:40:40 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18843#M17171</guid>
      <dc:creator>Peter_Bartell</dc:creator>
      <dc:date>2016-06-03T17:40:40Z</dc:date>
    </item>
    <item>
      <title>Re: nominal logistic fit</title>
      <link>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18844#M17172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you very much for the replay, I will check if I have &lt;SPAN style="color: #555555; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 13px; background-color: #f2f2f2;"&gt;correlation between my parameters&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Jun 2016 11:56:37 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18844#M17172</guid>
      <dc:creator>eldad_galili</dc:creator>
      <dc:date>2016-06-05T11:56:37Z</dc:date>
    </item>
    <item>
      <title>Re: nominal logistic fit</title>
      <link>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18845#M17173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, but I am not using the pro version, too much money &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_emote jive_macro" src="https://community.jmp.com/7.0.4.3b79b96/images/emoticons/happy.png"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Jun 2016 12:01:25 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/18845#M17173</guid>
      <dc:creator>eldad_galili</dc:creator>
      <dc:date>2016-06-05T12:01:25Z</dc:date>
    </item>
    <item>
      <title>Follow up--&gt;Re: nominal logistic fit</title>
      <link>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/335466#M58289</link>
      <description>&lt;P&gt;Just want to clarify this response that is in the link below.&amp;nbsp; The original question relates to unstable parameter estimates in nominal logistic regression.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;"&lt;EM&gt;This is a common issue. It is caused by some parameters of the model becoming theoretically infinite. This can happen when the model perfectly predicts the response or if there are more parameters in the model than can be estimated by the data (that is, with sparse data, where "sparse" means that there are few or no repeats of each setting of the covariates). One solution is to reduce the number of variables and/or change continuous variables to categorical. There is no way to know which variable to eliminate or categorize because all are involved simultaneously. The resulting model is usually good at classifying observations, but inferences about the parameters should be avoided."&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do I take it that even with unstable, biased or zeroed parameter estimates, the model may still be used if only for classifying?&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2020 06:17:54 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/335466#M58289</guid>
      <dc:creator>TCM</dc:creator>
      <dc:date>2020-11-19T06:17:54Z</dc:date>
    </item>
    <item>
      <title>Re: Follow up--&gt;Re: nominal logistic fit</title>
      <link>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/335483#M58297</link>
      <description>&lt;P&gt;These warnings and indicators suggest a poor model. I would not use it to predict outcomes (i.e., classify). I would correct the poor conditions and verify the model assumptions first.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2020 13:50:02 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/nominal-logistic-fit/m-p/335483#M58297</guid>
      <dc:creator>Mark_Bailey</dc:creator>
      <dc:date>2020-11-19T13:50:02Z</dc:date>
    </item>
  </channel>
</rss>

