[an error occurred while processing this directive]

<h2>Exploration Sessions </h2>
<h3>Thursdays, 4:30-5:20pm, in <a href="http://www.washington.edu/maps/#!/gug">GUG</a> 220</h3>

<p>
  Each week we will offer a different opportunity to explore extra topics in
  computer science. You will accumulate one "exploration
  point" for each week that you attend the lecture.  At the end of the quarter,
  your total exploration points will be divided by 3 and will be added to your
  homework points.  There will be approximately 150 homework points total, so
  this isn't adding a lot to your potential score.  As an example, if you were
  to participate in 3 exploration sessions, you would have 1 point added to
  your homework points, which is like getting one more point on a weekly
  programming assignment.  The idea is to give people a small reward, but not
  something that is so large that people feel obligated to participate in these
  optional sessions.  You can get fractions of a point (e.g., getting
  two-thirds of a point for attending 2 sessions).
</p>

<p>
  Please come prepared to listen to and ask questions of the guest speaker.
  <b>We have a strict no-laptop policy in these sessions. If you are using
    a laptop, you will be asked to put it away or leave.</b>
</p>

<p>
  This schedule is subject to change. We will send an announcement email
  the day before each session with information about the topic for that
  session.
</p>

<div class="week">
    <h3>
        Week 9: Physical Computing, <a href="http://christinebetts.com/">Christine Betts</a> - Thursday, May 25 from 4:30-5:20 in <a href="http://www.washington.edu/maps/#!/gug">GUG</a> 220
    </h3>
    <ul>
        <li>
          So you've got some Java programming under your belt and can write
          awesome programs to interact with on your computer, but what about
          interacting with the outside world? We'll discuss the realm of
          physical computing and hardware with the Raspberry Pi and Arduino
          along with an introduction to working with circuits and breadboards.
        </li>
        <li><img src="images/videos_icon.png"> <a href="https://uw.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=7720595a-91a2-4c17-8108-f1e157f6fe3b">Recording</a> (audio problems, sorry!)</li>
        <li><a href="http://christinebetts.com/learn/physical-computing/">Supplemental Page</a></li>
    </ul>
</div>

<div class="week">
    <h3>
        Week 8: Artificial Intelligence, <a href="http://maxwellforbes.com/">Max Forbes</a> - Thursday, May 18 from 4:30-5:20 in <a href="http://www.washington.edu/maps/#!/gug">GUG</a> 220
    </h3>
    <ul>
        <li>
          What is intelligence? How would you go about making an artificial
          intelligence (AI)? Join us as we explore these questions, examine an
          example artificial intelligence algorithm, and let it loose on a small
          Pac-Man grid. Along the way, we'll take a leisurely tour across the
          diverse and expanding field of artificial intelligence.
        </li>
        <li><img src="images/videos_icon.png"> <a href="https://uw.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=bf9af825-f1d9-4e6e-ae80-03b5473fadf7">Recording</a></li>
    </ul>
</div>

<div class="week">
    <h3>
        Week 7: The Command-Line Interface - Thursday, May 11 from 4:30-5:20 in <a href="http://www.washington.edu/maps/#!/gug">GUG</a> 220
    </h3>
    <ul>
        <li>
            Most of us use our computers graphically, using a pointer to
            manipulate visual elements on the screen.  However, you may have
            noticed that programmers often instead interact with their computers
            textually, using the command line.  We'll talk very briefly about why
            this is, and go through a crash course in a common command line
            environment known as "bash" (available on Mac, Linux, and Windows).
        </li>
        <li><img src="images/videos_icon.png"> <a href="https://uw.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=8b292bf3-65f8-4ddb-95e2-bdea10774cd3">Recording</a></li>
        <li>Check out <a href="https://courses.cs.washington.edu/courses/cse391/17sp/">CSE 391</a> for a much deeper look at this!</li>
    </ul>
</div>

<div class="week">
    <h3>
      Week 6: No session
    </h3>
    <ul>
      <li>
        Study for your midterms!
      </li>
    </ul>
</div>

