<node id="57638">
  <nid>57638</nid>
  <type>news</type>
  <uid>
    <user id="27279"><![CDATA[27279]]></user>
  </uid>
  <created>1173916800</created>
  <changed>1475895992</changed>
  <title><![CDATA[Bracket Tips at the 11th Hour]]></title>
  <body><![CDATA[<p>
</p><p><em>USA Today Blog</em> - March 15, 2007<br />No more fretting. No more over-analyzing that 8-9 game. Quit trying to figure out which 12 will be a 5. Just fill out that bracket. Here's a couple of things to remember. While it's nice to brag about pick that upset in the 12-5, 11-6, 13-4 games, those lower seeds rarely make it beyond the Sweet 16. The teams in the Sweet 16 and beyond are generally the higher seeded teams. So pick upsets carefully. You'll lose valuable points in your pool if you pick Albany to beat Virginia, and Virginia reaches the final eight.  But if you're really procrastinating with your picks, three ISyE professors came up with a system called "Logistic Regression/Markov Chain Model for NCAA Basketball." The program is "designed to use only basic scoreboard data (which two teams played, whose court they played on, and (in the "pure" version) what the margin of victory was)." The model is based on the research of Russian mathematician Andrey Markov. Don't scoff. The professors bring results. In the past seven NCAA tournaments, 22 of the 28 Final Four teams were ranked first or second in their region by the LRMC system.<br /><a href="http://blogs.usatoday.com/bracketracket/">http://blogs.usatoday.com/bracketracket/</a></p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2007-03-15T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_media>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[bchristopher@isye.gatech.edu]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[<strong>Barbara Christopher</strong><br />Industrial and Systems Engineering<br /><a href="http://www.gatech.edu/contact/index.html?id=bt3">Contact Barbara Christopher</a><br /><strong>404.385.3102</strong>]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>57458</item>
      </og_groups>
  <og_groups_both>
          <item>
        <![CDATA[Engineering]]>
      </item>
          <item>
        <![CDATA[Research]]>
      </item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>145</tid>
        <value><![CDATA[Engineering]]></value>
      </item>
          <item>
        <tid>135</tid>
        <value><![CDATA[Research]]></value>
      </item>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>57458</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[ISyE External News]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata>
      <![CDATA[]]>
  </field_userdata>
</node>
