- Course Meetings
- Getting Started
- Textbooks and Materials
- Assignments and Assessments
- Weekly Schedule
- Collaboration Policy and Academic Integrity
Welcome to DSC 10 at UC San Diego! This course aims to teach you how to draw conclusions about data. We will learn how to explore data and make predictions about data. Programming is a useful tool to help us analyze large data sets, and so we will learn how to program in Python towards this goal. We will learn some of the core techniques of data science, and we will practice applying them to real data sets from a variety of different disciplines.
Prerequisites: None. This course is an introduction to data science with no prior background assumed beyond high school algebra. If you are not planning on entering the DSC major/minor and have already taken a programming class and a statistics class, you may wish to take a more advanced course. If you are a DSC major/minor, DSC 10 is absolutely required, as later courses heavily reference its specific content.
There are three lecture sections, all of which will be taught in person.
- A00: MWF 10-10:50AM, Ridge Walk Academic Complex 0121, Janine Tiefenbruck
- B00: MWF 11-11:50AM, Ridge Walk Academic Complex 0121, Janine Tiefenbruck
- C00: MWF 9-9:50AM, Cognitive Science Building 001, Suraj Rampure
All lecture sections will cover the same content, but due to space constraints you must attend the lecture section you’re enrolled in. Email the instructors if you have any concerns about this policy.
There are three discussion sections, two of which will be taught in person while the third will be taught remotely.
- A01: Monday 3-3:50PM, Ridge Walk Academic Complex 0121
- B01: Monday 4-4:50PM, Ridge Walk Academic Complex 0121
- C01: Tuesday 5-5:50PM, Remote via Zoom (see Canvas for Zoom link)
You can attend any discussion section, not just the one you’re enrolled in.
Discussion section focuses on solving concrete problems using the techniques introduced in lecture, and is excellent preparation for the week’s assignments, as well as exams. We expect that students in this class will have a wide range of backgrounds and relevant experience. If you are new to programming, you will especially benefit from taking advantage of the opportunity to attend discussion section and review the material from lecture. Attendance in discussion is highly recommended but not required.
All lecture and discussion sections will be recorded and posted for students in other time zones who cannot attend synchronously. The remote discussion section’s recording will be posted on Canvas, and all other recordings will be posted on podcast.ucsd.edu. If you are able, you are encouraged to attend synchronously to ask questions and to participate in concept-check polls and discussion.
Note that the schedule of courses also includes a designated Laboratory time for all three sections on Friday – we will not be utilizing this time for anything this quarter, so you can ignore this Laboratory time and schedule other things during this time.
In order to provide you with help on assignments and concepts, the teaching team will be holding several office hours throughout the week. The office hours schedule, complete with locations/Zoom links, can be found on the Canvas calendar.
There are two types of office hours:
- Remote office hours: these are held on Zoom. Join the Zoom call by clicking the link within the calendar event on Canvas.
- In-person office hours: these are held in-person on the second floor of the east wing of the San Diego Supercomputer Center (map). Enter SDSC from the main entrance on Hopkins Drive, take the elevator up to the second floor, turn left at the kitchen, and meet in the common area. You may need a code to enter the building; you can find this code on Canvas embedded within each calendar event. This code must not be shared with anyone outside of the class. Make sure to hit the # key after entering the code.
- In order to actually get help in-person, you’ll need to join the queue at autograder.ucsd.edu and make a ticket.
Since this is a large class, we will break up students into smaller teams to simulate the environment of a small class within the big one. This will be an opportunity for you to get to know the people on your team and the tutor assigned to mentor your team. For data science majors (minors), it will be valuable to form connections with people in your major (minor) who have common interests, and perhaps down the road you’ll pursue a project together or work as teammates in another data science course.
You will be placed into a team with students from your assigned lecture, and each team will be assigned a tutor as a mentor to oversee the team and help answer questions. Your team assignment is available here, sorted by PID.
Within our Campuswire discussion board, each team will have a private chatroom. We ask that you first post questions to your team’s chatroom before posting on the main discussion board. If your question gets resolved within the chatroom, great! If not, then feel free to post to the main discussion board. Research shows that discussion boards work best with moderate size discussion groups, and we encourage you to be an active participant on Campuswire!
For the midterm and final project, you will be able to work with a partner, but that partner must come from your same team. You can use your team’s Campuswire chatroom to connect with potential partners. You are not committed to the same partner for both projects. This is to encourage everyone to be a good partner and pull their weight. If it’s not working out, just look for a new partner within your team.
As you’ll learn soon, in this class we’ll be heavily using a Python library called babypandas. Going with the theme of baby animals, the teams will have the following names:
- Joeys (baby kangaroos)
- Fawns (baby deer)
- Piglets (baby pigs)
- Tadpoles (baby toads)
- Ducklings (baby ducks)
- Lambs (baby sheep)
- Bunnies (baby rabbits)
- Porcupettes (baby porcupines)
- Puppies (baby dogs)
- Colts (baby horses)
We encourage friendly competition between the teams!
In order to get started in this class, you’ll need to set up a few things.
We’ll be using Campuswire as our course message and discussion board. Please make a post on Campuswire if you have any questions about course content or logistics, or if you need to get in touch with the staff. If you didn’t already get an invitation to our Campuswire course, sign up here. Make sure to join the chatroom for your assigned team as well as the #autograder chatroom.
You’ll submit labs, homeworks, and projects to Gradescope. Most questions will be autograded, meaning that a computer will run your code and check that it passes certain tests to verify that it works properly. If you didn’t already get an invitation to our Gradescope course, reach out to the instructors.
Most assignments in this course will involve programming in Python. DataHub (datahub.ucsd.edu) is UCSD’s online data science and machine learning platform, where you will work on assignments. Everything you need for this course is already loaded into DataHub, so you can get started on assignments quickly without having to download anything. You should be able to log in to DataHub and see DSC 10 listed among the course environments, starting on the first day of classes. If you find that you are not able to, first check the FAQs for some common login problems, and if you’re still having trouble, please contact us on Campuswire. To access assignments and course materials, first log into DataHub, then click the corresponding link on the course website.
All students must complete an Integrity of Scholarship Agreement through this required form.
The primary textbook for this class is Dive Into Data Science (DDS), a free online textbook that is currently under development specifically for DSC 10.
As the primary textbook is still a work in progress and doesn’t yet cover everything we cover in this course, we’ll also use a supplementary textbook, Computational Inferential Thinking (CIT), which is again a free online book. This book comes from Berkeley’s version of this course and uses slightly different Python commands, but the underlying concepts are the same.
You will also need access to a computer and a stable internet connection to participate in this course. UCSD has a Laptop Loaner program which may be helpful, but you should also contact us if you have any concerns about access to technology. You will not need a webcam for this course.
Weekly lab assignments are a required part of the course and will help you develop fluency in Python and working with data. The labs are designed to help you build the skills you need to complete homework assignments and projects, in a low-stress setting.
As you complete the lab, you’ll be able to run a sequence of tests, which check to make sure that your answers are correct. If you complete the assignment and all the tests pass, you’ll get a perfect score! Each person must complete and submit the lab on their own, but you are welcome to discuss the lab with others. You cannot copy or share answers, however.
To submit a lab, follow the instructions in the assignment to upload your notebook to Gradescope, which will run automated tests and assign your score. Lab assignments will usually (not always!) be due on Tuesdays at 11:59pm San Diego time. We will release lab assignments roughly a week before they’re due. The lowest lab score is dropped from the grade calculation.
Weekly homework assignments build off of the skills you have developed in labs. Homeworks will reinforce concepts from class, explore new ideas, and provide hands-on experience working with data.
An important difference between labs and homeworks lies in the way tests are run. Unlike the tests in the labs, the tests in the homework cannot be used to guarantee that you have the correct answers. The tests in the homework only check to make sure that your answer is reasonable, not that it is correct. For example, if a homework question asks you to calculate a percent, the test in the homework might check that the answer you provide is a number between 0 and 100. You should make sure that all the tests pass before submitting your homework, but this will not guarantee a perfect score.
After you submit your homework to Gradescope, and after the deadline for submissions has passed, a new set of hidden tests will be run to make sure that you have the correct answers. In the percent example above, the hidden test might check that your answer equals 56, for example. Your score for the assignment will be based on the results of the hidden tests, which won’t be available immediately after submission. So if you see a perfect score upon submission, this only means that you’ve passed the formatting tests, not the hidden correctness tests that determine your score.
You must work on homework assignments alone. To submit a homework, follow the instructions in the assignment to upload your notebook to Gradescope. Check back after the deadline to see your score, based on the hidden correctness tests. Homeworks will be due on Saturdays at 11:59pm San Diego time. We will release homework assignments roughly a week before they’re due. The lowest homework score is dropped from the grade calculation.
This class has two projects, a midterm project and a final project. Projects are like more challenging homeworks. They are longer than a typical homework, and they require you to pull together ideas from previous weeks, rather than just the last week. Projects also give you a chance to explore a data set in-depth, which can be a lot of fun! Project tests are like homework tests: the provided tests only check if your answer has the correct format, not if it is correct. You’ll only be able to see your score on the project after the deadline, once all projects are submitted and the hidden correctness tests have been run.
Unlike homeworks, you may work with a partner, though your partner must come from your team. If you choose to work with a partner, you should practice pair programming. This means that you should work on the assignment synchronously, discussing each problem together and writing each answer together, taking turns of who is in control of the coding. Please read the section of this website dedicated to pair programming to learn more about how this works, and some of the benefits of working in pairs. If working with a partner, only one of you should submit the assignment.
Labs, homeworks, and projects must be submitted by the 11:59pm San Diego time deadline to be considered on time. You may turn them in as many times as you like before the deadline, and only the most recent submission will be graded, so it’s a good habit to submit early and often. If you make a submission after the deadline, your assignment will be counted as late.
You have six “slip days” to use throughout the quarter. A slip day extends the deadline of any one homework, lab, or project by 24 hours. If you need to extend the deadline by 48 hours, you can, but this costs you three slip days. You cannot turn in any assignments more than 48 hours late.
Slip days are applied automatically at the end of the quarter, and you don’t need to ask in order to use one. It’s your responsibility to keep track of how many you have left. If you run out of slip days and submit an assignment late, it may still be graded so that you’ll see what questions you missed, but the grade will be changed to a zero at the end of the quarter. If you use more than six slip days, we will count the first six as slip days and late assignments after that will get zero scores.
Slip days are designed to be a transparent and predictable source of leniency in deadlines. You can use a slip day if you are too busy to complete an assignment on its original due date (or if you forgot about it). But slip days are also meant for things like the internet (or the DataHub server) going down at 11:58 PM just as you go to submit your homework. Slip days are meant to be used in exceptional circumstances, so you probably should not need to use all six, but if you have something going on in your life that is impeding your ability to do your classwork on time, please reach out to us as soon as possible so we can work something out.
This class has one midterm exam and one final exam. Exams are cumulative, though the final exam will emphasize material after the midterm.
Exams will be administered remotely through Gradescope or a similar online platform. Exams will be open-notes, open-book, open-internet, with the limitation that you must take the exam alone without communicating with any other person.
Both exams must be taken exactly during the scheduled slot, no exceptions.
- Midterm Exam: Wednesday, October 27th, during your assigned lecture slot (50 minutes)
- Final Exam: Saturday, December 4th, 11:30AM-2:30PM
To summarize all of the events and deadlines, refer to this general weekly schedule (which is subject to change in any given week):
|Lab due||Homework due|
Your mastery of class material will be assessed in the following ways, and final grades will be computed as follows:
|Lab Assignments||15%||drop lowest score|
|Homework Assignments||35%||drop lowest score|
- Each lab and each homework assignment will be worth the same amount, regardless of the number of points it is graded out of.
- You must score at least 55% on the final exam to pass the course. If you score lower than 55% on the final, you will receive an F in the course, regardless of your overall average.
If you’d like to request a regrade on any assignment, you must do so within one week of the assignment being graded. If you think there is a problem with the autograder, please post in the #autograder chatroom on Campuswire. If you think there is a problem with how your written question was graded, submit a regrade request through Gradescope.
We will use a standard scale for assigning letter grades. If you are taking the course P/NP, you will receive a grade of P if you meet the criteria for a C- grade, otherwise you will receive a grade of NP.
If you have extenuating circumstances that prohibit your completion of coursework, you may be eligible for an Incomplete grade. If you are considering using this option, the best thing you can do is let us know right away, and we can help you decide if this is an appropriate course of action. If you have any doubt about your ability to perform satisfactorily in this course due to something outside of your control, please contact us as soon as possible so we can figure out a plan.
The basic rule for DSC 10 is: Work hard. Make use of the expertise of the staff to learn what you need to know to really do well in the course. Act with integrity, and don’t cheat.
If you do cheat, we will enforce the UCSD Policy on Integrity of Scholarship. This means you will likely fail the course and the Dean of your college will put you on probation or suspend or dismiss you from UCSD. Students agree that by taking this course, their assignments will be submitted to third party software to help detect plagiarism.
Academic integrity is an issue that is pertinent to all students on campus. When students act unethically by copying someone’s work, taking an exam for someone else, plagiarizing, etc., these students are misrepresenting their academic abilities. This makes it impossible for instructors to give grades (and for the University to give degrees) that reflect student knowledge. This devalues the worth of a UCSD degree for all students, making it imperative for the the campus as a whole to enforce that all members of this community are honest and ethical. We want your degree to be meaningful and we want you to be proud to call yourself a graduate of UCSD!
The UCSD Policy on Integrity of Scholarship and this syllabus list some of the standards by which you are expected to complete your academic work, but your good ethical judgment (or asking us for advice) is also expected as we cannot list every behavior that is unethical or not in the spirit of academic integrity. Ignorance of the rules will not excuse you from any violations.
In DSC 10, you can read books, surf the web, talk to your friends and the DSC 10 staff to get help understanding the concepts you need to know to complete your assignments. However, all code must be written by you (or, in the instance of projects, together with your pair programming partner).
The following activities are considered cheating and are not allowed in DSC 10 (not an exhaustive list):
- Using or submitting code acquired from other students (except in the instance of projects, your pair programming partner), the web, or any other resource not officially sanctioned by this course
- Posting your code online, including on Campuswire, unless privately to instructors only
- Having any other person complete any part of your assignment on your behalf
- Completing an assignment on behalf of someone else
- Providing code, exam questions, or solutions to any other student in the course
- Splitting up project questions with your pair programming partner and each working on different questions
- Collaborating with others on exams
The following activities are examples of appropriate collaboration and are allowed in DSC 10 (not an exhaustive list):
- Discussing the general approach to solving homework problems or projects
- Talking about problem-solving strategies or issues you ran into and how you solved them
- Discussing the answers to exams with other students who have already taken the exam after the exam is complete
- Using code provided in class, by the textbook or any other assigned reading or video, with attribution
- Google searching for documentation on Python or babypandas
- Working together with other students on lab assignments without copying or sharing answers
- Posting a question about your approach to a problem in a class discussion forum, without sharing your code
The best way to avoid problems is by using your best judgement and remembering to act with Honesty, Trust, Fairness, Respect, Responsibility and Courage. Here are some suggestions for completing your work:
- Don’t look at or discuss the details of another student’s code for an assignment you are working on, and don’t let another student look at your code.
- Don’t start with someone else’s code and make changes to it, or in any way share code with other students.
- If you are talking to another student about an assignment, don’t take notes, and wait an hour afterward before you write any code.
Students requesting accommodations for this course due to a disability or current functional limitation must provide a current Authorization for Accommodation (AFA) letter issued by the Office for Students with Disabilities (OSD), which is located in University Center 202 behind Center Hall. If you have an AFA letter, please make arrangements to meet with the instructor and with the Data Science OSD Liaison by the end of Week 2 to ensure that reasonable accommodations for the quarter can be arranged. The Data Science OSD Liaison can be reached at email@example.com.
We are committed to an inclusive learning environment that respects our diversity of perspectives, experiences, and identities. Our goal is to create a diverse and inclusive learning environment where all students feel comfortable and can thrive. If you have any suggestions as to how we could create a more inclusive setting, please let us know. We also expect that you, as a student in this course, will honor and respect your classmates, abiding by the UCSD Principles of Community. Please understand that others’ backgrounds, perspectives and experiences may be different than your own, and help us to build an environment where everyone is respected and feels comfortable.