<div class="week">
    <h3>
      Week 5: History of Electronic Surveillance in the US - Thursday, April 27 from 4:30-5:20 in <a href="http://www.washington.edu/maps/#!/gug">GUG</a> 220
    </h3>
    <ul>
      <li>
        In recent years, there's been a lot of talk  about mass surveillance
        and the Snowden disclosures.  But surveillance of private electronic
        communications in the United States is nothing new.  In this session,
        we'll discuss its history, from the 19th century to today, and look at
        how legal, social, and technological attitudes towards it have changed
        over that time.
      </li>
      <li><img src="images/videos_icon.png"> <a href="https://uw.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=a52d12f4-de98-46a2-b592-e008e2a21a75">Recording</a></li>
    </ul>
</div>

<div class="week">
    <h3>
      Week 4: Car Hacking, <a href="https://homes.cs.washington.edu/~supersat/">Karl Koscher</a> - Thursday, April 20 from 4:30-5:20 in <a href="http://www.washington.edu/maps/#!/gug">GUG</a> 220
    </h3>
    <ul>
      <li>
        Did you know that the typical modern car has over a dozen computers inside? Have you ever thought about whether people might be able to hack in to these computers, or what might happen if they do? In this talk, I'll describe our multi-year research project that answered these questions and more. First, I'll describe what an attacker can do with access to a car's internal network. Then, I'll explain how someone might be able to break in to these networks remotely. This talk will feature several videos demonstrating our attacks and conclude with a short discussion about the impact this research has had.
      </li>
      <li><img src="images/videos_icon.png"> <a href="https://uw.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=9f32e651-77d3-4eec-8615-21add44bc9a7">Recording</a></li>
    </ul>
</div>

<div class="week">
    <h3>
      Week 3: What is the Internet? - Thursday, April 13 from 4:30-5:20 in <a href="http://www.washington.edu/maps/#!/gug">GUG</a> 220
    </h3>
    <ul>
      <li>
        As former senator Ted Stevens once famously said, the internet is not a
        big truck -- it's a series of tubes. What do those tubes look like? What
        can we put through them? Who owns them? Where are they located? In this
        session, we will learn the answer to these questions, and more.
      </li>
      <li><img src="images/videos_icon.png"> <a href="https://uw.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=194eca7e-15ad-4ab8-824a-50ddb3b336c4">Recording</a></li>
      <li><a href="http://submarinecablemap.com/">Submarine Cable Map</a></li>
      <li><a href="https://www.telegeography.com/telecom-resources/map-gallery/index.html">Internet Maps</a></li>
    </ul>
</div>

<div class="week">
    <h3>
      Week 2: What is a computer? - Thursday, April 6 from 4:30-5:20 in <a href="http://www.washington.edu/maps/#!/gug">GUG</a> 220
    </h3>
    <ul>
      <li>Computers have invaded every corner of our lives -- you probably have a personal computer, and you almost certainly have a smartphone in your pocket. But have you ever stopped to think about what a computer actually is? What differentiates a computer from other types of machines? We'll talk about the formal definition of a computer, and why computer scientists are interested in these questions.</li>
      <li><a href="https://www.gwern.net/Turing-complete">Surprising Turing Completeness</a></li>
      <li><a href="http://www.jflap.org/">JFLAP</a> (turing machine simulator)</li>
    </ul>
</div>

<div class="week">
    <h3>
      Week 1: No session
    </h3>
    <ul>
      <li>First week of the quarter!</li>
    </ul>
</div>


			</div>
		</div>

<!--
		<div class="w3c">
			<a href="http://validator.w3.org/check/referer"><img src="images/w3c_xhtml11.png" alt="Valid XHTML 1.1" /></a>

			<a href="http://jigsaw.w3.org/css-validator/check/referer"><img src="images/w3c_css.png" alt="Valid CSS!" /></a>
		</div>
-->

		<!-- Google Analytics -->
		<script type="text/javascript" src="//www.google-analytics.com/urchin.js"></script>
		<script type="text/javascript">
			_uacct = "UA-2729135-1";
			urchinTracker();
		</script>
	</body>
</html>