Photo by Marleena Garris on Unsplash
The first step in the process of turning information into knowledge process is to summarize and describe the raw information - the data. In this assignment we explore data on college majors and earnings, specifically the data begin the FiveThirtyEight story “The Economic Guide To Picking A College Major”.
These data originally come from the American Community Survey (ACS) 2010-2012 Public Use Microdata Series. While this is outside the scope of this assignment, if you are curious about how raw data from the ACS were cleaned and prepared, see the code FiveThirtyEight authors used.
We should also note that there are many considerations that go into picking a major. Earnings potential and employment prospects are two of them, and they are important, but they don’t tell the whole story. Keep this in mind as you analyze the data.
Click on your assignment link, clone it in Posit and open the R Markdown document. Knit the document to make sure it compiles without errors.
Before we introduce the data, let’s warm up with some simple exercises.
We’ll use the tidyverse package for much of the data wrangling and visualisation, the scales package for better formatting of labels on visualisations, and the data lives in the fivethirtyeight package. These packages are already installed for you. You can load them by running the following in your Console:
The data can be found in the fivethirtyeight package, and it’s called college_recent_grads
.
Since the dataset is distributed with the package, we don’t need to load it separately; it becomes available to us when we load the package.
You can find out more about the dataset by inspecting its documentation, which you can access by running ?college_recent_grads
in the Console or using the Help menu in RStudio to search for college_recent_grads
.
You can also find this information here.
You can also take a quick peek at your data frame and view its dimensions with the glimpse
function.
The college_recent_grads
data frame is a trove of information.
Let’s think about some questions we might want to answer with these data:
In the next section we aim to answer these questions.
In order to answer this question all we need to do is sort the data.
We use the arrange
function to do this, and sort it by the unemployment_rate
variable.
By default arrange
sorts in ascending order, which is what we want here – we’re interested in the major with the lowest unemployment rate.
This gives us what we wanted, but not in an ideal form.
First, the name of the major barely fits on the page.
Second, some of the variables are not that useful (e.g. major_code
, major_category
) and some we might want front and center are not easily viewed (e.g. unemployment_rate
).
We can use the select
function to choose which variables to display, and in which order:
Note how easily we expanded our code with adding another step to our
pipeline, with the pipe operator: |>
.
Ok, this is looking better, but do we really need to display all those decimal places in the unemployment variable? Not really!
We can use the percent()
function to clean up the display a bit.
To answer such a question we need to arrange the data in descending order. For example, if earlier we were interested in the major with the highest unemployment rate, we would use the following:
The desc
function specifies that we want
unemployment_rate
in descending order.
top_n(3)
at the end of the pipeline.A percentile is a measure used in statistics indicating the value below which a given percentage of observations in a group of observations fall. For example, the 20th percentile is the value below which 20% of the observations may be found. (Source: Wikipedia
There are three types of incomes reported in this data frame: p25th
, median
, and p75th
.
These correspond to the 25th, 50th, and 75th percentiles of the income distribution of sampled individuals for a given major.
The question we want to answer “How do the distributions of median income compare across major categories?”.
We need to do a few things to answer this question: First, we need to group the data by major_category
.
Then, we need a way to summarize the distributions of median income within these groups.
This decision will depend on the shapes of these distributions.
So first, we need to visualize the data.
We use the ggplot()
function to do this.
The first argument is the data frame, and the next argument gives the mapping of the variables of the data to the aes
thetic elements of the plot.
Let’s start simple and take a look at the distribution of all median incomes, without considering the major categories.
Along with the plot, we get a message:
`stat_bin()` using `bins = 30`. Pick better value with `binwidth`.
This is telling us that we might want to reconsider the binwidth we chose for our histogram – or more accurately, the binwidth we didn’t specify. It’s good practice to always think in the context of the data and try out a few binwidths before settling on a binwidth. You might ask yourself: “What would be a meaningful difference in median incomes?” $1 is obviously too little, $10000 might be too high.
geom_histogram
function. So to specify a binwidth of $1000, you would use geom_histogram(binwidth = 1000)
.We can also calculate summary statistics for this distribution using the summarise
function:
college_recent_grads |>
summarise(min = min(median), max = max(median),
mean = mean(median), med = median(median),
sd = sd(median),
q1 = quantile(median, probs = 0.25),
q3 = quantile(median, probs = 0.75))
✏️ Based on the shape of the histogram you created in the previous exercise, determine which of these summary statistics is useful for describing the distribution. Write up your description (remember shape, center, spread, any unusual observations) and include the summary statistic output as well.
Plot the distribution of median
income using a histogram, faceted by major_category
.
Use the binwidth
you chose in the earlier exercise.
Now that we’ve seen the shapes of the distributions of median incomes for each major category, we should have a better idea for which summary statistic to use to quantify the typical median income.
count
, which first groups the data and then counts the number of observations in each category (see below). Add to the pipeline appropriately to arrange the results so that the major with the lowest observations is on top.🧶 ✅ ⬆️ Knit, commit, and push your changes to GitHub with an appropriate commit message. Make sure to commit and push all changed files so that your Git pane is cleared up afterwards.
One of the sections of the FiveThirtyEight story is “All STEM fields aren’t the same”. Let’s see if this is true.
First, let’s create a new vector called stem_categories
that lists the major categories that are considered STEM fields.
stem_categories <- c("Biology & Life Science",
"Computers & Mathematics",
"Engineering",
"Physical Sciences")
Then, we can use this to create a new variable in our data frame indicating whether a major is STEM or not.
college_recent_grads <- college_recent_grads |>
mutate(major_type = ifelse(major_category %in% stem_categories, "stem", "not stem"))
Let’s unpack this: with mutate
we create a new variable called major_type
, which is defined as "stem"
if the major_category
is in the vector called stem_categories
we created earlier, and as "not stem"
otherwise.
%in%
is a logical operator.
Other logical operators that are commonly used are
Operator | Operation |
---|---|
x < y |
less than |
x > y |
greater than |
x <= y |
less than or equal to |
x >= y |
greater than or equal to |
x != y |
not equal to |
x == y |
equal to |
x %in% y |
contains |
x | y |
or |
x & y |
and |
!x |
not |
We can use the logical operators to also filter
our data for STEM majors whose median earnings is less than median for all majors’ median earnings, which we found to be $36,000 earlier.
🧶 ✅ ⬆️ Knit, commit, and push your changes to GitHub with an appropriate commit message. Make sure to commit and push all changed files so that your Git pane is cleared up afterwards.
🧶 ✅ ⬆️ Knit, commit, and push your changes to GitHub with an appropriate commit message. Make sure to commit and push all changed files so that your Git pane is cleared up afterwards and review the md document on GitHub to make sure you’re happy with the final state of your work.