| layout | title | nav_order | description | markdown | course | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
page |
Syllabus |
2 |
Principles and Techniques of Data Science |
kramdown |
|
{:.no_toc}
Jump to:
- TOC {:toc}
Combining data, computation, and inferential thinking, data science is redefining how people and organizations solve challenging problems and understand their world. This intermediate level class bridges between Data 8{:target="_blank"} and upper division computer science and statistics courses as well as methods courses in other fields. In this class, we explore key areas of data science including question formulation, data collection and cleaning, visualization, statistical inference, predictive modeling, and decision making. Through a strong emphasis on data centric computing, quantitative critical thinking, and exploratory data analysis, this class covers key principles and techniques of data science. These include languages for transforming, querying and analyzing data; algorithms for machine learning methods including regression, classification and clustering; principles behind creating informative data visualizations; statistical concepts of measurement error and prediction; and techniques for scalable data processing.
- Prepare students for advanced Berkeley courses in data-management, machine learning, and statistics, by providing the necessary foundation and context.
- Enable students to start careers as data scientists by providing experience working with real-world data, tools, and techniques.
- Empower students to apply computational and inferential thinking to address real-world problems.
While we are working to make this class widely accessible, we currently require the following (or equivalent) prerequisites. Prerequisites will be enforced in Data 100. It is your responsibility to know the material in the prerequisites. The instructors do not have the authority to waive these requirements. Undergraduates should fill out the Enrollment Exception Form{:target="_blank"} managed by CDSS to request an exception.
-
Foundations of Data Science: Data 8{:target="_blank"} covers much of the material in Data 100 but at an introductory level. Data 8 provides basic exposure to python programming and working with tabular data as well as visualization, statistics, and machine learning.
-
Computing: The Structure and Interpretation of Computer Programs (CS 61A{:target="_blank"}) or Computational Structures in Data Science (Data 88C{:target="_blank"}). These courses provide additional background in python programming (e.g., for loops, lambdas, debugging, and complexity) that will enable Data 100 to focus more on the concepts in Data Science and less on the details of programming in python.
-
Math: Linear Algebra (Math 54, EECS 16A, Math 56, Math 110, or Stat 89A). We will need some basic concepts like linear operators, projections, and optimization to analyze and derive new prediction algorithms. This may be satisfied concurrently to Data 100.
Please consult the Resources page for additional resources for reviewing prerequisite material.
Textbook: There is no official textbook for Data 100 this semester; we will provide course notes that will be released with the respective lectures.
Students taking Data C100 come from a wide range of backgrounds. We hope to foster an inclusive and safe learning environment based on curiosity rather than competition. All members of the course community — the instructors, students, and course staff — are expected to treat each other with courtesy and respect. Some of the responsibility for that lies with the staff, but a lot of it ultimately rests with you, the students.
Sometimes, the little things add up to creating an unwelcoming culture to some students. For example, you and a friend may think you are sharing a private joke about other races, majors, genders, abilities, cultures, etc. but this can have adverse effects on classmates who overhear it. There is a great deal of research on something called “stereotype threat”: research finds that simply reminding someone that they belong to a particular culture or share a particular identity (on whatever dimension) can interfere with their course performance.
Stereotype threat works both ways: you can assume that a student will struggle based on who they appear to be, or you can assume that a student is doing great based on who they appear to be. Both are potentially harmful.
Bear in mind that diversity has many facets, some of which are not visible. Your classmates may have medical conditions (physical or mental), personal situations (financial, family, etc.), or interests that aren’t common to most students in the course. Another aspect of professionalism is avoiding comments that (likely unintentionally) put down colleagues for situations they cannot control. Bragging in open space that an assignment is easy or “crazy,” for example, can send subtle cues that discourage classmates who are dealing with issues that you can’t see. Please take care, so we can create a class in which all students feel supported and respected.
Beyond the slips that many of us make unintentionally are a host of behaviors that the course staff, department, and university do not tolerate. These are generally classified under the term harassment; sexual harassment is a specific form that is governed by federal laws known as Title IX.
{: .note }
UC Berkeley’s Title IX website{:target="_blank"} provides many resources for understanding the terms, procedures, and policies around harassment. Make sure you are aware enough of these issues to avoid crossing a line in your interactions with other students. For example, repeatedly asking another student out on a date after they have said no can cross this line.
Your reaction to this topic might be to laugh it off, or to make or think snide remarks about “political correctness” or jokes about consent or other things. You might think people just need to grow a thicker skin or learn to take a joke. This isn’t your decision to make. Research shows the consequences (emotional as well as physical) on people who experience harassment. When your behavior forces another student to focus on something other than their education, you have crossed a line. You have no right to take someone else’s education away from them.
We take all complaints about unprofessional or discriminatory behavior seriously. Professionalism and respect for diversity are not just matters between students; they also apply to how the course staff treat the students. The staff of this course will treat you in a way that respects our differences. However, despite our best efforts, we might slip up, hopefully inadvertently. If you are concerned about classroom environment issues created by the staff or overall class dynamic, please feel free to talk to us about it. The instructors in particular welcome any comments or concerns regarding conduct of the course and the staff. See below for how to best reach us.
{: .note }
From the Data Science Department: Data Science Undergraduate Studies{:target="_blank"} faculty and staff are committed to creating a community where every person feels respected, included, and supported{:target="_blank"}. We recognize that incidents may happen, sometimes unintentionally, that run counter to this goal. There are many things we can do to try to improve the climate for students, but we need to understand where the challenges lie. If you experience a remark, or disrespectful treatment, or if you feel you are being ignored, excluded or marginalized in a course or program-related activity, please speak up. Consider talking to your instructor, but you are also welcome to contact Executive Director Christina Teller at cpteller@berkeley.edu or report an incident anonymously through this online form{:target="_blank"}.
As course staff, we are committed to creating a learning environment welcoming of all students that supports a diversity of thoughts, perspectives and experiences and respects your identities and backgrounds (including race, ethnicity, nationality, gender identity, socioeconomic class, sexual orientation, language, religion, ability, and more.) To help accomplish this:
- If your name and/or pronouns differ from those that appear in your official records, please let us know.
- If you feel like your performance in the class is being affected by your experiences outside of class (e.g., family matters, current events), please don’t hesitate to come and talk with us. We want to be resources for you.
- We (like many people) are still in the process of learning about diverse perspectives and identities. If something was said in class (by anyone) that made you feel uncomfortable, please talk to us about it.
- While the course staff understands that improving diversity, equity, and inclusion (DEI) are not enough to overcome systemic issues in academia such as racism, queerphobia, and other forms of discrimination and hatred, we also recognize the importance of DEI work.
- The Data Science Department has some resources available at https://data.berkeley.edu/about/diversity-equity-and-inclusion{:target="_blank"}.
- There’s also a great set of resources available at https://eecs.berkeley.edu/resources/students/grievances{:target="_blank"}.
- If there are other resources you think we should list here, let us know!
Below is a high-level “typical week in the course” for {{page.course.semester}}.
| Mo | Tu | We | Th | Fr | Sat | Sun |
|---|---|---|---|---|---|---|
| Live Lecture | Live Lecture | Live Lecture | Live Lecture | |||
| Discussion Section | Discussion Section | |||||
| Office Hours | Office Hours | Office Hours | Office Hours | Office Hours | ||
| Homework I due | Homework I released | |||||
| Homework II released | Homework II due | |||||
| Lab I released | Lab I due | |||||
| Lab II released | Lab II due |
- All deadlines are subject to change.
- The Office Hours schedule is on the Calendar page.
- Lectures, discussions, assignments, projects, and exams are scheduled on the Home page.
There are 4 live lectures held on Monday, Tuesday, Thursday, and Friday from 9:30am-11:00am in-person in Lewis 100. All session recordings, slides, activities, and examples will be uploaded to the course website within 24 hours of the lecture.
Lecture participation: Lecture attendance is graded, we expect you to "participate" in lecture by answering poll questions during the lecture as they are launched. We will not be offering an asynchronous lecture participation option.
- Lecture participation is graded using poll responses on a 0/1 basis. Complete at least one participation poll question during the live lecture timeslot (9:30am-11:00am on Monday, Tuesday, Thursday, and Friday). As long as you submit a response to at least one poll question in this timeframe, you will receive lecture attendance credit. In order to obtain full lecture attendance credit, students need to attend 20 lectures. This policy accommodates situations such as illness, personal emergencies, or other extenuating circumstances.
- Alternatively, students with low attendance scores may shift this portion (2.5%) of their grade onto their final exam score. The instructors will automatically determine which grading policy will maximize a student’s final grade in the course at the end of the semester.
- Please see the Policies section for more details.
Live discussion sections are one hour long, and held on Monday and Wednesdays. The goal of these TA-led sessions is to work through problems, hone your skills, and flesh out your understanding as part of a team. The problems that you solve and present as part of discussion are important in understanding course material.
The lectures, assignments, and exams of this course are structured with the expectation that all students attend discussion. The content covered in these sections is designed to solidify understanding of key lecture concepts and prepare students for homework assignments. It is to your benefit to actively participate in all discussions. Discussion attendance is graded as follows:
- Discussion attendance accounts for 2.5% of the overall grade. Each biweekly discussion will be graded on a 0/1 basis. You will only get credit for attending the discussion section that you are signed up for (except for the first discussion of the term). In order to obtain full discussion attendance credit, students need to attend 10 discussion sections. Akin to the lecture attendance policy, this policy accounts for illness, personal emergencies, or other extenuating circumstances.
- Alternatively, students with low discussion attendance may shift this portion (2.5%) of their grade onto their final exam score. The instructors will automatically determine which grading policy will maximize a student’s final grade in the course at the end of the semester.
- Please see the Policies section for more details.
Biweekly homeworks are designed to help students develop an in-depth understanding of both the theoretical and practical aspects of ideas presented in lecture. Projects are longer assignments that synthesize multiple topics.
- All homeworks and projects must be submitted to Gradescope by their posted deadlines. There may be separate coding and written Gradescope portals for the same assignment; please check that you are submitting the right part.
- Homeworks and projects have both public (visible) and hidden autograder tests. The public tests are mainly sanity checks. For example, a sanity check might verify that the answer you entered is a number as expected, and not a word. The hidden tests generally check for correctness, and are invisible to students while they are completing the assignment.
- The primary form of support students will have for homeworks and projects are office hours and Ed.
- Homeworks and projects must be completed individually, without the usage of any unauthorized resources (CourseHero, ChatGPT, etc). See the Collaboration Policy for more details.
- See the Policies section for the submission grace period.
Labs are shorter, weekly programming assignments designed to give students familiarity with new ideas. They are meant to be completed prior to homework.
- All lab assignments must be submitted to Gradescope by their posted deadlines.
- All lab autograder tests are public (visible).
- We will not be having lab sections for Data 100 this semester. Rather, we'll provide extensive lab support on Ed and accompanying video walkthroughs.
- All labs are intended to take about an hour.
- Lab submissions are mandatory and part of your grade. See the Policies section for the submission grace period.
There will be two exams in this course:
- Midterm on Friday, July 19 from 9-11 AM PT.
- Final on Thursday, August 8 from 9-11 AM PT.
All exams must be taken in-person and are a requirement for passing the course. There will be no alternate exams offered.
We want to enable everyone to succeed in this course. We encourage you to discuss course content with your friends, classmates, and course staff throughout the semester, particularly during office hours.
- All office hours will be updated on the Calendar.
- In-person course staff office hours will be held in Warren Hall 101B.
- In general, students can come to staff office hours for any questions on course assignments or material.
- Instructor office hours are generally reserved for conceptual questions, course review, course logistics, research opportunities, and career planning.
Course Communication:
-
EdStem, or Ed for short, is our course forum this semester. All course announcements will be through Ed. We are not using bCourses this semester. Please check out Ed{:target="_blank"} or the FAQ{:target="_blank"} page first before emailing course staff directly.
-
Ed is a formal, academic space. We must demonstrate appropriate respect, consideration, and compassion for others. Please be friendly and thoughtful; our community draws from a wide spectrum of valuable experiences. For further reading, please reference Berkeley’s Principles of Community{:target="_blank"} and the Berkeley Campus Code of Student Conduct{:target="_blank"}.
-
Ed is your primary platform for asking questions about the class. It is monitored daily by course staff, so questions posted to Ed will likely receive the fastest response. If you need to discuss a more sensitive matter, the following emails are monitored by a smaller subset of the teaching team:
-
-
For logistical questions: our course staff email is data100.instructors@berkeley.edu. This email is monitored by the instructors, the head TAs, and a few lead TAs.
-
For extenuating circumstances/DSP: student accommodation requests will be handled via the Accommodations Form{:target="_blank"}. Our staff email for student support and DSP accommodations is data100.support@berkeley.edu.
- Please only contact the course instructors directly for matters that require strict privacy and their personal attention.
| Category | Percentage | Details |
|---|---|---|
| Homeworks | 20% | 1 drop |
| Projects | 15% | No drop |
| Labs | 5% | 2 drops |
| Discussion Participation | 2.5% | Out of 10 sections |
| Lecture Participation | 2.5% | Out of 20 lectures |
| Midterm Exam | 20% | |
| Final Exam | 35% |
As mentioned above, students are provided with assignment drops for emergency situations that may come up unexpectedly. Only after using all drops, students facing unforeseen significant life events should complete the Accommodations Form. A course staff member will reach out to you and provide a space for conversation, as well as potentially arrange accommodations as necessary.
All assignments are due at 11:59 PM Pacific Time on the due date specified on the Home / Schedule page. The date and time of this deadline are firm. Submitting even a minute past is considered late.
Submitting by this “on-time” deadline earns an extra-credit on-time bonus, a 3% perk. This is available for homeworks, projects, and labs.
We recognize that life can be unexpected, and that you may face circumstances that prevent you from submitting your work by the posted deadline. In light of this, we offer a 1-day (24 hour) grace period for late submissions of homeworks, projects, and labs. Note that this grace period is designed to account for unexpected emergencies or technical difficulties (e.g. assignment submission errors) – you should not plan in advance to use it!
Submissions are not accepted beyond the grace period. The grace period is strictly enforced. We recommend thinking of the grace period as a backup, in case something unexpected, such as DataHub or autograding issues, comes up at the last minute when aiming for the deadline. Assignment drops are provided to students for unforeseen circumstances and/or personal emergencies, getting an extension beyond the grace period will generally not be granted. Only in case of unforeseen life events, students should complete the Accommodations Form.
If you encounter unforeseen life events at any time in the semester, please let us know. The sooner we are made aware, the more options we have available to us to help you.
{: .important } Within two business days of filling out the Accommodations Form{:target="_blank"}, we will reach out to you and provide a space for conversation, as well as potentially arrange course/grading accommodations as necessary. For more information, please email data100.support@berkeley.edu.
We recognize that at times, it can be difficult to manage your course performance — particularly in such a huge course, and particularly at Berkeley’s high standards. Sometimes emergencies just come up (personal health emergency, family emergency, etc.). Our drops policy combined with the accommodations form is meant to lower the barrier to reaching out to us, as well as build your independence in managing your academic career long-term. So please do not hesitate to reach out.
Note that accommodations are not given in case of logistical oversight, such as Datahub/Gradescope tests not passing, submitting only one portion of the homework, forgetting to save your notebook before exporting, submitting to the wrong assignment portal, or not properly tagging pages on Gradescope. It is the student’s responsibility to identify and resolve these issues in advance of the on-time deadline. We will not grant accommodations for these cases; instead, please use the grace period to cushion these submission errors.
If you are registered with the Disabled Students’ Program (DSP) you can expect to receive an email from us during the first week of classes. In this email, we will go over the extensions and other assignment and exam accommodations we will be offering you. Otherwise, email our student support team at data100.support@berkeley.edu. You are responsible for reasonable and timely communication with course staff.
Students will be allowed to submit regrade requests for the autograded and written portions of assignments in cases in which the rubric was incorrectly applied or the autograder scored their submission incorrectly. Regrades for the written portions of assignments will be handled through Gradescope, and autograder regrades via a Google Form.
Always check that the autograder executes correctly! Gradescope will show you the output of the public tests, and you should see the same results as you did on DataHub. If you see a discrepancy, ensure that you have exported the assignment correctly and, if there is still an issue, post on Ed as soon as possible.
Regrade requests will not be considered in cases in which:
- a student uploads the incorrect file to the autograder.
- the autograder fails to execute and the student does not notify the course staff before the assignment deadline.
- a student fails to save their notebook before exporting and uploads an old version to the autograder.
- a situation arises in which the course staff cannot ensure that the student’s work was done before the assignment deadline.
We will be following the EECS departmental policy on Academic Honesty{:target="_blank"}, which states that using work or resources that are not your own or not permitted by the course may lead to disciplinary actions, including a failing grade in the course.
Assignments. Data science is a collaborative activity. While you may talk with others about the homework and projects, we ask that you write your solutions individually in your own words. If you do discuss the assignments with others please include their names at the top of your notebook. Restated, you and your friends are encouraged to discuss course content and approaches to problem-solving, but you are not allowed to share your code nor answers with other students, nor are you allowed to post your assignment solutions publicly. Doing so is considered academic misconduct. We will be running advanced plagiarism detection programs on all assignments. Use of AI-assisted methods, such as ChatGPT, to generate written or code solutions to assignments is prohibited. Usage of past assignment solutions is also prohibited.
Exams. Cheating on exams is a serious offense. We have methods of detecting cheating on exams – so don’t do it! Students caught cheating on any exam will fail the course.
Plagiarism on any assignment, as well as other violations to Berkeley’s Code of Conduct{:target="_blank"}, will be reported to the Center for Student Conduct. The CSC treats most first-time offenses as a Non-Reportable Warning{:target="_blank"}. Additionally we reserve the right to give you a negative full score (-100%) or lower on the assignments in question, an F in the course, or even dismissal from the university. It’s just not worth it!
Rather than copying someone else’s work, ask for help. You are not alone in Data 100! The entire staff is here to help you succeed. We expect that you will work with integrity and with respect for other members of the class, just as the course staff will work with integrity and respect for you.
Finally, know that it’s normal to struggle. Berkeley has high standards, which is one of the reasons its degrees are valued. Everyone struggles, even though many try not to show it. Even if you don’t learn everything that’s being covered, you’ll be able to build on what you do learn, whereas if you cheat you’ll have nothing to build on. You aren’t expected to be perfect; it’s ok not to get an A.
Our Resources page lists not only course-specific academic resources such as course notes, past exams, study guides, and prerequisite review links, but also campus wellness resources on COVID-19, academic support, technology support, mental well-being, DSP accommodations, dispute resolution, social services, campus community, and basic needs. Our staff will also refer to this page when supporting you through this course.
If you are feeling overwhelmed, visit our office hours and talk with us, or fill out the Accommodations Form. We know college can be stressful and we want to help you succeed.
{: .important } We are committed to being a resource to you, but it is important to note that all members of the teaching staff for this course are responsible employees{:target="_blank"}, meaning that we must disclose any incidents of sexual harassment or violence to campus authorities. If you would like to speak to a confidential advocate, please consider reaching out to the Berkeley PATH to Care Center{:target="_blank"}.
Finally, the main goal of this course is that you should learn and have a fantastic experience doing so. Please keep that goal in mind throughout the semester. Welcome to Data 100!
Academic Honesty policy and closing words adapted from Data 8{:target="_blank"}. Course Culture inspired and adapted with permission from Dr. Sarah Chasins’ Fall 2021 CS 164 Syllabus{:target="_blank"} and Grace O’Connell, the Asssociate Dean for Inclusive Excellence.