CSCE 206 - Scientific Applications Programming
Spring 2004
Dr. Duncan A. Buell
3A01 Swearingen, 777-2880
email ID is "buell" in domain "cse.sc.edu"
Meeting time: MW 2:30-3:45, SWR 2A19
Office hours: MW 1:00-2:30, SWR 3A01
The graduate assistant for this course is
Xizhou Feng, id "fengx" in the domain
"cse.sc.edu",
office A111 in the 300 Main St. Engineering Building
(across Main St. from Swearingen),
phone 777-7506,
and office hours are 3:00pm to 5:00pm Tuesdays and Thursdays.
Caveat
This page is likely to be under changing throughout the semester
as assignments and notes are added to it.
Text
Nyhoff and Leestma,
Fortran 90 for Engineers and Scientists,
Prentice-Hall, 1997.
Other References
There are a number of FAQ and tutorial links on the CSE departmental
web server.
You should log in to the "Student and Faculty Login" link off the
home page and follow the links to the resources about software.
You could also go directly to the department's
secure web server
and follow the links from there to the information about computing
resources.
Email
I have had established a CSE department email list for CSCE 206.
You are responsible for putting your name on this list.
This can be done by signing on to the departmental
home page
and following the "CSE Mailing Lists" link.
You can put in this mail list any address you choose that gets mail to you.
A mass mailing to the entire class will be done through the mail alias
csce206 mentioned in the previous paragraph.
Actually, any of you can send mail to this alias.
It's just csce206 in the domain cse.sc.edu
If I need to initiate an email to you individually, I will do so using
the CSE departmental account that all students get as part of being
registered in this class.
You are responsible for reading email sent to this account or else
setting up the "dot forward" file to send it on to an account that you
do read regularly.
I will not attempt to keep track of your individual accounts except
for the CSE departmental account.
To forward your mail from your departmental account, create a file
with the file name .forward
in your departmental home directory.
(That's a period, with no space, followed by the word forward.)
This file should contain only one line, and that line should be
the email address to which you would want your mail forwarded.
For example, to forward to an account xyzzy@myisp.com your
dot forward file should have the line
xyzzy@myisp.com in it.
Outline, Prerequisites, and Expectations:
The hoped-for goals of this course are that students should leave it with
the following basic knowledge:
-
how to create and understand programs in the modern Fortran
language (Fortran 90 and beyond);
-
how to do basic numerical computing for scientific or engineering
applications;
-
how to know that the numerical inaccuracies and similar complexities
arising from the finite wordlength of a computer will negatively
affect the correctness of a program's output;
-
how to know whether a program is likely to be "fast" or whether the time
to completion could be a problem.
Programming Resources
The Fortran programming for this course will be done on Unix
machines in the Department of Computer Science and Engineering.
Access to these machines can be had from the college computer
labs in Swearingen or in 300 Main or using a secure login procedure
from any other computer.
This means that you would be able to access the compilers from
home- or dorm-based computers provided you install the acceptable
secure login software.
Tests and assignments
There will be two exams and a final exam during the semester.
The midterm is presently scheduled for 18 Feb 2004, timed so
that you can get back your exams just before the 24 Feb 2004
deadline to drop without receiving a WF grade.
The final exam is scheduled for Saturday, 1 May 2004, at 2:00 pm.
Both the midterm and the final exam will be closed book exams.
The quiz/participation grades will be done as follows.
You are expected to read the scheduled material prior to coming to class.
You are expected to come to class on time.
At random intervals, I will either assign short quizzes at the
beginning of class or will call upon an individual.
I will arrange the class roll so that everyone on the roll will be called
upon at least once during the course of the semester.
If I call upon you, and you are not there or are late for class that
day, you will lose that fraction of the potential quiz/participation grade.
A quiz will not be given to students who are not present at the
time I begin to hand it out.
Click here for the
programming assignments page for this course.
Click here for the
sample programs page for this course.
Grading scheme
The final grade will be computed on the basis of the weighted average
of the scores for
-
quizzes and participation (10%),
-
the two exams (20% each),
-
the programming assignments (30%),
-
the final exam (20%).
The final grades will almost certainly be curved,
but you should expect no lower a grade
than you would receive under the usual 90/80/70/60/50 scheme.
Lecture notes, slides, and pointers
(Caveat: Any lecture notes I prepare may well change during the
lecture process; if you print them too early and too often you may
use up your print quota.)
-
Unix for the Minimalist
ps
pdf
-
Crib sheet for the vi editor
ps
pdf
-
Lab exercise from 14 January 2004
ps
pdf
Deadlines
Homework and programming assignments will have due dates.
Unless otherwise specified, these will be turned
in by the beginning of the class period on the due date.
Late assignments will not be accepted without prior arrangement
to accommodate truly extraordinary circumstances.
Academic Honesty
Assignments and examination work are expected to be the sole effort
of the student submitting the work.
Students are expected to follow the
Code of Student Academic Responsibility
found in the
Carolina Community
and should expect that every instance of a suspected violation
will be reported.
Students found guilty of violations of the Code will be subject to academic
penalities under the Code in addition to whatever disciplinary sanctions
are applied.
There seems to be a widespread misunderstanding of the concept
of "your own work."
In addition to the USC Code, some good sources of text for what is or
is not acceptable behavior are the
academic honesty policy statement from Harvey Mudd College, the
policy statement from Professor Steven Huss-Lederman at Beloit College,
and the text of part of the
collaboration policy statement from MIT.
A sample first-offense admission can be found at
admission.
Proper Use of Computing Resources
Students are expected to be aware of the
university policy
on use of computing resources, including the
Student Guidelines for Responsible Computing,
as well as the
college
and
departmental
policies on proper use of computing resources.
Every instance of a suspected violation will be reported.
Students should be aware that neither the instructor nor the
department are responsible for making alternative arrangements
should improper use leading to revocation of access to departmental
or college resources make it impossible for you to complete the
programming assignments on time.
Return to Computer Science and Engineering homepage
This web site is maintained by the CSE Webmaster.
All contents copyright
© The Board of Trustees of the University of South Carolina.
Last Modified: 02-Dec-2003
URL: HTTP://www.cse.sc.edu/~buell/csce206/csce206_2004_1spring.html
|