<node id="627401">
  <nid>627401</nid>
  <type>event</type>
  <uid>
    <user id="27707"><![CDATA[27707]]></user>
  </uid>
  <created>1570642632</created>
  <changed>1570642632</changed>
  <title><![CDATA[MS defense by Heather A Handy]]></title>
  <body><![CDATA[<p><strong>Name:</strong>&nbsp;<strong>Heather A. Handy</strong></p>

<p><strong>Master&rsquo;s&nbsp;Thesis&nbsp;Defense Meeting</strong><br />
<strong>Date:</strong>&nbsp;Monday, October 21, 2019<br />
<strong>Time:</strong>&nbsp;11:00 am<br />
<strong>Location:&nbsp;</strong>J.S. Coon Building, Room 148<br />
&nbsp;<br />
<strong>Advisor:</strong><br />
Susan Embretson, Ph.D. (Georgia Tech)<br />
&nbsp;<br />
<strong>Thesis&nbsp;Committee Members:</strong><br />
Susan Embretson, Ph.D. (Georgia Tech)<br />
Rick Thomas, Ph.D. (Georgia Tech)<br />
Michael Hunter, Ph.D. (Georgia Tech)<br />
&nbsp;<br />
<strong>Title:&nbsp;A Study of a Fit Index for Explanatory Item Response Theory Models</strong></p>

<p>&nbsp;</p>

<p><strong>Abstract:</strong></p>

<p>Likelihood ratio chi square tests for nested models are typically used to determine model significance.&nbsp; Multiple correlations of item difficulties estimated with the explanatory predictors are often used to provide further information about model quality. However, this approach is not statistically justifiable, since the effective sample size becomes the number of items. Applying explanatory item response theory (IRT) models is advantageous when designing and selecting items. A simulation study was conducted to compare an explanatory item response theory fit statistic, &Delta;<sup>2</sup> (Embretson, 1997; 2016), to traditionally used fit indices (nested model likelihoods and limited information multiple correlations) for assessing model quality.&nbsp; Simulation conditions include varying test length, item difficulty and the number of predictors.</p>
]]></body>
  <field_summary_sentence>
    <item>
      <value><![CDATA[A Study of a Fit Index for Explanatory Item Response Theory Models]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_time>
    <item>
      <value><![CDATA[2019-10-21T12:00:00-04:00]]></value>
      <value2><![CDATA[2019-10-21T14:00:00-04:00]]></value2>
      <rrule><![CDATA[]]></rrule>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_time>
  <field_fee>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_fee>
  <field_extras>
      </field_extras>
  <field_audience>
          <item>
        <value><![CDATA[Faculty/Staff]]></value>
      </item>
          <item>
        <value><![CDATA[Public]]></value>
      </item>
          <item>
        <value><![CDATA[Graduate students]]></value>
      </item>
          <item>
        <value><![CDATA[Undergraduate students]]></value>
      </item>
      </field_audience>
  <field_media>
      </field_media>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_phone>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_phone>
  <field_url>
    <item>
      <url><![CDATA[]]></url>
      <title><![CDATA[]]></title>
            <attributes><![CDATA[]]></attributes>
    </item>
  </field_url>
  <field_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_email>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>221981</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Graduate Studies]]></item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>1788</tid>
        <value><![CDATA[Other/Miscellaneous]]></value>
      </item>
      </field_categories>
  <field_keywords>
          <item>
        <tid>111531</tid>
        <value><![CDATA[ms defense]]></value>
      </item>
      </field_keywords>
  <userdata><![CDATA[]]></userdata>
</node>
