| layout | nav_order | title | description |
|---|---|---|---|
page |
2 |
Syllabus |
Syllabus |
{:.no_toc}
{: .no_toc .text-delta }
- TOC {:toc}
The course is organized into four parts, covering the following topics.
- Foundations of Data Systems: Data models, big data storage and retrieval, and how to encode information when you store data.
- Scaling Distributed Systems: Cluster, cloud, edge, network, replication, partition, consistency, ACID.
- Data Processing and Programming model: Batch processing, stream processing, MapReduce, Hadoop, Spark, Ray.
- Machine Learning Systems: GPUs, TensorFlow, PyTorch, data and model parallelism, LLM training and serving.
A major component of this course is hands-on Python programming to implement data exploration, data preparation, distributed deep learning training and inference, and model selection pipelines on large real-world data using popular libraries (e.g., Ray, PyTorch) and cloud resources (e.g., AWS/GCP).
The class meets 3 times a week for 50-minute lectures in person.
- Attending the lectures is not mandatory but highly encouraged. All lectures will be automatically podcast here afterward.
- There will be scribe notes required for each lecture. Students should form groups of 2 - 4 people and sign up one slot. See details below.
- There will be reading summary required per week. Everyone needs to submit their reading summary. See details below.
- We will use Piazza for asynchronous discussions and questions.
- See the assignments page for updates on the PA schedule and details.
- There are no late days for the PAs. Plan your work accordingly.
- To make your life easier: There is NO midterm. As an alternative, we ask for scribe notes and reading summary.
- There will be a final exam. The final exam will be held as a Canvas Quiz.
- Tentative date: Friday, March 22, 8 - 11 am, PT.
- The exams will have primarily multiple choice questions (MCQ). Quantitative/longer problems wil exist but only the final answer may need to be selected. Some questions will have partial credits.
- The guideline for time per question is a max of 1min per point. The points of each question will be calibrated accordingly.
- If you miss an exam, you will get no credit for it, unless you notify the instructor in advance with a university approved reason and receive a makeup exam slot.
- The final exam is open books/Web/etc. The only requirement is you should neither give nor receive help from anyone by any means.
Each student is required to scribe for a small number of lectures (most likely just 1). Most lectures will have at least 3 students acting as scribes, and they should work as a team. During your assigned lectures, you are to take detailed notes in collaboration with your fellow scribes. After the lecture, the scribe team is to convert their notes into LaTeX format using the provided template. These notes should be 4-8 pages long, and must be submitted electronically. We only require one set of notes from the scribe team. The instructors will then audit your notes, and post them to the class home page for everyone's benefit. As long as your scribe notes are of sufficient standard, you will be awarded full credit for scribe duties. If your notes have errors or are otherwise not up to standard, we will inform you and give you one chance to correct them. ChatGPT is highly recommended to polish the writing of your scribe notes. You will receive zero credit if you fail to submit your notes.
- Sign-up: Spreadsheet
- Template: Overleaf latex template
- Submission: Submit a pull request to course website repo for review.
- Due: 11:59 pm PT of the day 10 days from the lecture
Starting from the second week, the instructor/TA team will provide one required reading and multiple optional readings prior to each lecture. The required readings for this class are compulsory. The optional readings are highly recommended. At the end of each week, you are to submit a 2-page summary of the readings you have done for all the required readings of all lectures of the week. These reading summaries are a requirement for this class, and they must be submitted via Gradescope by you in order to receive credit. However, you have 5 grace days on which you can submit the summaries late via email (e.g. if you need to absent from class for whatever reason) with no penalty. Your summary should be written at a high level, and should focus on the main point of the readings (i.e. avoid complicated math). As long as your summary is reasonable, you will be given full credit. There will be no readings for the last week (March 11 - March 15) of the instruction. Hence, in total, you need to submit 8 reading summary (week 2 - week 9).
You are encouraged to use ChatGPT to improve the writing of your summary; but you should avoid using software like ChatPDF to generate a summary without actually finishing any readings by yourself. The TA team will perform quick scans on all summaries and contact you if they notice the summary seems to be entirely generated by ChatGPT (the writing style is easily detectable).
- Template: NeurIPS format
- Length: 2 pages
- Submission: Gradescope
- Due: starting from the 2nd week, the summary of the week is due on Wednesday 11:59pm of the next week
We appreciate everyone being actively involved in the class! There are several ways of earning participation credit, which will be capped at 5%:
- Piazza participation: The top ~20 contributors to Piazza will get 3%; others will get credit in proportion to the participation of the ~20th person. (To prevent abuse of the system, not all contributions are counted and instructors hold the right to determine to count contributions as positive or negative.)
- Completing course evaluations: Around the middle and end of the semester, we will send out a survey to help us understand how the course is going, and how we can improve. Completing them is worth 1%.
- Karma point: Any other act that improves the class, which a DSC204A TA or instructor notices and deems worthy: 1%.
- DSC 202 (Data Mgt for Data Science); or substantial practical experience with scalable data systems and ML algorithms, subject to the consent of the instructor.
- Proficiency in Python programming.
- Knowledge of deep learning and deep learning frameworks such as PyTorch.
- Programming Assignments: 12% + 16% + 16%
- Final Exam: 36%
- Scribe Duties: 8%
- Reading summary: 12%
- Extra Credit: 5%
The grading scheme is a hybrid of absolute and relative grading. The absolute cutoffs are based on your absolute total score. The relative bins are based on your position in the total score distribution of the class. The better grade among the two (absolute-based and relative-based) will be your final grade.
| Grade | Absolute Cutoff (>=) | Relative Bin (Use strictest) |
| A+ | 95 | Highest 5% |
| A | 90 | Next 10% (5-15) |
| A- | 85 | Next 15% (15-30) |
| B+ | 80 | Next 15% (30-45) |
| B | 75 | Next 15% (45-60) |
| B- | 70 | Next 15% (60-75) |
| C+ | 65 | Next 5% (75-80) |
| C | 60 | Next 5% (80-85) |
| C- | 55 | Next 5% (85-90) |
| D | 50 | Next 5% (90-95) |
| F | < 50 | Lowest 5% |
Example: Suppose the total score is 82 and the percentile is 33. So, the relative grade is B-, while the absolute grade is B+. The final grade then is B+.
Non-Letter Grade Options: You have the option of taking this course for a non-letter grade. The policy for P in a P/F option is a letter grade of C- or better; for S in an S/U option is a letter grade of B- or better.
No late daysfor submitting the PAs. No extensions on the final exam time window. Plan all your work well up front accordingly.- Students are encouraged to ask questions and participate in discussions in class and on Piazza. Please raise your hand before speaking and the instructor will call on you to speak.
- Please review UCSD's honor code and policies and procedures on academic integrity here. If plagiarism is detected in your code, or if we detect collusion on the graded quizzes or exams, or if you are found to be using someone else's clickers, or if any other form of academic integrity violation is identified, you will get zero for that component of your score and get downgraded substantially. I will also notify the University authorities for appropriate disciplinary action to be taken, up to and including expulsion from the University.
- Please review UCSD's principles of community and our commitment to creating an inclusive learning environment on this website.
- Harassment, discrimination, or intimidation of any form against any student will not be tolerated in class or on Piazza. Please review UCSD's policies on dealing with harassment and discrimination on this website.