class: center, middle, inverse, title-slide # welcome ### 2021-08-25 --- class: middle, inverse # Course Details --- ## Teaching team ### Instrutor * Dr. Mine Çetinkaya-Rundel - mc301@duke.edu ### Teaching assistants * Jennifer Kampe * Vittorio Orlandi --- ## Timetable * Lectures (weekly) - Wednesdays, 12:00 - 1:15 pm - Link Classroom 3 - Fridays, 12:00 - 1:15 pm - Link Classroom 3 * Labs (weekly) - Mondays, 12:00 - 1:15 pm - Link Classroom 3 --- ## Themes: what, why, and how - **What:** the plot - Specific types of visualizations for a particular purpose (e.g., maps for spatial data, Sankey diagrams for proportions, etc.) - Tooling to produce them (e.g., specific R packages) -- - **How:** the process - Start with a design (sketch + pseudo code) - Pre-process data (e.g., wrangle, reshape, join, etc.) - Map data to aesthetics - Make visual encoding decisions t(e.g., address accessibility concerns) - Post-process for visual appeal and annotation -- - **Why:** the theory - Tie together "how" and "what" through the grammar of graphics --- class: inverse .xlarge[.hand[but first...]] -- <img src="images/charty-party.png" width="50%" style="display: block; margin: auto 0 auto auto;" /> --- class: middle, inverse # Course components --- ## Course website .center[.large[[vizdata.org](https://www.vizdata.org/)]] .center[.hand[aka "the one link to rule them all"]] .center[ <iframe width="900" height="450" src="https://www.vizdata.org/" frameborder="0" style="background:white;"></iframe> ] --- ## Lectures - Lectures will be in person this semester - Recordings will be automatically posted after class - Attendance is expected (as long as you're healthy!) - A little bit of everything: - Traditional lecture - Live coding + demos - Short exercises + solution discussion --- ## Labs - Attendance is expected - Opportunity to work on course assignments with TA support - Opportunity to work with teammates on projects --- ## Community participation - I'll try to do a live stream in alternating weeks for the these two community projects (schedule TBA): - [TidyTuesday](https://github.com/rfordatascience/tidytuesday) - New dataset every week for wrangling, visualizing, modeling - [Recreation Thursday](https://twitter.com/_natalie_oshea/status/1400526683170541570) - Piece of art to recreate/remix, every two weeks - I encourage you to participate, or at a minimum, browse others' contributions on Twitter with [#TidyTuesday](https://twitter.com/search?q=%23TidyTuesday&src=typed_query&f=live) and [#RecreationThursday](https://twitter.com/search?q=%23RecreationThursday&src=typed_query&f=live) --- ## Announcements - Posted on Sakai (Announcements tool) 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! You’ll be able to note this in the Getting to know you survey. - Please let me know your preferred pronouns. You’ll also be able to note this in the Getting to know you survey. - 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)](https://access.duke.edu/students) is available to ensure that students are able to engage with their courses and related assignments. - 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. --- class: middle, inverse # Assessments --- ## Assessments - Reading quizzes: - Online, individual - Cover reading that is due since the previous quiz and up to and including the deadline for the given quiz - Due by 12pm ET (beginning of class) on the indicated day on the course schedule - Lowest dropped - Homework assignments: - Submitted on GitHub, individual - Lowest dropped - Projects: - Submitted on GitHub, team-based - Interim deadlines, peer review on content, peer evaluation for team contribution --- ## Teams - Team assignments - In class exercises and projects - 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. --- ## Project 1 - Same data, different results - Presentation and write-up - Wrapped up before Fall break --- ## Project 2 - The world is your oyster! (and more details TBA) - Presentation and write-up - Wrapped up on the last day of classes --- ## Grading This course is assessed 100% on your coursework (there is no exam). We will be assessing you based on the following assignments, <br/> |Assignment|Type |Value | n |Due | |:---------|:----------|:------|:---|---------------------| |Reading quizzes |Individual |12% | 6 | ~ Every other week | |Homeworks |Individual |48% | 6 | ~ Every other week | |Project 1 | Team |15% | 1 | ~ Week 4 and 6 | |Project 2 | Team |25% | 1 | ~ Week 11 and 15 | --- class: middle, inverse # Course policies --- ## COVID policies - Wear a mask at all times! - Read and follow university guidance --- ## Late work policy - Reading quizzes: Late submissions not accepted - Homework assignments: - Late, but same day (before midnight): -10% of available points - Late, but next day: -20% of available points - Two days late or later: No credit, and we will not provide written feedback - Project presentations: Late submissions not accepted - Project write-ups: - Late, but same day (before midnight): -10% of available points - Late, but next day: -20% of available points - Two days late or later: No credit, and we will not provide written feedback - 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) - Reading quizzes must be completed individually, you may not discuss answers with teammates, clarification questions should only be asked to myself and the TAs - Homeworks 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. RStudio Community, StackOverflow, etc.) 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 --- ## 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. --- class: middle .hand[.large[most importantly: ask if you're not sure if something violates a policy!]] --- ## Learning during a pandemic 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 during this crisis. --- class: middle, inverse # Support --- ## Office hours - Mine: on Zoom - 3-4pm on Tuesdays - 9:30-10:30am on Fridays - Jennifer: on Zoom - 5-6pm on Thursdays - Vittorio: at Old Chem 203B - 2-3pm on Mondays - 11am-12pm on Tuesdays - R TA: TBA - and lots more resources listed on the [syllabus](https://www.vizdata.org/syllabus.html#support) --- class: middle, inverse # Course Tools --- ## RStudio .center[.large[https://cmgr.oit.duke.edu/containers]] <br> - Browser based RStudio instance(s) provided by Duke OIT - Requires internet connection to access - Provides consistency in hardware and software environments - Local R installations are fine but we will not guarantee support --- ## GitHub .center[.large[https://github.com/vizdata-f21]] <br> - 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, only points recorded on Sakai gradebook .task[ Fill out the *Getting to know you* survey for collection of your account names, later this week you will be invited to the course organization. ] --- ## Username advice .hand[in case you don't yet have a GitHub account...] 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 --- ## GitHub Discussions .center[.midi[https://github.com/vizdata-f21/discussion/discussions]] <br> - 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 .task[ Demo on Friday, but it's basically your standard online course discussion forum meets GitHub issues meets StackOverflow/RStudio Community... ] --- class: middle, inverse # Before Friday --- ## Before Friday - Create a GitHub account if you don't have one - Complete the [*Getting to know you* survey](https://sakai.duke.edu/samigo-app/servlet/Login?id=6fa7ebf3-01af-42a6-91ba-3e813d3901221629867759400) - Read the [syllabus](https://www.vizdata.org/syllabus.html) - Complete the [reading](https://www.vizdata.org/schedule.html): [Wickham et al., Chp 13](https://ggplot2-book.org/mastery.html) - Make sure you can login in to RStudio and reserve a container for STA 313: [cmgr.oit.duke.edu/containers](https://cmgr.oit.duke.edu/containers)