If you wish your grade, please send me an email and I will reply with your final exam score and your semester grade. Please note there may be a slight security risk in having your grade sent by email. Unless you're a rock star hounded by tabloids, or you have nosy relatives/neighbors that are expert hackers, I don't think it could be much of an issue. Nevertheless I will assume that if you ask me to email your grade, then you are willing to assume this risk.

Your exam paper is yours to have, if you wish it. I'll probably toss them out around January 2004, maybe sooner.

The University of Colorado

Boulder, Colorado

Mathematics 4650, Spring 2003

Intermediate numerical analysis



This page pertains only to Professor Taylor's section of Mathematics 4650, for the spring semester of 2003. As far as I know, this is the only section occurring this semester. For other sections or other semesters, other details and regulations will no doubt apply.

An attempt will be made to keep this page up-to-date, but this is not guaranteed. Students are responsible for every assignment made in class, whether or not it ultimately appears on this page.


Prerequisites


Computing Resources

Experience in a structured programming language is highly desirable. I prefe r helping you in C, just because I am more familiar Generally speaking, the computing part of this course will not go beyond the abilities of any student with university-level computing experience.

Your main programming work can take place either on a university unix machine, such as rintintin, or on a PC (your own, or the university's). To use any university machine, unix or PC, you will need an identikey . (See this page). Here you can also set up an account on rintintin.

The unix machine rintintin (also abbreviated rtt) is a remote-access machine, which can be accessed from almost any computer on campus (using ssh). It can also be contacted from your home PC, if you have a modem and an available phone line. rtt has several compilers, and all the tools you need.

If you elect to use unix machines, it is imperative to make sure that you have noclobber set at all times. (Ask me what this means.) On a unix account, your work is theoretically saved for your next login. (Accidents do happen - most frequently user mistakes, much less often system breakdowns. I would make copies of your precious files on disk or on other machines, or something!)

On the ITS page about printing,, and on a second ITS page about printing, you can find out about printing from a unix machine such as rtt.

You may use your own PC, or a university PC, but the code you submit must compile and run, with no editing, on one of the compilers on rintintin. (I will ask for the "math library, -lm", but beyond that it must run with no further assistance.) There are many PC-labs on campus. According to the ITS computer lab list, the following rooms in Engineering have PC's with Borland C++: ECCH 107, ECCR 235, ECCR 239, ECCR 252, ECME 107.

Remember that when you use your identikey to access a PC on campus, from the operating system's point of view you are only a temporary guest, and none of your work is protected against deletion by another user . (In fact, to protect class security, you are asked to delete at least your source-code before leaving a shared machine on campus.) Therefore, it is imperative to save your work on diskette at the end of every session. If you have Borland at home, you can of course carry work back and forth between home and CU on a diskette.


Textbook

Numerical Analysis, by Burden and Faires, Brooks-Cole, seventh edition, 2001. (It is essential to have the seventh edition.)

ISBN 0-534-38216-9

To see the cover of the text, click here .

The book comes with a CD that contains various computational materials. We will not use this CD, although you might gain something by browsing through it and playing with it a bit. (In any case, the CD files are available here, if you're missing the CD.)


About homework

More later; for now only this:

When homework involves computing, you will submit results of calculation in writing (computer output fine), and will submit code by email. Please send it as ordinary text, no fancy encodings. Both should include a statement of your sole authorship of the material. Code submitted will be subjected, on a random basis, both to performance testing and to scrutiny to see that it really looks like it's doing the right thing. So please keep it simple. All of our problems will have simple solutions. A few more things will be said in class.


Exams


Homework.

Due at the start of class on the indicated day.