This course familiarizes the you with the process of answering questions using data. The projects are hands-on and open-ended. The projects attempt to answer the three big questions:
The data used to answer the questions will range from real-world government data to tweets about UCSD to sound recordings.
By the time you finish this class, you will be able to:
Prerequisites: Concurrent enrollment in DSC 10, or completion of DSC 10.
Instructor: Aaron Fraenkel
Lecture: Tuesday/Thursday, 5:00-6:20 pm, EBU3B 4140
Office Hours: TBA, EBU3B 4104
Course content (projects, data, links to reading) is found on the following github repository: https://github.com/afraenkel/DSC96.
This class operates as a data science lab class, meaning that the bulk of time in class is spent doing data science. Formal lectures will be minimal, and meant to help you understand the tasks and the context.
Unless we get behind, there should not be mandatory coding or analytics work outside of class (though you are encouraged to expand on the projects and see how much you can do!). There is significant reading outside of class, and it is important to keep up with the reading because of the limited formal instruction during class time.
Projects are worked on during class and must be turned in to the instructor via email by the due date below. Please include "[CSE 91 Fa18 Project]" in the subject line and attach Tableau workbook or Jupyter notebook. You should not need to work on the projects outside of class, but are encouraged to expand on the project and clean up the presentation if you are motivated. A little extra work can make a great project to show off on your resume.
Due Dates:
Each week, at least 24 hours before the start of the Thursday class, you must email me a paragraph or two about the weekly reading. Please include "[CSE 91 Fa18 Journal]" in the subject line. The goal of this is to have a more in-depth conversation than our class time allows. Think of these journals more as emails to discuss something you read with a colleague than as a formal essay.
The topic is up to you, but examples include:
I may bring up what you write to me in class unless you explicitly ask me in that email not to.
This class is graded on a Pass/Not Pass scale. Your course grade consists of the following components:
10% Class Participation
20% Journals
30% SDPD traffic stops Tableau project
20% Best assignment of “Why did it happen?”
20% SDPD traffic stops final project
The final grade is computed using the following range:
Pass 70%-100%
Not Pass 0%-69%
Attendance is critical because the bulk of the coding happens in a collaborative manner during class time. Of course, you may have to miss class due to illness, a family emergency, or similar reason. If this happens, you should let the instructor know by email as soon as possible (preferably before class). You will still be responsible for completing the in-class work. Without the collaboration and explanations that happen in class, this will be much more difficult, so I strongly recommend coming to the office hours for help. In-class assignments from a missed class will not be accepted after the following class meeting.
Some coding will be by yourself, and some will be paired programming, meaning that you will work together with a partner to complete tasks. In both cases you are encouraged to ask for help from the instructor or from other students. This is a collaborative environment, which means that while in this classroom it is ok to show your work to other students and discuss it openly.
However, even in this collaborative environment, the work you do must be your own. Specifically, you must do the actual work of completing the assignment (i.e. typing out the code, moving the mouse) and understand what your code or analysis is doing.
If you are unsure about if what you are doing is ok, just ask! You will never be reprimanded in this class for asking for clarification. Also note that this is likely a different standard than your other classes.
I am committed to an inclusive learning environment that respects our diversity of perspectives, experiences and identities. You, as a student in this course, are also responsible for maintaining an environment where your fellow students feel safe and respected.
In my opinion, the key to this is recognizing the inherent worth and dignity of every person. If there is a way you could feel more included please let me know, either in person, via email/discussion board, or even in a note under the door.
The Office for Students with Disabilities (OSD), an Academic Affairs department, is responsible for the review of medical documentation and the determination of reasonable accommodations based on a disability. Authorization for Accommodation (AFA) letters are issued by the OSD and given to undergraduate, graduate, and Professional School students directly. If you have an AFA letter, meet with the CSE Student Affairs representative, and schedule an appointment with your instructor by the end of Week 2 to ensure that reasonable accommodations for the quarter can be arranged.
For this class, the key to academic integrity is accurately representing the status and authorship of your work. I strongly encourage you to read the official UCSD policy on integrity of scholarship.
Remember, Academic Integrity is about doing your part to act with Honesty, Trust, Fairness, Respect, Responsibility and Courage.