Syllabus - Spring 2020
Time and Location
Lectures: Tuesday 1:30PM-2:45PM; Thursday 1:30PM-2:45PM
Ignacio M. Llorente
About the Course
After completing this course you should be able to:
- Recognize and recall programming models, platforms, open-source tools and computing architectures that are relevant to computational and data science
- Assessment of computational approaches and their practical applications to scientific problems
- Fundamentals of parallel computing including abstract thinking and algorithmic development
- Identify which parallel strategy is appropriate to solve a given problem
- Design efficient parallel solutions to scientific problems
- Implement parallel programs in prominent programming models and evaluate their performance using various metrics
- Use a collection of open source software and state-of-the-art HPC platforms for data analysis, modelling, and visualization of real scientific problems
Students are expected to have basic programming experience, familiarity with Python and C, basic knowledge of Linux including using the command line, and basic understanding of algorithms (CS207 or CS50).
The course is aimed at students with a background in a scientific discipline who will not typically have a traditional Computer Science background, though basic programming knowledge is assumed as a prerequisite. We hope to attract students from the life sciences, physical sciences, economics, social sciences, medicine, and the humanities interested in developing applications for large-scale computational or data processing.
This course is also for computer science, engineering, and undergraduate students that need to make decisions about the architecture of a system, choose tools for solving a given problem and figure out how best to apply them, or better understand the strengths and weaknesses of existing systems and tools.
- Introduction to High Performance Computing for Scientists and Engineers; Georg Hager; CRC Press; July 2010
- Introduction to parallel computing; Ananth Grama, Anshul Gupta, George Karypis, Vipin Kumar; Pearson, January 2003
- Programming Massively Parallel Processors: A Hands-on Approach; David B. Kirk and Wen-mei W. Hwu; Morgan Kaufmann; February 2010
- The Art of Multiprocessor Programming; Maurice Herlihy, Nir Shavit; Morgan Kaufmann; June 2012
- Designing Data-Intensive Applications. The Big Ideas Behind Reliable, Scalable, and Maintainable Systems; Martin Kleppmann; O'Reilly Media, March 2017
- MapReduce Design Patterns: Building Effective Algorithms and Analytics for Hadoop; Adam Shook and Donald Miner; O'Reilly Media, December 2012
- Data Analysis in the Cloud, Models, Techniques and Applications; Domenico Talia, Paolo Trunfio, Fabrizio Marozzo, September 2015
- Cloud Computing for Science and Engineering; Ian Foster, Dennis Gannon; The MIT Press Cambridge, 2017
The course is designed to study and discuss the principles (reading assignments and lectures), to develop practical skills (hands-on sessions, programming assignments and infrastructure guides), to expose students to real-world life experiences (case studies and guest lectures), and to apply the concepts to solve a real-life problem (project).
Each lecture includes a required reading to ensure that you are prepared for the activities in class. You are expected to complete the required reading and answer to the questions of a 30-minute online survey that will be available during the day of the lecture before class.
You are also invited to post on Piazza before lecture any comments for the readings. Post your comments under the Piazza note announcing the publication of the reading assignment using the “Follow-up discussion” feature. Examples of good comments:
- Clarification of some point or detail in the readings
- Critiques of arguments made in the readings
- Analysis of implications or future directions for work discussed
- Questions about the readings or answers to other people's questions
- Links to web resources or examples that pertain to a reading
Typically you should set aside 1-2 hours to complete each reading assignment. Even though we do not expect you to fully understand everything before coming to class, you will often have to read some passages several times to build your understanding. The goal of the reading assignments is to prepare for class, to familiarize yourself with new terminology and definitions, and to determine which part of the subject needs more attention.
Lecture attendance is mandatory and essential. Lectures are organized under themes and include explanation of theoretical concepts to build a conceptual framework, and simple examples and case studies to illustrate the theory. They may also include discussion of reading assignments to develop problem-solving strategies and critical thinking. Please arrive on time, we will have in-class quizzes to assess your understanding of the material and to help us identify gaps.
Hands-on session attendance is mandatory. Hands-on sessions provide an opportunity to learn and practice the main programming models, which will be used in the programming assignments (homework) and the final project. Students should previously prepare the execution framework needed to do the exercises according to the guidelines provided by the instructors. The course includes hands-on exercises on AWS cloud and Harvard’s Odyssey supercomputer.
Attendance to labs is optional but strongly encouraged. Lab sessions are used to allow students to become familiar with the computing and data processing infrastructure on AWS by following the infrastructure guides, and to provide help with the homework (programming assignments) and the final project.
Guest lecture attendance is mandatory. Guest lectures are given by experts with proven expertise in the course topics to expose students to real-world life experiences about the application of the models and platforms learnt in the course. There will be a survey at the end of each guest lecture.
In-class quizzes will be taken at the end of the lecture sessions and the material will be based on what was discussed in the class. There will be no retakes or makeup quizzes for any reason. Your lowest 3 scores on all quizzes will be dropped.
Lectures are complemented by homeworks to bridge the theory with the practice. Homeworks mostly consist of basic programming assignments to exercise a technology or programming model. Homework assignments will be posted on the website on Mondays and will be due the following Monday (listed in the course schedule). There are no late days.
Infrastructure guides help with the deployment of parallel computing and big data processing frameworks on the AWS cloud for developing, testing and evaluating the programming assignments and the final project.
A major component of the course is a final programming project. Your final project is to solve a compute or data intensive scientific problem using the platforms, tools and systems introduced in the course. You will collect the data, implement the tool, and analyze the performance of an end to end application. You are required to form teams and to partition the work among the team members. The final project has five milestones: the team formation, an in-class presentation of your project proposal, an in-class presentation of your progress with the design of the project, and project deliverables submission and final presentation to teaching staff.
Further details about the project will be updated under the Projects page.
We will not have standard midterm or final exams. Instead, we will have in-class quizzes, two in-class presentations on project proposal and progress, and a final project presentation during the scheduled final exam period.
We'll be using Piazza for online class discussions. We will also use Piazza for all course announcements. Piazza is your main venue to ask questions, discuss problems, and help each other out. It should always be your first recourse for seeking answers to your questions about the course, lecture or reading material, or the assignments. Participation on Piazza will factor into your participation grade for the course.
The Instructors and the Teaching Fellows hold weekly office hours. Office hour times and locations are listed on the Class Homepage. Office hours provide you with an opportunity to review and discuss course materials as well as provide further guidance for your homework in a more intimate environment, with only your teaching fellow and maybe a handful of classmates present.
This course can be taken for a letter grade only, there is no pass/fail option. You will be graded on homework assignments, a final project, in-class quizzes and participation. There will be no exams. The final grade will be composed as follows:
- Homework (40% - 400 points): Individual submission of assignments.
- Final Project (40% - 400 points): A project of your own design to be worked on in small teams.
- Quizzes (10% - 100 points): Assessments of your understanding of the material.
- Participation (10% - 100 points): Online forum posts, reading assignments, in-class participation, and lecture attendance.
Homework will be graded based on 1) how correct your code is (the code should compile and run, we are not troubleshooting code), and 2) how you have interpreted the results in a report. Your work will be evaluated holistically beyond mechanical correctness and focus on the overall quality of the work. Solutions to homework assignments can be discussed in office hours but will not be posted publicly.
It is very important to us that all assignments are properly graded. If you believe there is an error in your assignment grading, please submit an explanation via email to us within 7 days of receiving the grade. No regrade requests will be accepted orally, and no regrade requests will be accepted more than 7 days after you receive the grade for the assignment. Also, note that requesting a regrade applies to the entire assignment.
No homework assignments or project milestones will be accepted for credit after the deadline. If you have a verifiable medical condition or other special circumstances that interfere with your coursework please let us know as soon as possible. You will need to provide a written note from a medical professional confirming your inability to participate in course work.
Any student receiving accommodations through the Accessible Education Office should present their AEO letter as soon as possible. Failure to do so may prevent us from making appropriate arrangements.
Devices in Class
We will use laptops throughout the term to facilitate activities and project work in-class. However, research and student feedback clearly shows that using devices on non-class related activities not only harms your own learning, but other students’ learning as well. Therefore, we only allow device usage during activities that require devices. At all other times, you should not be using your device. We may help you remember this by announcing when to bring devices out and when to put them away.
Lecture, hands-on session and guest lecture attendance is mandatory and quality of participation will factor into the participation grade. You must send an email to the staff at least a day before a lecture to be excused. Attendance to labs is optional but strongly encouraged.
Helping each other out and discussing the reading assignments and lectures is a key aspect of this course. All students are expected to contribute online on Piazza and during lectures, and participation on Piazza and lecture attendance will contribute to the final grade.
You are welcome to discuss the course's material and homework with others in order to better understand it, but the work you turn in must be your own (with some exceptions, e.g., the final project, where work is explicitly shared). You are encouraged to discuss programming assignments with classmates, but should be open about such cooperation, and should attribute anyone you collaborated with with in your homework.
There is a balance to be struck between submitting your own work (to demonstrate you're learning the material) and discussion/collaboration with others (to enhance learning through mutual assistance). In general, avoid sharing actual code (particularly code you hand in), but feel free to discuss, diagram, use pseudocode, and even share small amounts of code ("snippets"). If you are in doubt as to the appropriateness of some level of collaboration with other students, contact the course instructor.
The class staff will be using codeanalysis tools to compare students work; plagiarism will not be tolerated, and students may be asked to work more independently if their work is too similar. You may not submit the same or similar work to this course that you have submitted or will submit to another, without permission. You must acknowledge any source code that was not written by you by mentioning the original author(s) directly in your source code (comment or header), or in a README.txt file accompanying your submission. Do not remove any original copyright notices and headers. All forms of academic dishonesty will be forwarded to the Harvard College or Extension School Administrative Boards.
The lecture material is adapted from the books and online research resources relevant to the course topics. Please contact us if you find materials where the credit is missing or that you would rather have removed.