Syllabus
CMSC 714:  High Performance Computing

 

No Primary Text

• But we will read parts of:
  The Grid: Blueprint for a New Computing Infrastructure (2nd Edition), Morgan Kaufmann/Elsevier, 2004. 
  

Tentative Grading Plan

Your grade will be determined as follows:

	#	% total
Programming assignments	2	15
Group project	1	40
Midterm	1	30
Paper presentation	1 or 2	10
Class participation	-	5

 

Exams

• The midterm exam will cover all material up to the midterm.

Programming projects

• The first two projects, in C and/or Fortran, will use MPI and OpenMP to become familiar with parallel/distributed programming on a Linux cluster and a Sun SMP.  Accounts will be forthcoming.
  
• After the first 2 projects, you will do a group project, in C, C++ (or Fortran or Java), with milestones along the way.
  This project will be done in teams of 2 people.
  
• The projects should be submitted by 6:00 pm on the day they are due. Late projects will be not be accepted.
  
• The instructor reserves the right to fail, regardless of overall numeric score, students who do not submit on-time a good faith attempt to complete the programming assignments.
  
• All submissions of assignments will be via email to me. Posted deadlines for program submission are sharp; standard Unix time of submission is used.
  

Intellectual Integrity, Academic Honesty, and Cheating

• The college policy on academic dishonesty is strictly followed.
  All graded materials (whether exams or programming assignments) must be strictly individual efforts.
  
• We expect you to follow all UMIACS and UMD guidelines for responsible machine usage.
  
• Dr. Sussman is the information owner for all Linux cluster and Sun accounts in this class, and all files in those accounts may be inspected by him at any time.
  
• Allowing another student not in your group to examine a listing of your program or examining the listing of another student's program (not in your group), for any reason, is strictly forbidden.
  
• Logging onto another student's account, for any reason, is cheating.
  
• Attempting to falsely represent the correctness of your program, or to delay other members of the class from completing a programming assignment, is cheating.
• The standard penalty for any cheating is to receive a grade of XF in the course. This grade denotes failure due to academic dishonesty, and your transcript will be so annotated.
  
• Automatic tools may be used to compare your solution to that of every other current or past student in this class, so it will be very difficult to hide any collaboration. The risk of getting caught is too high, and the standard penalty is way too high (grade of XF). In Spring 2003, multiple systems faculty members caught multiple students who thought they could hide their collaboration in CMSC 412.