chdl17 / activity06-logistic-regression

Activity 06 - Logistic Regression

This activity is intended to be completed in one week - outside of class preparation work and three 75-minute class meetings. On our Blackboard course site you were provided with items to read, watch, and do prior to attempting this activity. Do not proceed in this activity until you have minimally:

1. (Day 1 portion) Read ISL Sections 4.3.0 - 4.3.3.
2. (Day 2 portion) Read ISL Sections 4.3.4.
3. (Day 3 portion) Read ISL Sections 4.3.5.

In this repository/directory, you should see five items:

• README-img - a folder containing images that I am embedding within this README.md file and other files. You do not need to do anything with this.
• .gitignore - a file that is used to specify what Git can ignore when pushing to GitHub. You do not need to do anything with this.
• README.md - the document you are currently reading.
• day01-simple-logistic - a folder that contains items for you to complete during the first 75-minute class meeting.
• day02-multiple-logistic - a folder that contains items for you to complete during the second 75-minute class meeting.
• day03-multinomial-logistic - a folder that contains items for you to complete during the third 75-minute class meeting.

We will explore most of these items over this week. Before doing that, you will first make your own copy of this repository.

Check in

Do you want an interactive way to check your understanding outside of class? Remember that these are a good way to check your foundation understanding and were created by Benjamin Baumer (associate professor at Smith College), in collaboration with the OpenIntro team and others. The following tutorials will provide you with an applied approach to our topics (reorganized to better correspond with our readings):

Days 1 & 2:

• ISL 3.2 & 3.3 - Logistic regression

Day 3:

• There is no interactive tutorial that corresponds to multinomial logistic regression.

Task 1: Forking & cloning

Forking

Read these directions first, then work through them. In this GitHub repo (i.e., my repo):

1. Click on the Fork icon near the upper-right-hand corner. You will be taken to a Create a new fork screen.
2. Verify that your GitHub username is selected under Owner and that the Repository name is activity06-logistic-regression with a green check mark (this verifies that you do not already have a GitHub repository with this name).
3. You may provide a Description if you would like. This is a way to provide some additional, more descriptive, meta information related to the things you did. I like to provide a brief description of what happened.
4. Verify that Copy the main branch only is selected.
5. Click on the green Create fork button at the bottom of this page.

You should be taken a copy of this repo that is in your GitHub account. That is, your page title should be username/activity06-logistic-regression, where username is replaced with your GitHub username. Directly below this, you will see the following message:

forked from gvsu-sta631/activity06-logistic-regression

You will complete the rest of this activity in your forked copy of the activity06-logistic-regression repo.

Cloning

Read these directions first, then work through them. Note that you will be switching between RStudio and your GitHub repo (that you previously forked).

1. In RStudio, click on the icon (the icon below the Edit drop-down menu).
2. Click on Version Control on the New Project Wizard pop-up.
3. Click on Git and you should be on a “Clone Git Repository” page.
4. Back to your activity06-logistic-regression GitHub repo, click on the green Code button near the top of the page.
5. Verify that HTTPS is underlined in orange/red on the drop-down menu, then copy the URL provided.
6. Back in RStudio, paste the URL in the “Repository URL” text field.
7. The “Project directory name” text field should have automatically populated with activity06-logistic-regression. If yours did not (this is usually an issue on Macs),
   • Click back into the “Repository URL” text field.
   • Highlight any bit of this text (it does not seem to matter what or how much).
   • Press Ctrl/Cmd and the “Project directory name” should now have automatically populated with activity06-logistic-regression.
8. Browse to STA 631/Activities (assuming you followed my opinionated file structure from earlier in the semester), then click Choose.
9. Click on Create Project.

Your screen should refresh and the Files pane should say that you are currently in your activity06-logistic-regression folder that currently has the same files and folders as your GitHub repo. If you are asked for your GitHub credentials, provide your GitHub username and your PAT (not your password).

Check in

Take a moment to reflect on what is possibly your second time doing this forking process.

• How is this process going for you? Is it “muscle memory” yet?
• What is easier since last week?
• What do you still need help remembering?

We will use a dataset with information from résumés and job callbacks.

Task 2: Odds and logistic regression

Read these directions first, then work through them.

1. In your activity06-logistic-regression repo folder/directory, locate and click into the day01-simple-logistic subfolder.
2. In the day01-simple-logistic subfolder, you will be greeted by a new README.md file. Do your best to complete the tasks/directions provide in this subfolder by 11:59 pm (EST) on Tue, Feb 21.
3. Ask questions in class as you are working. If you need to finish this up outside of our class meetings, remember that you can use our Teams workspace (linked on Blackboard), and post questions/issues in the Muddy channel. If someone else already posted what you though was muddy, add any clarification to their post and give them a “+ 1” 👍. Remember that this space is for conversations as well as posting questions. Read through your peers’ muddy posts and do your best to provide help.

The rest of this README document contains tasks/directions for the second class meeting of this week.

Task 3: Updating your forked GitHub repo

You will need to start reading these directions back at my gvsu-sta631/activity06-logistic-regression GitHub repo and have your forked username/activity06-logistic-regression GitHub repo handy. I recommend that you have my repo opened on one half of your screen and your repo opened on the other half. Read these directions first, then work through them.

