<node id="629408">
  <nid>629408</nid>
  <type>event</type>
  <uid>
    <user id="27707"><![CDATA[27707]]></user>
  </uid>
  <created>1574796985</created>
  <changed>1574796985</changed>
  <title><![CDATA[PhD Proposal by Frederick Hohman]]></title>
  <body><![CDATA[<p><strong>Title:</strong>&nbsp;Interactive Scalable Interfaces for Machine Learning Interpretability<br />
<br />
Fred Hohman<br />
School of Computational Science &amp; Engineering<br />
College of Computing<br />
Georgia Institute of Technology<br />
<br />
<strong>Date:</strong>&nbsp;Monday, December 2, 2019<br />
<strong>Time:</strong>&nbsp;4:30pm - 6pm (EST)<br />
<strong>Location:</strong>&nbsp;Coda 114 (first floor conference room)<br />
<br />
<strong>Committee</strong><br />
Duen Horng (Polo) Chau - Advisor, Georgia Tech, Computational Science&nbsp;&amp;&nbsp;Engineering<br />
Alex Endert - Georgia Tech, Interactive Computing<br />
Chao Zhang - Georgia Tech, Computational Science&nbsp;&amp;&nbsp;Engineering<br />
Nathan Hodas - Pacific Northwest National Lab<br />
Scott Davidoff - NASA Jet Propulsion Lab<br />
Steven Drucker - Microsoft Research<br />
<br />
<strong>Abstract</strong><br />
Data-driven paradigms now solve the world&#39;s hardest problems. Instead of authoring a function through exact and explicit rules, machine learning techniques instead learn rules from data.&nbsp;Unfortunately, often these rules are unknown to both the people who train models and the people they impact. This is the purpose and promise of machine learning interpretability. But what is&nbsp;interpretability? What are the rules that modern, complex models learn? And how can we best represent and communicate them to people? Since machine learning now impacts people&#39;s daily lives,&nbsp;we answer these questions taking a&nbsp;<em>human-centered approach</em>&nbsp;by designing and developing interactive interfaces can enable interpretability at scale and for everyone. This thesis focuses on:<br />
<br />
<em>(1) Operationalizing machine learning interpretability:</em> We conduct user research for understanding what practitioners want from interpretability, instantiate these into an interactive interface, and use it&nbsp;as a design probe into the emerging practice of interpreting models (Gamut). We also show how different complementary mediums can be used for explanations, such as visualization and&nbsp;verbalization (TeleGam).<br />
<br />
<em>(2) Scaling deep learning interpretability:</em>&nbsp;We reveal critical yet missing areas of deep learning interpretability research (Interrogative Survey). For example, neural network explanations focus on single&nbsp;instances or neurons, but predictions are often computed from millions of weights that are optimized over millions of instances, such explanations can easily miss a bigger picture. We present an&nbsp;interactive interface that scalably summarizes and visualizes what features a deep learning model has learned and how those features interact to make predictions (Summit).<br />
<br />
<em>(3) Communicating interpretability with interactive articles:</em>&nbsp;Due to rapid democratization, machine learning now impacts everyone. We use interactive articles, a new medium to communicate complex&nbsp;ideas, to communicate interpretability and teach people about machine learning&#39;s capabilities and limitations, while developing new publishing platforms (Parametric Press). We propose a framework for&nbsp;how interactive articles can be effective through a comprehensive survey that pulls from diverse disciplines of research and critical reflections (Interactive Articles).<br />
<br />
Our work has made significant impact to industry and society: our visualizations have been deployed and demoed at Microsoft and built into widely-used interpretability&nbsp;toolkits, our research is supported by NASA, and our interactive articles have been read by hundreds of thousands of people.</p>
]]></body>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Interactive Scalable Interfaces for Machine Learning Interpretability]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_time>
    <item>
      <value><![CDATA[2019-12-02T16:30:00-05:00]]></value>
      <value2><![CDATA[2019-12-02T18:30:00-05: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>102851</tid>
        <value><![CDATA[Phd proposal]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
