Instructor:
Lori Pollock pollock@cis.udel.edu
436 Smith Hall (831-1953) - Moving to 436 Smith on September 15
Office Hours:
TTh 11:00-12:00
and by appointment.
Teaching Assistant:
Sara Sprenkle
102 Smith Hall
We will write parallel programs primarily using MPI (Message
Passing Interface). MPI is a library of routines that allows
programs running in parallel to talk to each other, and send data
back and forth. These programs will be compiled and executed on
a dedicated network of linux PCs on the CIS network. You
must obtain an account on this cluster as soon as
possible. Go to htto://www.eecis.udel.edu and click
on "Apply for Account". Ask for an academic
account for MPI parallel programming.
When using the cluster login to "porsche.cis.udel.edu".
Each quiz will take about 5 minutes at the beginning of class. It
will contain 1-2 short questions based on recent class discussions and
readings.
There will be a quiz every Tuesday, unless announced otherwise. The
quiz will focus on the previous week's classroom and reading topics.
Each student's lowest two quiz grades will not be counted toward their
final grade.
Thus, there WILL BE NO MAKEUP quizzes. Any missed quizzes will be counted
as zeros in the grading scheme above. Thus, if you miss more than two
quizzes, all additional missed quizzes and all other quiz grades will be
counted toward your final grade.
I have found that the quickest way to resolve ambiguities and answer questions on
homework and programming assignments is via email.
Any questions sent to pollock@cis will
be posted anonymously with an answer
via email to the entire class, and on the course Blog.
One
or more classmates as well as the instructor may offer
an answer or expand the discussion.
Labs must be given to the instructor by the start of
class on the due date, in order to have no points
deducted for lateness.
The due dates are to be taken seriously and you should not expect
them to be extended. The pace of work is implicit in the due
dates and necessary if you expect to finish by the end of the semester.
Homeworks to be graded should be turned in at the start of class on the specified due date.
NO late programs or homeworks will be accepted FOR FULL CREDIT without
discussion with me prior to the due date. If you can not reach me, leave a message on my voicemail.
All other assignments not delivered
by the due date are considered late.
My philosophy on late assignments is:
(1) Everyone should try their best to complete all assignments by the
specified due date. (2) People who work conscientiously to make the deadlines should
be rewarded for their promptness and sacrifice of sleep. Thus, allowing others to hand
in late assignments without some penalty is not fair to these people. However, there
are various circumstances that may prevent you from completing an assignment by
the due date. Allowing no late assignments would not give you much incentive
to
continue to work on the assignment, which is a major source of learning in this course.
Thus, I believe late assignments are better than no assignment.
Late assignments will be penalized 5% off the total possible points if turned
in within the first 24-hour period after the specified due date and time,
and 5% per 24-hour period (or fraction of a day) (including weekends)
after that time, up to a week after the due date.
Late assignments will be accepted with penalty up to one week after
the due date. Assignments submitted at any later time without
an approved excuse will not be accepted.
It is up to you to determine the version of your assignment
to be graded. You must weigh the
late penalty against the completeness of your assignment.
If you are dissatisfied with a grade on a homework, programming assignment,
or exam,
you should consult the instructor directly within a week of the day the
graded assignment was returned to you. No regrade requests will be considered
after this week period.
With your permission, grades will be posted periodically (by your secret code)
on the course web page.
Questions about accuracy of recorded grades should be
addressed to me.
You are permitted to consult with other students and professors on any
conceptual problems on all programming assignments.
Debugging should be done individually or in your project group.
Debugging assistance can be obtained from the TA after you have tried all
of the debugging tricks discussed in class - print statements, etc.
Any evidence of collaboration other than this kind
will be handled as stated in the Official Student Handbook of the University of Delaware.
If you are in doubt regarding the requirements,
please consult with me before you complete any requirement of this course.
Office Hours:
TBA
Required Textbook:
Michael J. Quinn, Parallel Programming in C with MPI and OpenMP, McGraw Hill,
2004.
References:
Programming Environment and Computer Usage:
Weekly Quizzes:
Goals:
Requirements and Grading:
Email Questions:
Assignment Submission:
Regrading Policy:
Posting Grades:
Policy on Academic Dishonesty: