<?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 Probit, concerns about small p-values of goodness-of-fit tests in Statistical Procedures</title>
    <link>https://communities.sas.com/t5/Statistical-Procedures/Proc-Probit-concerns-about-small-p-values-of-goodness-of-fit/m-p/722178#M34990</link>
    <description>&lt;P&gt;As always, when searching for SAS related topics, start with&amp;nbsp;&lt;A href="https://lexjansen.com/" target="_self"&gt;https://lexjansen.com/&lt;/A&gt;&amp;nbsp;.&amp;nbsp; The search function for the SAS documentation returns 185 hits for "logistic" AND "overdispersion".&amp;nbsp; Many of those are examples that can be worked through.&amp;nbsp; The Overdispersion example for PROC LOGISTIC says this:&amp;nbsp;&lt;/P&gt;
&lt;DIV class="xis-refProc"&gt;
&lt;DIV id="statug.logistic.logisticex9" class="AAsection"&gt;
&lt;P&gt;"If the link function and the model specification are correct and if there are no outliers, then the lack of fit might be due to &lt;FONT&gt;overdispersion&lt;/FONT&gt;."&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My concern is that a probit or logit link is not appropriate for this dataset, which is a model misspecification problem.&amp;nbsp; The lack of a plateau at the upper doses and the much sharper increase right at the beginning make this look more like a segmented linear model with 2 phases.&amp;nbsp; The residual plots from PROC LOGISTIC (using a probit link) show a big spike at about the 3rd record, which would be consistent with a segmented linear model.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Logistic (and probit) models are fit using maximum likelihood methods, so there really are not any sums of squares for calculating R-squared or R-squared like measures.&amp;nbsp; The deviation based chi-squared measures reported are much more appropriate.&amp;nbsp; Using the adjustments in PROC PROBIT is fine, provided the model is not misspecified.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SteveDenham&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Fri, 26 Feb 2021 15:33:46 GMT</pubDate>
    <dc:creator>SteveDenham</dc:creator>
    <dc:date>2021-02-26T15:33:46Z</dc:date>
    <item>
      <title>Proc Probit, concerns about small p-values of goodness-of-fit tests</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/Proc-Probit-concerns-about-small-p-values-of-goodness-of-fit/m-p/722017#M34983</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I used Probit regression to predict LC50. Here is my data and SAS code&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data d;
         infile cards ;
         input  Dose N Response @@;
         Observed= Response/N;
         output;
         return;
         datalines;
0	300	5
50	300	76
100	300	110
200	300	142
300	300	195
400	300	214
500	300	247
600	300	276
;
run;
proc probit data=D log10 plots=all optc;
      model Response/N=Dose / COVB lackfit inversecl itprint ;
      output out=B p=Prob stderr=stderr xbeta=xbeta;