1. At the top of your username/activity06-logistic-regression repo (above the repo contents section), verify that you see a message that looks something like:

This branch is X commits behind gvsu-sta631:main.

2. Click on the hyperlinked “X commits behind” portion of that message to be taken to a Comparing changes page.
3. Verify that your drop-down menu options specify:
   • base repository: username/activity06-logistic-regression
   • base: main
   • head repository: gvsu-sta631/activity06-logistic-regression
   • compare: main
4. Also verify that you have a message directly below this that says:

✓ Able to merge. These branches can be automatically merged.

Flag me if you see something different.

5. Click on the green Create pull request button under this previous message. Note you can look at the changes that I made, if you so desire, by scrolling down. However, this is not necessary.
6. On the next page, provide a short descriptive message in the “Title” box (e.g., “Adding Day 2 materials”). You can also provide a more detailed message in the “Leave a comment” box if you choose.
7. Click on the green Create pull request button.
8. On the next screen which is titled the same thing as what you provided in the “Title” box on the previous screen, you will be presented with a bunch of information. If you scroll down a little, you should see a green check mark with a message that specifies:

This branch has no conflicts with the base branch

And you can click on the green Merge pull request.

9. You will be provided with with an opportunity to provide another meaningful message (or accept the default message). Finally, click on the green Confirm merge button. You can now work directly from your username/activity06-logistic-regression repo.

In summary, what you just did is pulled my changes into your repository. Git and GitHub refer to this as a “pull request” because you are asking to pull items into your repo.

Task 4: Multiple logistic regression

You will continue to work in your activity06.Rmd file that you started during Day 1 of this activity. Read these directions first, then work through them.

1. In your activity06-logistic-regression repo folder/directory, locate and click into the day02-multiple-logistic subfolder.
2. In the day02-multiple-logistic subfolder, you will be greeted by a new README.md file. Do your best to complete the tasks/directions provide in this subfolder by 11:59 pm (EST) on Thu, Feb 23.
3. Ask questions in class as you are working. If you need to finish this up outside of our class meetings, remember that you can use our Teams workspace (linked on Blackboard), and post questions/issues in the Muddy channel. If someone else already posted what you though was muddy, add any clarification to their post and give them a “+ 1” 👍. Remember that this space is for conversations as well as posting questions. Read through your peers’ muddy posts and do your best to provide help.

Task 5: One mo’ gain

You will need to start reading these directions back at my gvsu-sta631/activity06-logistic-regression GitHub repo and have your forked username/activity06-logistic-regression GitHub repo handy. I recommend that you have my repo opened on one half of your screen and your repo opened on the other half. Read these directions first, then work through them.

1. At the top of your username/activity06-logistic-regression repo (above the repo contents section), verify that you see a message that looks something like:

This branch is X commits behind gvsu-sta631:main.

2. Click on the hyperlinked “X commits behind” portion of that message to be taken to a Comparing changes page.
3. Verify that your drop-down menu options specify:
   • base repository: username/activity06-logistic-regression
   • base: main
   • head repository: gvsu-sta631/activity06-logistic-regression
   • compare: main
4. Also verify that you have a message directly below this that says:

✓ Able to merge. These branches can be automatically merged.

Flag me if you see something different.

5. Click on the green Create pull request button under this previous message. Note you can look at the changes that I made, if you so desire, by scrolling down. However, this is not necessary.
6. On the next page, provide a short descriptive message in the “Title” box (e.g., “Adding Day 2 materials”). You can also provide a more detailed message in the “Leave a comment” box if you choose.
7. Click on the green Create pull request button.
8. On the next screen which is titled the same thing as what you provided in the “Title” box on the previous screen, you will be presented with a bunch of information. If you scroll down a little, you should see a green check mark with a message that specifies:

This branch has no conflicts with the base branch

And you can click on the green Merge pull request.

9. You will be provided with with an opportunity to provide another meaningful message (or accept the default message). Finally, click on the green Confirm merge button. You can now work directly from your username/activity06-logistic-regression repo.

In summary, what you just did is pulled my changes into your repository. Git and GitHub refer to this as a “pull request” because you are asking to pull items into your repo.

Task 4: Mulinomial logistic regression

You will work in activity06-multinomial.Rmd file for this portion of the activity as we are working with a different dataset. Read these directions first, then work through them.

1. In your activity06-logistic-regression repo folder/directory, locate and click into the day03-multinomial-logistic subfolder.
2. In the day03-multinomial-logistic subfolder, you will be greeted by a new README.md file. Do your best to complete the tasks/directions provide in this subfolder by 11:59 pm (EST) on Tue, Feb 28.
3. Ask questions in class as you are working. If you need to finish this up outside of our class meetings, remember that you can use our Teams workspace (linked on Blackboard), and post questions/issues in the Muddy channel. If someone else already posted what you though was muddy, add any clarification to their post and give them a “+ 1” 👍. Remember that this space is for conversations as well as posting questions. Read through your peers’ muddy posts and do your best to provide help.

Attribution

This document is based on materials from OpenIntro and Dr. Maria Tackett (Duke University).

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.