<?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: categorical interactions in proc logistics in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667464#M199876</link>
    <description>Thanks @PaigeMilller.&lt;BR /&gt;I had run an initial data step and included the statement: Health_sex=Health*sex for the interaction term. So Health_sex in the model is representing my interaction term.&lt;BR /&gt;I asked the question because when I split the dataset into male and female and run the same model separately, but excluding bsex and the interaction term, my odds ratios don't appear to be giving a similar picture as the predicted probability plots?</description>
    <pubDate>Tue, 07 Jul 2020 15:11:31 GMT</pubDate>
    <dc:creator>catch18</dc:creator>
    <dc:date>2020-07-07T15:11:31Z</dc:date>
    <item>
      <title>categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667374#M199833</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I am trying to visualise a significant categorical interaction in proc logistics via the below code.&lt;/P&gt;
&lt;P&gt;Health is categorized as 0 - low, 1- med, 2 -high, bsex is 0- female, 1-male.&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;ODS&lt;/FONT&gt; &lt;FONT face="Courier New" size="2" color="#0000ff"&gt;graphics&lt;/FONT&gt; &lt;FONT face="Courier New" size="2" color="#0000ff"&gt;on&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Courier New" size="2" color="#000080"&gt;&lt;STRONG&gt;PROC&lt;/STRONG&gt;&lt;/FONT&gt; &lt;STRONG&gt;&lt;FONT face="Courier New" size="2" color="#000080"&gt;logistic&lt;/FONT&gt;&lt;/STRONG&gt; &lt;FONT face="Courier New" size="2" color="#0000ff"&gt;data&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;=work&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;class&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt; Primiparity (ref="yes")&amp;nbsp;Health (ref="2)&amp;nbsp;bsex (ref="0")/&lt;/FONT&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;param&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;=ref;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;MODEL&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt; LGAc (&lt;/FONT&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;event&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;=&lt;/FONT&gt;&lt;FONT face="Courier New" size="2" color="#800080"&gt;'1'&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;) = Health Primiparity bsex Health_sex/noor;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;effectplot&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt; / &lt;/FONT&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;at&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;(bSex=all) &lt;/FONT&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;noobs&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;effectplot&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt; slicefit(&lt;/FONT&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;sliceby&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;=bSex &lt;/FONT&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;plotby&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;=Health)/ &lt;/FONT&gt;&lt;FONT face="Courier New" size="2" color="#0000ff"&gt;noobs&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Courier New" size="2" color="#000080"&gt;&lt;STRONG&gt;RUN&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT face="Courier New" size="2"&gt;;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Would this code be right?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jul 2020 08:11:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667374#M199833</guid>
      <dc:creator>catch18</dc:creator>
      <dc:date>2020-07-07T08:11:22Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667393#M199846</link>
      <description>&lt;P&gt;You code does not include an interaction in the MODEL statement, so I don't think it is right.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jul 2020 10:34:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667393#M199846</guid>
      <dc:creator>PaigeMiller</dc:creator>
      <dc:date>2020-07-07T10:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667464#M199876</link>
      <description>Thanks @PaigeMilller.&lt;BR /&gt;I had run an initial data step and included the statement: Health_sex=Health*sex for the interaction term. So Health_sex in the model is representing my interaction term.&lt;BR /&gt;I asked the question because when I split the dataset into male and female and run the same model separately, but excluding bsex and the interaction term, my odds ratios don't appear to be giving a similar picture as the predicted probability plots?</description>
      <pubDate>Tue, 07 Jul 2020 15:11:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667464#M199876</guid>
      <dc:creator>catch18</dc:creator>
      <dc:date>2020-07-07T15:11:31Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667469#M199878</link>
      <description>&lt;P&gt;If health and sex are categorical variables, then Health*Sex is meaningless code, you can't multiply health times sex.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Furthermore, even if you create the variable health_sex somehow, unless you do it properly you do not get the interaction. So let's clear this up first before we get into splitting the data sets.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jul 2020 15:22:49 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667469#M199878</guid>
      <dc:creator>PaigeMiller</dc:creator>
      <dc:date>2020-07-07T15:22:49Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667471#M199879</link>
      <description>Great, so what do you suggest?</description>
      <pubDate>Tue, 07 Jul 2020 15:25:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667471#M199879</guid>
      <dc:creator>catch18</dc:creator>
      <dc:date>2020-07-07T15:25:02Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667482#M199884</link>
      <description>&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;MODEL LGAc (event='1') = Health Primiparity bsex Health*sex/noor;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;In a model statement, constructs with an * do not indicate multiplication, it indicates creating an interaction (properly).&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jul 2020 15:37:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667482#M199884</guid>
      <dc:creator>PaigeMiller</dc:creator>
      <dc:date>2020-07-07T15:37:26Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667485#M199886</link>
      <description>Yes, but when I had run this initially without creating the data step. SAS told me the variable Health*sex did not exist?&lt;BR /&gt;Thanks.</description>
      <pubDate>Tue, 07 Jul 2020 15:41:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667485#M199886</guid>
      <dc:creator>catch18</dc:creator>
      <dc:date>2020-07-07T15:41:45Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667488#M199888</link>
      <description>&lt;P&gt;Show me the log from when you try this. I want to see the code as seen in the log, plus ERRORs, WARNINGs and NOTEs for this PROC step. Do not chop anything out of the log for this PROC step.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please format the log so that it is readable. You do this by copying the log as text, then pasting it into the window that appears after you click on the &amp;lt;/&amp;gt; icon. DO NOT SKIP THIS STEP.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jul 2020 15:46:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667488#M199888</guid>
      <dc:creator>PaigeMiller</dc:creator>
      <dc:date>2020-07-07T15:46:55Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667513#M199901</link>
      <description>Thanks &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/10892"&gt;@PaigeMiller&lt;/a&gt;!&lt;BR /&gt;It appears to have run without a problem. I'm not sure why I thought I had to create the variable first.&lt;BR /&gt;I did run the same data with proc reg earlier on and this was the log:&lt;BR /&gt;1406  PROC reg data= work;*Final model;&lt;BR /&gt;1407  MODEL StdTotalsubcut_b_cond = StdHealth Primiparity bsex Health*bsex;&lt;BR /&gt;                                                                                                                       -&lt;BR /&gt;                                                                                                                      22&lt;BR /&gt;                                                                                                                      200&lt;BR /&gt;NOTE: The previous statement has been deleted.&lt;BR /&gt;ERROR 22-322: Syntax error, expecting one of the following: a name, ;, -, /, :, _ALL_,&lt;BR /&gt;              _CHARACTER_, _CHAR_, _NUMERIC_, {.&lt;BR /&gt;ERROR 200-322: The symbol is not recognized and will be ignored.&lt;BR /&gt;1408  RUN;&lt;BR /&gt;&lt;BR /&gt;WARNING: No variables specified for an SSCP matrix. Execution terminating.&lt;BR /&gt;NOTE: PROCEDURE REG used (Total process time):&lt;BR /&gt;      real time           0.00 seconds&lt;BR /&gt;      cpu time            0.00 seconds&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Jul 2020 17:32:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667513#M199901</guid>
      <dc:creator>catch18</dc:creator>
      <dc:date>2020-07-07T17:32:26Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667516#M199902</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/293117"&gt;@catch18&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;Thanks &lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/10892"&gt;@PaigeMiller&lt;/a&gt;!&lt;BR /&gt;It appears to have run without a problem. I'm not sure why I thought I had to create the variable first.&lt;BR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;So, are we done?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jul 2020 17:35:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667516#M199902</guid>
      <dc:creator>PaigeMiller</dc:creator>
      <dc:date>2020-07-07T17:35:27Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667520#M199903</link>
      <description>So I rerun the code again with interaction term as discussed and this is the log;&lt;BR /&gt;NOTE: PROC LOGISTIC is modeling the probability that LGAc='1'.&lt;BR /&gt;NOTE: Convergence criterion (GCONV=1E-8) satisfied.&lt;BR /&gt;NOTE: Under full-rank parameterizations, Type 3 effect tests are replaced by joint tests. The&lt;BR /&gt;      joint test for an effect is a test that all the parameters associated with that effect&lt;BR /&gt;      are zero. Such joint tests might not be equivalent to Type 3 effect tests under GLM&lt;BR /&gt;      parameterization.&lt;BR /&gt;ERROR: The specified plot type does not support the variable configuration.&lt;BR /&gt;NOTE: The SAS System stopped processing this step because of errors.&lt;BR /&gt;NOTE: There were 283 observations read from the data set TARGET.PATTERN_MORPH_LOG.&lt;BR /&gt;NOTE: PROCEDURE LOGISTIC used (Total process time):&lt;BR /&gt;      real time           1.07 seconds&lt;BR /&gt;      cpu time            0.73 seconds&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Jul 2020 17:43:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667520#M199903</guid>
      <dc:creator>catch18</dc:creator>
      <dc:date>2020-07-07T17:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667521#M199904</link>
      <description>&lt;P&gt;Hi ... I gave specific instructions on how to provide the LOG from a SAS program. Please follow those instructions.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jul 2020 17:47:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667521#M199904</guid>
      <dc:creator>PaigeMiller</dc:creator>
      <dc:date>2020-07-07T17:47:06Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667523#M199906</link>
      <description>&lt;PRE&gt;NOTE: PROC LOGISTIC is modeling the probability that LGAc='1'.
