PH 265: Introductory Scientific Computing
Fall 2005 - Class Home Page


Catalog Description:
INTRODUCTORY SCIENTIFIC COMPUTING (3). Basic computational tools and techniques for courses in science and engineering. Project approach to problem solving using symbolic and compiled languages with visualization. Basic computer literacy assumed. COREQ: MTH 251. CROSSLISTED as CS 265.

Daily Schedule: Syllabus and Assignments
Class Meetings: Lecture ---- 2:00-2:50pm Monday ---------------- Room: WNGR 149A
Lab -------- 2:00-2:50pm Wednesday/Friday ----- Room: WNGR 412
Exam Dates & Times: Oct 28 (Friday) 2:00pm -------------- Mid-Term Exam
Dec 06 (Tuesday) 12:00noon -------- Final Exam
Class Web Address: www.physics.orst.edu/~haerer/ph265/Description.html (it points to this page)
Course Textbook: A First Course in Scientific Computing, by Rubin Landau (Princeton University Press, 2005)
Instructor: Sally D. Haerer
Office Hours: 30 minutes before/after each class (Weniger 403) or by appointment. Send email with questions, comments, or discussion to haerer@physics.orst.edu
Teaching Assistant: Kyle Augustson augustsk@onid.orst.edu
Computer Support: Department of Physics Support Page www.physics.orst.edu/support


Grading:
All assignments must be submitted electronically by the date and time of the deadline. Please use the following website for submitting your assignments: http://oregonstate.edu/~augustsk/PH265/SubmitHomework.html At this web location, there are facilities for you to enter your name, browse your directories for the proper homework file, then submit that file to be graded. Late assignments will not be considered.

Your final letter grade will be assigned on a 10-percentage-point scale (90-100%, A; 80-90%, B; etc.). Four types of grades will be used to evaluate your performance in this course:

Note: Any student whose total exam score is below 60% will receive an F, even if the overall total average (which includes out-of-class assignments) exceeds 60%.

Exams will be as follows:

Academic Honesty
For the assignments, each student must write his or her own solutions. Some discussion among students about assignments is good, so how can you tell where to draw the line? A good rule of thumb is the "visual aids" rule. It is ok to talk to each other, offer advice, suggest techniques, demonstrate general methods, and so on, as long as no visual aids (such as printouts, gathering around a screen to look at code, handwritten notes, written code or algorithms, etc.) are directly involved with a particular assignment. This means you may not exchange or share written or drawn information with classmates on assignments, nor should you make written notes as you discuss these things with your classmates. Please refer to the University policy on dishonesty and feel free to discuss any questions or concerns with Instructor Haerer.