Project: Data Questions Check-In

Python

Due end of Week 4

Project Overview

Tip

This assignment must be completed in the assignment.ipynb file provided in the GitHub repository created when you accepted this assignment.

I will NOT grade any other file.

These instructions are also included in the README.md file in the repository for your reference.

For more on connecting to the GitHub repository, see below.

The final project for this course will be a data analytics report based on a dataset of your choosing. You will be expected to explore the data and answer a question (or questions) of interest using the data. The goal is to articulate something interesting about the data using the skills you have learned in this course. In this check-in you will choose the dataset that you will use for the final project.

If you receive a C or lower on the assignment, the dataset has not been approved. You will need to resubmit the assignment with a different dataset that meets the requirements. This is the only assignment that permits resubmission.

For this project, you will seek out a dataset that interests you. The dataset can come from any source, but the dataset must include the following:

  • At least 100 rows of data
  • At least 2 numerical columns
    • Or some way to derive 2 numerical data from existing columns either by counting categorical columns or some other means. If you take this route, the means by which you will derive numerical data must be clearly explained in your notebook.
  • At least 1 categorical column with more than three unique values.
  • At least 1 categorical column that has either only two unique values (think male/female, or yes/no, etc.) or a way to group the data into two categories.
    • If you are grouping the data into two categories, the means by which you will derive the categorical data must be clearly explained in your notebook.

Include the following:

  • Read the dataset into a DataFrame using pandas and print the head of the DataFrame.
  • Explain what the dataset is and why it interests you.
  • Explain what questions you hope to answer with this dataset.

Project Data Question Rubric

Criteria 4 Points 3 Points 2 Points 1 Point
Data Criteria The Data meets the minimum criteria N/A N/A The Data does NOT meet the minimum criteria
Explanation The student effectively discusses (1) the dataset and its relationship to the topic and question, (2) the available columns that can be used for exploration of their topic, (3) demonstrates genuine familiarity with the data, and (4) writes it in narrative form. The student effectively only provides 3 of the 4 needed explanation criteria. The student effectively only provides 2 of the 4 needed explanation criteria The student effectively only proveds 1 of the 4 needed explanation criteria.
Question The student asks a clear and thoughtout question that can answered by the available data. The student asks a question but it is not clear how it relates to the data or is not thoroughly thought out. The student asks a question but it is neither clear how it relates to the data nor thoroughly thought out. There is not a question.

GitHub Classroom

This assignment uses GitHub Classroom. GitHub Classroom is a tool that helps instructors manage coding assignments using GitHub repositories. When you accept the assignment, GitHub Classroom will create a private repository for you where you can work on your code. To complete this assignment you will have to accept the assignment, clone the repository to your local machine, complete the assignment, and then commit and push your changes back to GitHub.

To accept the assignment, go to the assignment page on Canvas and click on the link to create the GitHub repository.

Note

Part of this assignment is not just completing the coding tasks, but also learning how to use GitHub and Git for version control. Make sure to follow the instructions carefully and reach out to me if you encounter any issues.

Understand, problems with Git/GitHub are not an excuse for late work. Plan ahead to ensure you have time to resolve any issues that may arise. In industry, version control is an essential skill, and being proficient with these tools is crucial for collaboration and project management. Moreover, technology issues (including those with GitHub) will never be accepted as an excuse for missing deadlines. This is a programming class. The technology is part of the assignment.

If technology difficulties arise, I’m happy to help, but before deadlines (not after).

Cloning the Repository

Once you have accepted the assignment, a new repository titled - will be created in your GitHub account. You can log in to GitHub to view the repository. You will need to clone this repository to your local machine to work on the assignment. Follow these steps to clone the repository:

  1. Open VS Code
  2. Press Ctrl+Shift+P (or Cmd+Shift+P on Mac) to open the command palette.
  3. Type Git: Clone and select it.
  4. Select Clone from GitHub...
  5. You might be prompted to sign in to GitHub if you haven’t already.
  6. After signing in to GitHub, you will need to follow steps 1-4 again to clone the repository.
  7. You should receive a list of your repositories. Select the repository for this assignment.
    1. If you do not see your repository, you can copy the URL from GitHub and paste it into the prompt in VS Code.
  8. Choose a local directory where you want to clone the repository.
    1. Choose the folder location carefully. File management is incredibly important in programming, and it is best to keep all your assignments for this class in one folder.
    2. Make sure NOT to clone the repository into another repository.
  9. Click Select Repository Location to complete the cloning process.

Committing and Pushing Changes

In order to submit your assignment, you will need to commit any changes you make to your local repository and push them to GitHub. Committing saves your changes to the local repository, while pushing uploads those changes to the remote repository on GitHub. In other words, just saving your files is not enough. Saving updates the files on your computer, but when you commit those saves, you are creating a snapshot of your project at that point in time. Think of a commit like a save point in a video game that you can always return to. Remember, you can commit multiple changes to multiple files at once You should commit your changes to the repository often, especially after completing significant portions of the assignment. To do so, follow these directions.

  1. Click the Source Control icon in the Activity Bar on the side of VS Code (it looks like a branch with a dot at the end). You should see a list of files that have been changed.
  2. Stage changes to be committed. Not all files need to be in every commit. You can stage individual files by hovering over the file name and clicking the plus (+) icon that appears, or you can stage all changes at once by clicking the plus (+) icon next to the “Changes” header.
  3. Enter a commit message in the text box at the top of the Source Control panel that describes the changes you made. A good commit message is concise yet descriptive, such as “Completed function to calculate average” or “Fixed bug in data processing loop.”
  4. Press the blue button below the commit message box that looks like a checkmark to commit your changes.
  5. After committing, these changes are still only saved locally. The blue button below the commit message input box now states “Sync Changes” with an up and down arrow icon. Click this button to push your committed changes to the remote repository on GitHub. You may be prompted to sign in to GitHub again if you haven’t done so recently.
  6. Check the GitHub repository online to ensure your changes have been pushed successfully. If you cannot see your changes online, try refreshing the page. If you still cannot see your changes, the process was not completed successfully, and you should try pushing again.