NOTE: Convergence criterion (GCONV=1E-8) satisfied.
NOTE: Under full-rank parameterizations, Type 3 effect tests are replaced by joint tests. The
      joint test for an effect is a test that all the parameters associated with that effect
      are zero. Such joint tests might not be equivalent to Type 3 effect tests under GLM
      parameterization.
ERROR: The specified plot type does not support the variable configuration.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: There were 283 observations read from the data set TARGET.PATTERN_MORPH_LOG.
NOTE: PROCEDURE LOGISTIC used (Total process time):
      real time           1.07 seconds
      cpu time            0.73 seconds

&lt;/PRE&gt;</description>
      <pubDate>Tue, 07 Jul 2020 17:51:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667523#M199906</guid>
      <dc:creator>catch18</dc:creator>
      <dc:date>2020-07-07T17:51:51Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667524#M199907</link>
      <description>Is this any better? Thanks</description>
      <pubDate>Tue, 07 Jul 2020 17:53:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667524#M199907</guid>
      <dc:creator>catch18</dc:creator>
      <dc:date>2020-07-07T17:53:00Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667526#M199909</link>
      <description>&lt;PRE&gt;1409  ODS graphics on;
1410  PROC logistic data= work;*Final model;
1411  class Primiparity(ref="Yes") Health (ref="2") bsex (ref="0")/param=ref;
1412  MODEL LGAc (event='1') = Health Primiparity bsex Health*bsex/noor;
1413  effectplot / at(bSex=all) noobs;
1414  effectplot slicefit(sliceby=bSex plotby=Health)/ noobs;
1415  RUN;

