Numerical Analysis –
362.01 – Spring 2003
T/Th:
Instructor: Dr.
John Neuberger, Office AMB #214.
Office: (#214) T 2-2:30, Th
9-9:30, (#222) W 10-11, F 3-4. (And by appointment.)
Text:
Numerical Analysis, 7th
ed, Burden and Faires
(Includes diskette).
Supplement: Programming Language reference (C/C++
recommended).
Optional: Mathematica
reference (suggested), or Matlab/Mathcad/etc.
4 Projects (1/30,
2/21, 3/13, 4/3): 35%
1 Final Project (4/24): 15%
Homework/Quizzes: 10%
3 Tests (2/13,
3/25, 4/29): 20%
Comprehensive
Final (5/6,
Suggestion: Obtain phone/email info of reliable
classmate(s) for missed assignments.
Projects: See attached guidelines. Regular projects should be done in groups of
2 to 4 students. It
is each student’s
duty to make sure that all group members contribute equally, and to report
discrepancies. Final projects are to be
solo efforts.
Attendance: This
will affect your daily grade. No makeups without verifiable written
excuse. Five (5) Point deduction
per day for late projects. Makeups given
(possibly orally) during Reading Week.
Please plan to arrive and depart class at
the scheduled time!
Ethics: Student’s are bound by the NAU Student Handbook
(See http://www4.nau.edu/stulife/StudentHandbook/TableofContents.htm).
Unless
otherwise stated, all work is to be done by the student alone, without collaboration,
and without extensive use of supplemental texts.
Important:
Keep homework and corrected quizzes/tests
in a neat organized notebook.
I will collect and grade this
notebook periodically for Homework/Quiz points.
Typically, this notebook can make 1/2 a letter grade difference!
1.
Homework will be assigned, some of which may be
presented by students at the board, some collected, the rest to be placed in the notebook.
2.
The Projects will be the single most important
component of the class. See the attached
Guidelines.
3.
You may use any programming language you like, but I
will be using C for class discussion and be best able to help you with C
programs. Fortran
is a decent choice also. You will need an email account.
4.
We will also be using Mathematica or similar software to analyze results and write reports. I will use Mathematica for class discussions.
Plan to produce
professional appearing documents. There
are many different acceptable formats…the following is more of a suggestion
than a rigid rule.
Use Mathematica or similar package to
write-up report.
1)
Title –
suggestive of content, short.
2)
Author(s) – in alphabetical order.
3)
Introduction –
short, mathematical, informative,
useful to the reader:
a)
Purpose of report.
b)
Contents of
report.
c)
Languages/Platforms
used.
d)
Algorithm/Formulae/Theorem
names.
4)
Main Body – Label/Identify all objects, refer to
appendix as needed.
a)
Explanations
b)
Formulaes and mathematics.
c)
Algorithms, Pseudocode, short code segments.
d)
Graphics, Tables.
e)
Freestyle - do something extra, creative, different! This portion
is typically worth a full letter grade!
5)
Conclusion –
short, mathematical, informative, useful to the reader.
a)
Successes/Failures.
b)
Discoveries.
c)
Proposed future
efforts.
6)
Appendix –
Optional – Longer Code segments, large tables, repetitive data/graphics,
glossary,
bibliography, index, etc.
Please avoid inclusion of
enormous quantities of output data or tedious repetition. An excellent report may be quite short or
somewhat long; length has no direct bearing on the quality of the report. Make an effort to include mathematical formulaes and equations, handwritten if necessary.