|
|
CS276 / LING 286 |
Meeting Times and Locations
Lecture: 3 units, Tu/Th 4:15-5:30
Gates B01
Review Section: 0 units, Tu 1:15 Skilling 193, (held 6 times per quarter, one per assignment/exam, see the syllabus for specific dates)
Staff Contact Information
Newsgroup:
We strongly recommend students to post questions to the course newsgroup su.class.cs276 (instead of sending emails). This forum enables students to discuss the
questions they encounter in lectures or assignments. For information about how
to access the newsgroup see A
Stanford Intro to Usenet.
Email:
If you have a question not appropriate for the newsgroup (e.g., one that is only
relevant to your situation or one that reveals part of your solution to a
homework question), please email the staff mailing list at cs276-aut0809-staff@lists.stanford.edu.
Professor: Christopher Manning
Office: Gates 158
Office Hours: Monday 2:00pm - 3:00pm
Email: manning@cs.stanford.edu
Professor: Prabhakar Raghavan
Office: none on campus
Office Hours: by appointment
Email: pragh@yahoo-inc.com
TA: Daniel Ramage
Office: Gates 114
Office Hours #1: Tuesday 5:30pm - 7:00pm, Gates B24B, Phone (650) 736-1816
Office Hours #2: Thursday 10:30am - 12:00pm, Gates 114, Phone (650) 725-6965
Email: email
TA: Kevin Wong
Office Hours: Wednesday 4:30pm - 6:30pm, Gates B26A
Email: kbw5@stanford.edu
TA: Jason Chuang
Office: Gates 398
Office Hours #1: Monday 4:30pm - 6:00pm, Gates 398, Phone (650) 725-7784
Office Hours #2: Tuesday 10:30am - 12:00pm, Gates 398
Email: jcchuang@stanford.edu
TA: Richa Bhayani
Office Hours #1: Wednesday 2:30pm - 4:00pm, Gates B26A
Office Hours #2: Friday 11:30am - 1:00pm, Gates B26A
Email: rbhayani@stanford.edu
Course
admin: Debbie Barros
Office: Gates 150
Email: dbarros@cs.stanford.edu
Announcements: If you are not registered in the course but wish to receive course announcements, you may subscribe to the guest mailing list cs276-aut0809-guests@lists.stanford.edu.
Grading Policy:
|
Problem
sets (2) |
20% |
|
Programming
exercises (2) |
10%
+ 20% = 30% |
|
Midterm |
20% |
|
Final |
30% |
Assignment/Exam Schedule:
In addition to the midterm and final, we will assign two written problem sets and two programming-based practical exercises. Refer to the right-most column of the syllabus for the scheduled dates.
Assignment Policies:
- Delivery: Assignments must be submitted by 5 p.m. Pacific on the due date. Problem sets should be handed to TAs in class or left in the box outside of Professor Manning's office. (SCPD students should deliver their problem sets to SCPD, via courier, faxo, or email.) Practical exercises should be submitted online according to instructions in the assignment handouts.
- Late days: Each student has 5 late days to use at his or her discretion, and may apply up to 4 late days for each assignment. If your assignment is late, you must mark the hand-in date and time on your assignment. Please reserve your late days for legitimate emergencies. Each late day constitutes a 24-hour extension; you cannot split late days into smaller increments. If two partners on a practical exercise want to take a late day, they must contribute two days from their allotment; either one from each of them, or, with permission, two days from the person with extra late days.
- Late penalties:
Once a student runs out of late days, any late submissions are penalized
at a rate of 10% per day. No assignment may be handed in more than 5 days
late.
- Collaboration:
- You may talk to anybody you want about the assignments,
including working through problems together in groups. Indeed, we
encourage you to work in groups, and to work with different people
through the quarter.
- For written problem sets:
- you must state on your written assignment the
people you discussed problems with, and
- you are not allowed to take detailed notes in any group sessions that will appear verbatim in assignment write-ups. Everybody has to turn in written homework answers that are written solely by himself/herself.
- For practical exercises you may work with one other person and submit a single copy of your work.
- Regrades: If you feel that we made a mistake in grading one of your assignments, you can resubmit the assignment for a regrade. Please include a brief written statement describing which portion(s) you would like us to review and why. Your assignment will be regraded by a different TA. If you are still not happy, you can ask for your assignment to be regraded by an instructor. Note that when you request a regrade, we reserve the right to review your entire assignment -- i.e. we may find errors in your work that we missed before.
Honor Code:
All actual, detailed work on the solution of problem sets must be individual work. You are encouraged to discuss problem sets with each other in a general way, but if you do so, then you must acknowledge the people with whom you discussed the problem set at the top of your submission.
You should not look for problem answers
elsewhere; but again, if material is taken from elsewhere, then you should acknowledge
it. For practical exercises, you are not permitted to get programming help from
people other than your partner. Normally, you are permitted to use pre-existing
code, but you must acknowledge code that you have taken from other
sources. In general, we will act and expect you to act according to the Stanford
Honor Code.