This activity is intended to be completed in one week - outside of class preparation work and two 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:
- (Day 1 portion) Read ISL Sections 3.2.0 (the chapter introduction) & 3.2.1.
- (Day 2 portion) Read ISL Sections 3.2.2.
In this repository/directory, you should see five items:
README-img
- a folder containing images that I am embedding within thisREADME.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-fitting
- a folder that contains items for you to complete during the first 75-minute class meeting.day02-assessing
- a folder that contains items for you to complete during the second 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.
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 - Multiple regression
Note that this tutorial covers materials for this week and next week.
Read these directions first, then work through them. In this GitHub repo (i.e., my repo):
- Click on the Fork icon near the upper-right-hand corner. You will be taken to a Create a new fork screen.
- Verify that your GitHub username is selected under Owner and
that the Repository name is
activity03-mlr
with a green check mark (this verifies that you do not already have a GitHub repository with this name). - 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.
- Verify that Copy the
main
branch only is selected. - 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/activity03-mlr
, where
username
is replaced with your GitHub username. Directly below this,
you will see the following message:
forked from gvsu-sta631/activity03-mlr
You will complete the rest of this activity in your forked copy of
the activity03-mlr
repo.
Read these directions first, then work through them. Note that you will be switching between RStudio and your GitHub repo (that you previously forked).
- In RStudio, click on the icon (the icon below the Edit drop-down menu).
- Click on Version Control on the New Project Wizard pop-up.
- Click on Git and you should be on a “Clone Git Repository” page.
- Back to your
activity03-mlr
GitHub repo, click on the green Code button near the top of the page. - Verify that HTTPS is underlined in orange/red on the drop-down menu, then copy the URL provided.
- Back in RStudio, paste the URL in the “Repository URL” text field.
- The “Project directory name” text field should have automatically
populated with
activity03-mlr
. 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
activity03-mlr
.
- In the “Create project as subdirectory of” field, click on Browse…. Create a New Folder called “STA 631”, then within this folder, create a New Folder called “Activities”, then click Choose. If you already have this, you can simply browse to “STA 631/Activities”, then click Choose. Note that I am forcing you to use my opinionated file system management style.
- Click on Create Project.
Your screen should refresh and the Files pane should say that you
are currently in your activity03-mlr
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).
Take a moment to reflect on what is possibly your second time doing this forking process.
- What was easier this time?
- What is still muddy?
- What do you need to try/do/explore to help with this muddiness?
We will continue exploring the Human Freedom Index dataset. Recall that this is a report that attempts to summarize the idea of “freedom” through a bunch of different variables for many countries around the globe. It serves as a rough objective measure for the relationships between the different types of freedom - whether it is political, religious, economical or personal freedom - and other social and economic circumstances. The Human Freedom Index is an annually co-published report by the Cato Institute, the Fraser Institute, and the Liberales Institut at the Friedrich Naumann Foundation for Freedom.
Read these directions first, then work through them.
- In your
activity03-mlr
repo folder/directory, locate and click into theday01-fitting
subfolder. - In the
day01-fitting
subfolder, you will be greeted by a newREADME.md
file. Do your best to complete the tasks/directions provide in this subfolder by 11:59 pm (EST) on Tue, Jan 31. - 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.
You will need to start reading these directions back at my
gvsu-sta631/activity03-mlr
GitHub repo and have your forked
username/activity03-mlr
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.
- At the top of your
username/activity03-mlr
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.
- Click on the hyperlinked “X commits behind” portion of that message to be taken to a Comparing changes page.
- Verify that your drop-down menu options specify:
- base repository: username/activity03-mlr
- base: main
- head repository: gvsu-sta631/activity03-mlr
- compare: main
- 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.
- 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.
- 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.
- Click on the green Create pull request button.
- 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.
- 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/activity03-mlr
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.
In your username/activity03-mlr
repo, go into the day02-assessing
subfolder and follow the tasks listed in the README
. You will continue
to work in your activity03-day01.Rmd
file that you started during Day
1 of this activity.
This document is based on labs from OpenIntro.
This
work is licensed under a
Creative
Commons Attribution-ShareAlike 4.0 International License.