Welcome to STA 113FS

Lecture 1

Dr. Mine Çetinkaya-Rundel

Duke University
STA 113 - Fall 2023

Course Details

Teaching team

Instructor

Dr. Mine Çetinkaya-Rundel

Old Chem 213

mc301@duke.edu

Teaching assistant

Shelby Tisdale

shelby.tisdale@duke.edu

Learning objectives

  • Learn a modern toolkit commonly used in data science research and careers (R, RStudio, Quarto, Git, GitHub).
  • Introduce students to the ideas and methods of data visualization in a comprehensible reproducible way using this toolkit.
  • Understand the principles of designing and creating data visualizations.
  • Evaluate, critique, and improve upon one’s own and others’ data visualizations through an iterative process.
  • Use data visualization to look for and answer questions of societal importance and of interest to students.

But first…

Let’s play a game!

Course components

Course website

aka “the one link to rule them all”

Lectures

  • In person

  • Attendance is required (as long as you’re healthy!)

  • A little bit of everything:

    • Traditional lecture
    • Live coding + demos
    • Short exercises + solution discussion
  • Recordings will be posted after class – to be used for review + make-up if you can’t make it to class due to health reasons, they’re not an alternative to class attendance

Announcements

  • Posted on Canvas (Announcements) and sent via email, be sure to check both regularly

  • I’ll assume that you’ve read an announcement by the next “business” day

Diversity and inclusion

It is my intent that students from all diverse backgrounds and perspectives be well-served by this course, that students’ learning needs be addressed both in and out of class, and that the diversity that the students bring to this class be viewed as a resource, strength and benefit.

  • If you have a name that differs from those that appear in your official Duke records, please let me know! Add your name pronunciation to your Canvas and Slack profiles.

  • Please let me know your preferred pronouns and add these to your Canvas and Slack profiles.

  • If you feel like your performance in the class is being impacted by your experiences outside of class, please don’t hesitate to come and talk with me. I want to be a resource for you. If you prefer to speak with someone outside of the course, your advisers and deans are excellent resources.

  • I (like many people) am 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 me about it.

Accessibility

  • The Student Disability Access Office (SDAO) is available to ensure that students are able to engage with their courses and related assignments.

  • We will have in class exams. If you need special accommodations, please book the testing center ASAP!

  • I am committed to making all course materials accessible and I’m always learning how to do this better. If any course component is not accessible to you in any way, please don’t hesitate to let me know.

Assessments

Attendance + participation (10%)

Required throughout the semester as well as on Slack

If you attend at least 80% of the classes, you’ll get all available points for this component.

HW (25%)

Submitted as GitHub repos, individual, can discuss with classmates

Lowest HW score is dropped, whether it’s an actual low score or a 0 from not turning it in.

Exams

  • Two exams, each 15%

  • Each exam comprised of two parts:

    • In class: 75 minute in-class exam. Closed book, one sheet of notes (“cheat sheet”, no larger than 8 1/2 x 11, both sides, must be prepared by you) – 70% of the grade

    • Take home: 48 hours to complete the take home portion. The take home portion will follow from the in class exam and focus on the analysis of a dataset introduced in the take home exam – 30% of the grade

Exam dates cannot be changed and no make-up exams will be given. If you can’t take the exams on these dates, you should drop this class.

Projects

  • Project 1 (15%)

    • Same data, limited methods
  • Project 2 (20%)

    • Dataset of your choice, method of your choice
    • New team
  • Both projects have a presentation and write-up

  • Interim deadlines, peer review on content, peer evaluation for team contribution

  • Some class sessions allocated to working on projects, doing peer review, getting feedback from TA and instructor

Presentation dates cannot be changed. If you can’t present on that date, you should drop this class.

Teams

  • Teamwork
    • Projects (required), in class exercises (recommended)
    • Assigned different teams for each project
    • Peer evaluation during teamwork and after completion
  • Expectations and roles
    • Everyone is expected to contribute equal effort
    • Everyone is expected to understand all code turned in
    • Individual contribution evaluated by peer evaluation, commits, etc.

Course policies

COVID policies

  • Wear a mask if the university requires

  • Stay home if you’re sick and follow guidance

  • Read and follow university guidance

Late work policy

  • Interactive tutorials: Late submissions past the hard deadlines not accepted

  • HW:

    • Late, but within 24 hours of deadline: -20% of available points

    • Any later: No credit, and we will not provide written feedback

    • Note that lowest HW score will be dropped, even if that score is a 0

  • Project write-ups:

    • Late, but within 24 hours of deadline: -20% of available points
    • Any later: No credit, and we will not provide written feedback
  • Project presentation: Late submissions not accepted

  • Peer evaluation:

    • Late submissions not accepted
    • Must turn in peer evaluation if you want your own score from others

