Well it's that time of the year again in the United States. The 162 game marathon MLB season is officially underway. In honor of the opening of another season of America's Pasttime I was working on a post that uses data from the MLB. What I realized was that as I was writing the post, I found that I kept struggling with inconsistent data across different seasons. It was really annoying and finally it hit me: This is what I should be writing about! Why not just dedicate an entire post to normalizing data!
So that's what I've done. In this post we'll be digging into some MLB payroll data. In particular I'm going to show you how you can use normalization techniques to compare seemlingly incomparable data! Sounds like magic? Well it's actually really simple, but I think these little Python scripts will really help you out 🙂
The data I'm using is a collection of MLB standings and attendance data from the past 70 years. You can read more about how I collected it in this post
I'm sure a lot of you saw the news last week about feather, the brainchild from Wes McKinney and Hadley Wickham. As both a Python and an R user, I think it's a really compelling idea. It'll be interesting to see how the project progresses over time. Can't wait to see what else they cook up!
In any event, I thought I'd give it a try for this post. I did my data collection using R (comes from a previous post on the MLB), but I wanted to do the analysis in Rodeo. After running my data collection script in R, I sent the output to a
.feather file using the
feather R package.
library(feather) write_feather(standings, "standings.feather") write_feather(attendance, "attendance.feather")
I then read that data back into Python.
import feather import pandas as pd standings = feather.read_dataframe('./standings.feather') attendance = feather.read_dataframe('./attendance.feather')
|3||26695.0||1441545.0||30.5||99||3828834.0||Fregosi and Mauch||13||4||1||30.0||99||2:40||CAL||1981|
Wow! Really easy. Great work Wes and Hadley! 🙂
Now that we've got our data, it's time to do some munging.
I'm looking to compare payrolls over time. There are a couple of tricky things about this.
First off (and probably most obviously) is that the value of the dollar has changed over the past 70 years. So there will be obvious differences between a payroll from 1970 and a payroll from 2010.
payrolls = attendance[['year', 'est_payroll']].groupby('year').mean() / 1000 payrolls[(payrolls.index==1970) | (payrolls.index==2010)] Out: est_payroll (1000s) year 1970 434.565455 2010 91916.006567
Yikes! When adjusted for inflation, that $434k becomes $2.5M. Compare that to the actual average payroll in 2010, $92M, and not quite everything seems to be adding up.
That's because the value of baseball players has ALSO been increasing over time. As teams have been able to make more money through TV revenue and other means, ballplayers salaries have gone up...way up! As a result normalizing our data isn't as simple as just adjusting for inflation. Darn!
Brief Aside: While on the subject, a super interesting factoid is the "Bobby Bonilla Mets contract". Despite having been retired for 15 years, the Mets still pay him over $1M per year, thanks to an interesting negotiation and Mets owner Fred Wilpon's involvement in Bernie Madoff's Ponzi scheme. Full story here.
Bobby Bonilla still makes over $1M / year despite not having played baseball since 2001
Not to worry! We can still get an apples to apples comparison of payrolls over time. In order to make that comparison, we need our payrolls to be on the same numerical scale.
We're going to use a really simple approach for this. For each year we're going to calculate the mean salary for the league as whole, and then create a derived field which compares a given team's payroll to the mean payroll for the entire league.
Lucky for us, Python and
pandas make this super easy to do. Here goes...
mean_payrolls = attendance[['year', 'est_payroll']].groupby('year').mean().reset_index() mean_payrolls.columns = ['year', 'league_mean_payroll'] attendance = pd.merge(attendance, mean_payrolls, on='year') attendance['norm_payroll'] = attendance.est_payroll / attendance.league_mean_payroll
Let's take a look at what our
norm_payroll field looks like. Ahh there we go!
But what if we wanted to do something a little different? for instance, what if you wanted the
norm_payroll to bet a standardized value between 0 and 1 (instead of a uncapped scale as in the previous example)?
This is actually something that's really common. Many machine learning algorithms perform much better using scaled data (support vector machine comes to mind). Again, lucky for us doing this in Python is super easy.
To do this we'll use the same approach as before (as in, normalizing by year) but instead of using the mean, we're going to use the max and min values for each year.
min_payrolls = attendance[['year', 'est_payroll']].groupby('year').min().reset_index() min_payrolls.columns = ['year', 'league_min_payroll'] max_payrolls = attendance[['year', 'est_payroll']].groupby('year').max().reset_index() max_payrolls.columns = ['year', 'league_max_payroll'] attendance = pd.merge(attendance, min_payrolls, on='year') attendance = pd.merge(attendance, max_payrolls, on='year') attendance['norm_payroll_0_1'] = (attendance.est_payroll - attendance.league_min_payroll) / (attendance.league_max_payroll - attendance.league_min_payroll)
As you can see things actually look a bit different than they did using the first method. Keep this in mind: Your normalization strategy can impact your results! Please don't forget this!
There are lots more ways to normalize your data (really whatever strategy you can think of!). These are just 2 ways that work a lot of the time and can be nice starting points. By no means is this the end all be all of data normalization (there are many books on the subject), but hopefully this gives you a quick intro to this very important topic.
Till next time--enjoy the season, the normalization techniques and the new feather file format!
Still around, huh? Looking for other resources on data normalization? Look no further:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.