ECS 122B - Algorithm Design and Analysis - Winter 2007

Course Information Sheet

January. 2, 2011



You are responsible for the information on this handout. Please read it.

Course Web page

We will maintain useful information on the course Web page: http://www.cs.ucdavis.edu/~martel/122b.
  • Visit this page regularly to see what's new. If you miss a handout, get it from here.

    Lectures

    T,Th 1:40-3:00 in 147 Olson


    Discussion Sections

    W 9-9:50 in 106 Olson

    Instructor

    • Chip Martel.
    • #3049 Kemper Hall.
    • Phone: 752-2651.
    • email: martel AT cs DOT ucdavis.edu.
    • Office hours: Tuesday 11:45-12:40, F. 12:45-2:00

      TA

    • Sam Johnson.
    • Phone:
    • email: samjohnson AT ucdavis DOT edu.
    • Office hours: Thursday 4:30-5:30,

      Midterm

      There will be one midterm in this class around Febuary 8.

      Final

      In class final, on Tuesday, March 10 .

      Prerequisites

      Minimal prerequisites are ECS 20 (formerly known as ECS 100) ECS 60 and ECS 122A. Mathematics majors might do fine without ECS 20. However, the knowledge in both these classes is critical to success in this class. This is a demanding class and those without the prerequisites are likely to do poorly .

      Textbook

      There are two textbooks:
    • Programming Pearls, by Jon Bently, second edition. [Main Text]
    • Algorithm Design, by Kleinberg and Tardos [Supplemental Text]

      Grading

      There will be periodic problem sets and programs (35%), one midterm (30% each), and a final (35%). Note that you must get a passing average on the two midterms to pass this course.

      Homeworks

      Homeworks are due by 3:15PM on the due date. It is to be turned in at the marked box in Kemper Hall, #2131. No late homeworks will be accepted.

      Much of what one learns in this course comes from trying to solve the homework problems, so work hard on them. Doing a conscientious job on the homeworks is the best preparation for the exams. We hope that you will ultimate solve the majority of the problems, but don't be surprised if some of them stump you; some of the problems may be quite challenging.

      Your solutions should be terse, correct, and legible. Understandability of the solution is as necessary as correctness. Expect to lose points if you provide a "correct" solution with a not-so-good writeup. As with an English paper, you can't expect to turn in a first draft: it takes refinement to describe something well. Typeset solutions are always appreciated.

      If you can't solve a problem, briefly indicate what you've tried and where the difficulty lies. Don't try to pull one over on us.