NOTE: PROC LOGISTIC is modeling the probability that LGAc='1'.
NOTE: Convergence criterion (GCONV=1E-8) satisfied.
NOTE: Under full-rank parameterizations, Type 3 effect tests are replaced by joint tests. The
      joint test for an effect is a test that all the parameters associated with that effect
      are zero. Such joint tests might not be equivalent to Type 3 effect tests under GLM
      parameterization.
ERROR: The specified plot type does not support the variable configuration.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: There were 283 observations read from the data set TARGET.PATTERN_MORPH_LOG.
NOTE: PROCEDURE LOGISTIC used (Total process time):
      real time           1.07 seconds
      cpu time            0.73 seconds

&lt;/PRE&gt;</description>
      <pubDate>Tue, 07 Jul 2020 17:58:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667526#M199909</guid>
      <dc:creator>catch18</dc:creator>
      <dc:date>2020-07-07T17:58:41Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667538#M199914</link>
      <description>&lt;P&gt;I'm guessing here, but at line 1413, you don't specify a plot type after EFFECTPLOT, and the default plot doesn't allow the AT option.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jul 2020 18:47:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667538#M199914</guid>
      <dc:creator>PaigeMiller</dc:creator>
      <dc:date>2020-07-07T18:47:55Z</dc:date>
    </item>
    <item>
      <title>Re: categorical interactions in proc logistics</title>
      <link>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667547#M199922</link>
      <description>If I remove line 1413 together with the AT option I still get the same error message</description>
      <pubDate>Tue, 07 Jul 2020 19:34:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/categorical-interactions-in-proc-logistics/m-p/667547#M199922</guid>
      <dc:creator>catch18</dc:creator>
      <dc:date>2020-07-07T19:34:21Z</dc:date>
    </item>
  </channel>
</rss>

