CS/ENGRD 3220, Spring 2011

Lecture time: MW 10:10-11:00

Lecture location: Phillips 219

Sections times:

- Th 12:10-1:10
- Th 3:35-4:25
- Th 4:35-5:25
- F 2:30-3:20

Section location: Phillips 307

Prof. David
Bindel

5137 Upson Hall

Phone: 607-255-4428

E-mail:

TA: Ivaylo (Ivo) Boyadzhiev

E-mail:

- Heath,
*Scientific Computing: An Introductory Survey*(2nd ed) - Moler,
*Numerical Computing with MATLAB*(the online edition is fine)

You will need basic multivariable calculus and linear algebra. The standard Engineering math sequence is fine, or Math 1110-1120-2210. If you have taken other courses covering the same material, that is also fine.

You will also need to know the basics of MATLAB. If you have never
used MATLAB, consider taking (or just following) Transition to
MATLAB, a one-credit self-paced web course intended to quickly teach
MATLAB to students who have already learned another programming language.
If you know a little MATLAB and would like to build your skills, you may
also find it helpful to read the first chapter of *Numerical Computing
with MATLAB*.

There will usually be weekly homeworks, which are due in class on Monday. These problems will involve a mix of short answers, plots, and computations done in MATLAB. Homework may be handwritten or printed, and should be submitted at the beginning of class. After they are graded, homework scores will be posted to CMS, and the graded papers can be picked up from 363C Upson 10am-12pm or 2pm-4pm on weekdays. Regrade requests must be submitted within one week of receiving the graded homework.

Some weeks, instead of homework, there will be small programming projects in which you will apply the methods to practical problems. These projects may be done individually or in groups of two. Your implementations must be done in the MATLAB environment, and they must run on the machines in the CSUGlab.

There will be two evening prelims and a final exam:

- First prelim: February 22 at 7:30 in Upson B17
- Second prelim: April 7 at 7:30 in Upson B17
- Final exam: May 13 at 2:00 in Phillips 203

All three exams are closed book, but you may bring one letter-sized piece of paper with writing on both sides.

Your final grade in CS 3220 will be computed from grades on the assignments and exams using the following weights:

- Homework: 5% times 8 homeworks (lowest grade is dropped)
- Projects: 7% times 4 projects
- Prelims: 8% times 2 prelims
- Final: 16%

Homework assignments are due at the start of class on the due date (normally Monday), and are not accepted late. The lowest homework grade will be dropped in computing your final score.

Projects are due at 11:59pm on the due date (normally Monday) and are accepted with a late penalty two days after the due date (normally Wednesday). Programs are accepted late as follows:

- Hand in by late deadline: 10% off score (about a letter grade)
- Hand in within one week of due date: graded pass/fail; pass receives 50% credit
- More than one week late: no credit

Assignments that are handed in under option 2 will not be graded carefuly and may be returned very late. This option is solely intended to mitigate the effect of zero scores on the final grade.

An assignment is an academic document, like a journal article. When
you turn it in, you are claiming everything in it is your original work,
*unless you cite a source for it*.

You are welcome to discuss homework and projects among yourselves in general terms. However, you should not look at code or writeups from other students, or allow other students to see your code or writeup, even if the general solution was worked out together. No credit will be given for code or writeups that are shared between students (or teams, in the case of projects).

If you get an idea from a classmate, the TA, a book or other published source, or elsewhere, please provide an appropriate citation. This is not only critical to maintaining academic integrity, but it is also an important way for you to give credit to those who have helped you out. When in doubt, cite! Code or writeups with appropriate citations will never be considered a violation of academic integrity in this class (though you will not receive credit for code or writeups that were shared when you should have done them yourself).

We expect academic integrity from everyone. School is stressful, and you may feel pressure from your coursework or other factors, but that is no reason for dishonesty! If you feel you can't complete the work on the own, come talk to the professor, the TA, or your advisor, and we can help you figure out what to do.

For more information, see Cornell's Code of Academic Integrity.

In the event of a major campus emergency, course requirements, deadlines, and grading percentages are subject to changes that may be necessitated by a revised semester calendar or other circumstances. Any such announcements will be posted to the course home page.