run;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;The p-values of two goodness-of-fit are all &amp;lt;.0001. Then the outputs gave two notes&amp;nbsp;&lt;/P&gt;
&lt;DIV class="branch"&gt;
&lt;DIV align="left"&gt;
&lt;TABLE class="notecontent"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD class="l notebanner"&gt;Note:&lt;/TD&gt;
&lt;TD class="l notecontent"&gt;Since the Pearson Chi-Square exceeds the test level (0.1000), the covariance matrix has been multiplied by the heterogeneity factor (Pearson Chi-Square / DF) 7.1178.&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV align="left"&gt;
&lt;TABLE class="notecontent"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD class="l notebanner"&gt;Note:&lt;/TD&gt;
&lt;TD class="l notecontent"&gt;Please check to be sure that the large chi-square (p &amp;lt; 0.0001) is not caused by systematic departure from the model. A t value of 2.57 will be used in computing fiducial limits.&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;My question is that when p&amp;lt;.0001, are all the estimates and predicted results still valid after applying the two adjustments in the Notes above? If no, then why using those adjustments? If yes, how to explain to others who are concerned on the small p-values of goodness-of-fit tests?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks a lot!&lt;/P&gt;
&lt;P&gt;Rosie&lt;/P&gt;</description>
      <pubDate>Fri, 26 Feb 2021 00:22:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/Proc-Probit-concerns-about-small-p-values-of-goodness-of-fit/m-p/722017#M34983</guid>
      <dc:creator>RosieSAS</dc:creator>
      <dc:date>2021-02-26T00:22:19Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Probit, concerns about small p-values of goodness-of-fit tests</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/Proc-Probit-concerns-about-small-p-values-of-goodness-of-fit/m-p/722128#M34986</link>
      <description>&lt;P&gt;I think the estimates are as good as you will get with a probit model.&amp;nbsp; I think the overdispersion is due to the steep jump from the first dose level to the second, and then the relatively linear response after that, with little indication that an upper plateau has been reached with this dataset.&amp;nbsp; There are several examples of overdispersed logit/probit models being fit with PROC NLMIXED - perhaps that would be worth exploring.&amp;nbsp; If you get similar values for EC50 from both analyses, then you can have some reassurance that the PROC PROBIT results are acceptable.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SteveDenham&lt;/P&gt;</description>
      <pubDate>Fri, 26 Feb 2021 13:12:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/Proc-Probit-concerns-about-small-p-values-of-goodness-of-fit/m-p/722128#M34986</guid>
      <dc:creator>SteveDenham</dc:creator>
      <dc:date>2021-02-26T13:12:11Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Probit, concerns about small p-values of goodness-of-fit tests</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/Proc-Probit-concerns-about-small-p-values-of-goodness-of-fit/m-p/722139#M34987</link>
      <description>Thanks &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/15363"&gt;@SteveDenham&lt;/a&gt;. Do you mean when we got a small p-value of goodness-of-fit, or overdispersion happens, we are not sure if the ROC PROBIT results are reliable or not, even it tries some adjustments as the NOTES described? So it is better to try overdispersed logit/probit models being fit with PROC NLMIXED to reassure the PROC PROBIT results are acceptable. I found some examples using PROC NLMIXED to fit logit or probit model, but not overdispersion model. Can you suggest some links?&lt;BR /&gt;&lt;BR /&gt;Can we use pseudo R2 to assess the goodness-of-fit of the estimate from PROC PROBIT?  Is the formula pseudoR2 = 1 - (SSerror/SStotal(corrected)) correct? If yes, how to get the values of SSerror and SStotal(corrected)? PROC PROBIT doesn't report ANOVA table.</description>
      <pubDate>Fri, 26 Feb 2021 13:50:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/Proc-Probit-concerns-about-small-p-values-of-goodness-of-fit/m-p/722139#M34987</guid>
      <dc:creator>RosieSAS</dc:creator>
      <dc:date>2021-02-26T13:50:24Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Probit, concerns about small p-values of goodness-of-fit tests</title>
      <link>https://communities.sas.com/t5/Statistical-Procedures/Proc-Probit-concerns-about-small-p-values-of-goodness-of-fit/m-p/722178#M34990</link>
      <description>&lt;P&gt;As always, when searching for SAS related topics, start with&amp;nbsp;&lt;A href="https://lexjansen.com/" target="_self"&gt;https://lexjansen.com/&lt;/A&gt;&amp;nbsp;.&amp;nbsp; The search function for the SAS documentation returns 185 hits for "logistic" AND "overdispersion".&amp;nbsp; Many of those are examples that can be worked through.&amp;nbsp; The Overdispersion example for PROC LOGISTIC says this:&amp;nbsp;&lt;/P&gt;
&lt;DIV class="xis-refProc"&gt;
&lt;DIV id="statug.logistic.logisticex9" class="AAsection"&gt;
&lt;P&gt;"If the link function and the model specification are correct and if there are no outliers, then the lack of fit might be due to &lt;FONT&gt;overdispersion&lt;/FONT&gt;."&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My concern is that a probit or logit link is not appropriate for this dataset, which is a model misspecification problem.&amp;nbsp; The lack of a plateau at the upper doses and the much sharper increase right at the beginning make this look more like a segmented linear model with 2 phases.&amp;nbsp; The residual plots from PROC LOGISTIC (using a probit link) show a big spike at about the 3rd record, which would be consistent with a segmented linear model.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Logistic (and probit) models are fit using maximum likelihood methods, so there really are not any sums of squares for calculating R-squared or R-squared like measures.&amp;nbsp; The deviation based chi-squared measures reported are much more appropriate.&amp;nbsp; Using the adjustments in PROC PROBIT is fine, provided the model is not misspecified.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SteveDenham&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 26 Feb 2021 15:33:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Statistical-Procedures/Proc-Probit-concerns-about-small-p-values-of-goodness-of-fit/m-p/722178#M34990</guid>
      <dc:creator>SteveDenham</dc:creator>
      <dc:date>2021-02-26T15:33:46Z</dc:date>
    </item>
  </channel>
</rss>

