Nowadays we are witnessing the continuous generation of a huge volume of data from heterogeneous sources. Managing, processing, and analyzing such data becomes challenging and requires the adoption of high-performance computing frameworks and techniques. The course discusses the performance bottlenecks in traditional data processing and analytical tools and techniques and presents the opportunities to design scalable solutions leveraging distributed cluster environment architectures. Emphasis is put on the Hadoop and Spark frameworks, with practical examples of big data processing and analytical tasks in real-world applications.
In this course, we will be using the Python programming interface to the Apache Spark framework (PySpark), in combination with Databricks. You will be able to write and execute PySpark code directly in your browser, without worrying about standalone configuration, and leveraging free access to Databricks' powerful cloud infrastructure. This structure also facilitates collaborative coding.
Our High-Performance Computing course has joined the Databricks University Alliance, an active community of professors and educators who collaboratively share ideas to improve the teaching experience and provide students with most recent and relevant developments in terms of data science tools and concepts adopted in the industry. In order to start using Databricks, you can set up a free personal account (Community Edition). This options gives you the option to use Databricks on Amazon AWS for free. Instructions to sign up will be provided in the course.
Date | Topic | Module | Deadlines |
---|---|---|---|
Week 1 | |||
Aug 30 | Introduction to HPC | S1 | |
Sep 2 | Big Data Analytics / NoSQL | S2 - S3 | |
Week 2 | |||
Sep 6 | Hadoop I | S4 | Install VM |
Sep 9 | Hadoop II | S4 | |
Week 3 | |||
Sep 13 | Spark: Intro, RDDs & Databricks Platform | S5 | Create Databricks Account |
Sep 16 | Spark: Dataframes | S5 | |
Week 4 | |||
Sep 20 | Spark: Transformations | S6 | |
Sep 23 | Spark: Internals | S7 | |
Week 5 | |||
Sep 27 | Midterm Exam I | Pool of Papers Release | |
Sep 30 | Spark: Structured Streaming / Delta Lakes | S8 | |
Week 6 | |||
Oct 4 | Spark: ML and MLlib / Linear Regression | S9 | |
Oct 7 | Spark: MLflow / Decision Trees / Random Forest | S10 | |
Week 7 | |||
Oct 11 | Spark: HyperOpt / AutoML / XGBoost | S11 | |
Oct 14 | Fall Break | / | |
Week 8 | |||
Oct 18 | Spark: MLlib Deployment / Pandas UDF / Koalas | S12 | |
Oct 21 | Spark: Logistic Regression / Collaborative Filtering | S12 | |
Week 9 | |||
Oct 25 | Time Series Forecasting Graph Analysis: GraphX / Case Study / GraphFrames |
S13 | |
Oct 28 | Spark: Deep Learning I | S14 | Paper critiques submission Project Assignment |
Week 10 | |||
Nov 1 | Spark: Deep Learning II | S15 | |
Nov 4 | Spark: Deep Learning III | S15 | |
Week 11 | |||
Nov 8 | Spark: NLP I | S16 | |
Nov 11 | Spark: NLP II | S16 | |
Week 12 | |||
Nov 15 | Midterm Exam II | Project: Data Exploration / Pre-processing | |
Nov 18 | Spark: ML Deployment / ML in production | S17 / S18 | |
Week 13 | |||
Nov 22 | Spark: Performance Optimization I (Online) | S19 | Project: Modeling |
Nov 25 | Thanksgiving Holidays | ||
Week 14 | |||
Nov 29 | Spark: Performance Optimization II | S19 | |
Dec 2 | Paper Presentations | Project: Report draft | |
Week 15 | |||
Dec 6 | Paper Presentations | ||
Dec 9 | Paper Presentations | Project submission | |
Week 16 | |||
Dec 13 | Final Exam (02:30PM-05:00PM) |
Component | Weight |
---|---|
Midterm Exams (2) | 30% (2 x 15%) |
Research Papers: 2 critiques + 1 presentation | 10% |
Final Exam | 30% |
Final Project | 30% |
Component | Weight |
---|---|
Midterm Exams (2) | 20% (2 x 10%) |
Research Papers: 3 critiques + 1 presentation | 10% |
Final Exam | 30% |
Final Project | 40% |
Students are recommended to attend all lectures. Prolonged absences must be discussed with the instructor. If you cannot attend lectures regularly, due to work or other obligations during remote learning, then please reach out to the instructor so that I know about it.
Exams cover the material from the lectures, projects, and reading. While not necessarily cumulative, each exam will require understanding many of the concepts covered in the preceding exams. Exams consist of multiple choice, short answer, and long answer questions. Each exam, except the final, is weighted equally.
The Final Exam is cumulative: half of the final exam will be material covered for prior exams, half will be material that is new since the previous exam.
For the Final Project, students will propose their own topic in consultation with the instructor.
A penalty of 5% per day will be levied. The course doesn’t grant extension on the homework/lab/project submission deadline unless you have an extremely compelling excuse as observance of a religious holiday (in which case you need to let me know in advance).
Range | Letter |
---|---|
>=93 | A |
>=90 | A- |
>=87 | B+ |
>=83 | B |
>=80 | B- |
>=77 | C+ |
>=73 | C |
>=70 | C- |
>=60 | D |
<60 | F |
Even though we encourage collaboration with a partner, sharing code between groups is strictly forbidden - this is a form of plagiarism. As is showing your work to other students, even just for a second. There is rarely one single correct way to write code that solves a problem. While we want you to feel free to discuss your approach freely with a partner, you should know that there are often many solutions for a given problem and it's typically obvious when one student shares code with another. If you directly copy and paste code from the Internet (or even the text), cite your source in your comments (but also ensure that you understand what the code is doing - not all code on the web is good!). Assignments will be checked using plagiarism detection software and by hand to ensure the originality of the work.
Do not share your code with anyone other than a partner. Do not let someone look at your screen. You may get behind, or your friend may ask for help, but the consequences for plagiarism are far worse than an incomplete submission - for the submission, you will still likely get some points. If I suspect that you have purposely shared code with another student or presented someone else's work as your own, the matter will be referred to the Academic Integrity Code Administrator for adjudication. If you are found responsible for an academic integrity violation, sanctions can include a failing grade for the course, suspension for one or more academic terms, dismissal from the university, or other measures as deemed appropriate by the Dean.
All students are expected to adhere to the American University Honor Code. If you have a question about whether or not something is permissible, ask the instructor or the TA first.