Collaboration policy

  • Only work that is clearly assigned as team work should be completed collaboratively (projects)

  • Exams must be completed individually, you may not discuss answers with teammates, clarification questions should only be asked to myself and the TA

  • HW must be completed individually. You may not directly share answers / code with others, however you are welcome to discuss the problems in general and ask for advice

Sharing / reusing code policy

  • We are aware that a huge volume of code is available on the web, and many tasks may have solutions posted

  • Unless explicitly stated otherwise, this course’s policy is that you may make use of any online resources (e.g., StackOverflow) but you must explicitly cite where you obtained any code you directly use or use as inspiration in your solution(s)

  • Any recycled code that is discovered and is not explicitly cited will be treated as plagiarism, regardless of source

Generative AI policy

You should treat generative AI, such as ChatGPT, the same as other online resources. There are two guiding principles that govern how you can use AI in this course:1

(1) Cognitive dimension: Working with AI should not reduce your ability to think clearly. We will practice using AI to facilitate—rather than hinder—learning.

(2) Ethical dimension: Students using AI should be transparent about their use and make sure it aligns with academic integrity.

  • ✅ AI tools for code: You may make use of the technology for coding examples on assignments; if you do so, you must explicitly cite where you obtained the code. Any recycled code that is discovered and is not explicitly cited will be treated as plagiarism.

  • ❌ AI tools for narrative: Unless instructed otherwise, you may not use generative AI to write narrative on assignments. In general, you may use generative AI as a resource as you complete assignments but not to answer the exercises for you. You are ultimately responsible for the work you turn in; it should reflect your understanding of the course content.

Academic integrity

To uphold the Duke Community Standard:

  • I will not lie, cheat, or steal in my academic endeavors;
  • I will conduct myself honorably in all my endeavors; and
  • I will act if the Standard is compromised.



most importantly:

ask if you’re not sure if something violates a policy!

Support

Office hours

  • Mine: TBA

  • Shelby: Thu 3-4 pm in Old Chem 213 and Sun 7 - 8 pm on Zoom (link to be shared)

  • + lots more resources listed on the syllabus!

Wellness

I want to make sure that you learn everything you were hoping to learn from this class. If this requires flexibility, please don’t hesitate to ask.

  • You never owe me personal information about your health (mental or physical) but you’re always welcome to talk to me. If I can’t help, I likely know someone who can.

  • I want you to learn lots of things from this class, but I primarily want you to stay healthy, balanced, and grounded.

Course Tools

RStudio

  • Browser based RStudio instance(s) provided by Posit

  • Requires internet connection to access

  • Provides consistency in hardware and software environments

  • Local R installations are fine but we will not guarantee support

Slack

  • Online forum for asking and answering questions

  • Private repo in the course organization

  • You will need to join the course organization for access

  • Ask and answer questions related to course logistics, assignment, etc. here

  • Personal questions (e.g., extensions, illnesses, etc.) should be via email to me

  • Once you join, browse the channels to make sure you’re posting questions in the right channel, update your profile with your name, photo/avatar of you that matches your GitHub profile, and your pronouns

  • Unfortunately Slack is not the best place to in-depth questions, but it’s a great place for real-time connection and collaboration

GitHub

  • GitHub organization for the course

  • All of your work and your membership (enrollment) in the organization is private

  • Each assignment is a private repo on GitHub, I distribute the assignments on GitHub and you submit them there

  • Feedback on assignments is given as GitHub issues, scores recorded on Canvas Gradebook

GitHub username advice

Some brief advice about selecting your account names (particularly for GitHub),

  • Incorporate your actual name! People like to know who they’re dealing with and makes your username easier for people to guess or remember

  • Reuse your username from other contexts, e.g., Twitter or Slack

  • Pick a username you will be comfortable revealing to your future boss

  • Shorter is better than longer, but be as unique as possible

  • Make it timeless. Avoid highlighting your current university, employer, or place of residence

To do before…

To do before…

we move on

See course announcement (on Canvas or in your email) and click on the links to

  • Log in to Posit Cloud – and update your profile
  • Log in to Slack – and update your profile with your photo, pronouns, name pronunciation
  • Complete the Getting to know you survey on Canvas

the next class on Thursday

  • Read the syllabus

  • Complete the readings

the end of the week

  • Get started on the first HW assignment

Wrap up

Next time

Meet the computational tools for the course: R and RStudio