Introduction to Parallel Computing (CMSC416/CMSC818X)

Hours

Lectures: Tu Th 11:00 AM--12:15 PM in CSI 3117.
TA office hours:

  • Tu 9:30 AM--10:30 AM with Pooja Nilangekar in IRB 2207 Open Area
  • Th 2:15 PM--3:15 PM with Shoken Kaneko in IRB 2207 Open Area

Staff

Name Email Role Office
Abhinav Bhatele bhatele@cs.umd.edu Instructor IRB 5218
Shoken Kaneko kaneko60@umd.edu TA
Pooja Nilangekar poojan@umd.edu TA

Description (from catalog)

Introduction to parallel computing for computer science majors. Topics include programming for shared memory and distributed memory parallel architectures, and fundamental issues in design, development and analysis of parallel programs.

Additional description

The objective of this course is to study the theory and practice of high performance and parallel computing. The overall goal is to expose you to programming tools and techniques for parallel environments. This course will focus on current practices in high performance computing technologies, including systems, architectures, programming models, languages and software tools.

Prerequisites

CMSC416: Minimum grade of C- in CMSC330 and CMSC351; or permission of instructor.
CMSC818X: CMSC411 and CMSC412; or permission of instructor.

Course Topics (Subject to change)

  • Introduction to parallel computing (1 week)
  • Parallel architectures and networks (1 week)
  • Shared-memory programming (1 weeks)
  • Distributed-memory programming (3 weeks)
  • Parallel algorithm design (2 weeks)
  • Debugging & Instrumentation (1 week)
  • Performance Tools (1 week)
  • Performance optimizations (1 week)
Primary Text

None.

Grading

Your grade will be determined as follows:

Number % total
Programming assignments440
Quizzes410
Midterm exam120
Final exam130
Programming Assignments
  • The programming assignments, in C/C++, will use MPI and OpenMP to become familiar with parallel/distributed programming on a Linux cluster. Accounts on the university deepthought2 cluster will be forthcoming.
  • The assignments should be submitted by 11:59 PM Anywhere on Earth (AoE) on the day they are due. Late assignments will be not be accepted.
  • All submissions of assignments will be via ELMS. Posted deadlines for program submission are sharp; standard Unix time of submission is used.
Academic Integrity

The CS Department takes academic integrity seriously. Information on how the CS Department views and handle academic integrity matters can be found at Academic Integrity.

Note that academic dishonesty includes not only cheating, fabrication, and plagiarism, but also includes helping other students commit acts of academic dishonesty by allowing them to obtain copies of your work. In short, all submitted work must be your own. Cases of academic dishonesty will be pursued to the fullest extent possible as stipulated by the Office of Student Conduct.

It is very important for you to be aware of the consequences of cheating, fabrication, facilitation, and plagiarism. For more information on the Code of Academic Integrity or the Student Honor Council, please visit http://www.shc.umd.edu.

Exams/Programming Assignments

On any graded exam or programming assignments, you are NOT allowed to collaborate or exchange code. We compare each student's code with every other student's code to check for similarities. Every semester, we catch an embarrassingly high number of students that engage in cheating and we have to take them to the Honor Council.

Uploading code to Github

You may post your assignment(s) code to private Github (or similar service) repos only. As a student, you can make a private repo for free. Just remember that your free premium subscription has an expiry date, and your code becomes public once it expires. The Honor Council can retroactively give an XF (even to students who have already graduated) if your code is then used by another student to cheat. So just be careful.

Posting graded code to a public repo will give you a free ticket to the Honor Council.

GroupMe/ Other Group Chats

We encourage students to talk about course material and help each other out in group chats. However, this does NOT include graded assignments. Talking about release tests is NOT okay.

There have been a couple instances in the past where students have posted pictures/source files of their code, or earlier sections have given away exam questions to later sections. Not only did this lower the curve for the earlier section because the later one will do better, the WHOLE group chat had to pay a visit to the Honor Council. It was an extremely ugly business. Remember that in a group of 200+, someone or the other will blow the whistle. If you happen to be an innocent person in an innocent groupchat and someone starts cheating out of the blue, leave it immediately (and better yet, say you are leaving and say you will report it).

Study Guides

Creating collaborative study guides on Google docs is OK. Encouraged, even. Just do this before the exam, and don't bring the study guide to the exam. Don't add exam questions to the study guide after the early section's midterm.

PRACTICE Exams/ Worksheets/ Lecture examples/ Ungraded Lab examples Totally cool. Highly encouraged to co-create and share (with same caveats as study guides).

Prof. Bhatele is the information owner for all Linux cluster accounts in this class, and all files in those accounts may be inspected by him at any time.

The following are examples of academic integrity violations:

  • Hardcoding of results in an assignment. Hardcoding refers to attempting to make a program appear as if it works correctly (e.g., printing expected results for a test).
  • Using any code available on the internet/web or any other source. For example, using code from GitHub.
  • Hiring any online service to complete an assignment for you.
  • Sharing your code or your tests with any student.
  • Using online forums in order to ask for help regarding assignments.
Piazza

This term we will be using Piazza for class discussion. Rather than emailing questions to the teaching staff, I encourage you to post your questions on Piazza. The class sign up link is on ELMS.

Excused Absence and Academic Accommodations

See the section titled "Attendance, Absences, or Missed Assignments" available at Course Related Policies.

Any student who needs to be excused for an absence from a single lecture, due to a medically necessitated absence shall make a reasonable attempt to inform the instructor of his/her illness prior to the class. Upon returning to the class, present the instructor with a self-signed note attesting to the date of their illness. Each note must contain an acknowledgment by the student that the information provided is true and correct. Providing false information to University officials is prohibited under Part 9(i) of the Code of Student Conduct (V-1.00(B) University of Maryland Code of Student Conduct) and may result in disciplinary action.

Self-documentation may not be used for Major Scheduled Grading Events (midterm exams, and final exams) and it may only be used for two class meetings during the semester. Any student who needs to be excused for a prolonged absence (two or more consecutive class meetings), or for a Major Scheduled Grading Event, must provide written documentation of the illness from the Health Center or from an outside health care provider. This documentation must verify dates of treatment and indicate the timeframe that the student was unable to meet academic responsibilities. In addition, it must contain the name and phone number of the medical service provider to be used if verification is needed. No diagnostic information will ever be requested.

Disability Support Accommodations

See the section titled "Accessibility" available at Course Related Policies.

Miscellaneous

Copyright

All course materials are copyright UMCP, Department of Computer Science © 2021. All rights reserved. Students are permitted to use course materials for their own personal use only. Course materials may not be distributed publicly or provided to others (excepting other students in the course), in any way or format.