# Reshaping & Tidy Data¶

Structuring datasets to facilitate analysis (Wickham 2014)

So, you've sat down to analyze a new dataset. What do you do first?

In episode 11 of Not So Standard Deviations, Hilary and Roger discussed their approaches. I'm with Hilary on this one, you should make sure your data is tidy. Before you do any plots, filtering, transformations, summary statistics, regressions... Once you get to a tidy dataset, it's relatively easy to do all of those.

Today we'll talk about what makes a dataset tidy and how to get there.

Hadley Whickham (who I think is tied with Wes for number of shoutouts in this series...) kindly summarized a tidyness as a dataset where

1. Each variable forms a column
2. Each observation forms a row
3. Each type of observational unit forms a table

And most of the time it's just the first two that matter. As quoted at the top, this really is about facilitating analysis: going as quickly as possible from question to answser.

In [1]:
import numpy as np
import pandas as pd
import seaborn as sns
import matplotlib.pyplot as plt

pd.options.display.max_rows = 10
sns.set(style='ticks', context='talk')
%matplotlib inline


# NBA Data¶

Note: I'm reusing this example from an earlier post.

Based on this StackOverflow question. We'll grab some NBA game data from basketball-reference.com using pandas' read_html function, which returns a list of DataFrames.

In [7]:
tables = pd.read_html("http://www.basketball-reference.com/leagues/NBA_2016_games.html")
games = tables[0]


Out[7]:
Date Start (ET) Unnamed: 2 Visitor/Neutral PTS Home/Neutral PTS.1 Unnamed: 7 Notes
0 October NaN NaN NaN NaN NaN NaN NaN NaN
1 Tue, Oct 27, 2015 8:00 pm Box Score Detroit Pistons 106.0 Atlanta Hawks 94.0 NaN NaN
2 Tue, Oct 27, 2015 8:00 pm Box Score Cleveland Cavaliers 95.0 Chicago Bulls 97.0 NaN NaN
3 Tue, Oct 27, 2015 10:30 pm Box Score New Orleans Pelicans 95.0 Golden State Warriors 111.0 NaN NaN
4 Wed, Oct 28, 2015 7:30 pm Box Score Philadelphia 76ers 95.0 Boston Celtics 112.0 NaN NaN

Side note: pandas' read_html is pretty good. On simple websites it almost always works. It provides a couple parameters for controlling what gets selected from the webpage if the defaults fail. I'll always use it first, before moving on to BeautifulSoup or lxml if the page is more complicated.

As you can see, we have a bit of general munging to do before tidying. Each month slips in an extra row of mostly NaNs, the column names aren't too useful, and we have some dtypes to fix up.

In [8]:
column_names = {'Date': 'date', 'Start (ET)': 'start',
'Unamed: 2': 'box', 'Visitor/Neutral': 'away_team',
'PTS': 'away_points', 'Home/Neutral': 'home_team',
'PTS.1': 'home_points', 'Unamed: 7': 'n_ot'}

games = (games.rename(columns=column_names)
.dropna(thresh=4)
[['date', 'away_team', 'away_points', 'home_team', 'home_points']]
.assign(date=lambda x: pd.to_datetime(x['date'], format='%a, %b %d, %Y'))
.set_index('date', append=True)
.rename_axis(["game_id", "date"])
.sort_index())

Out[8]:
away_team away_points home_team home_points
game_id date
1 2015-10-27 Detroit Pistons 106.0 Atlanta Hawks 94.0
2 2015-10-27 Cleveland Cavaliers 95.0 Chicago Bulls 97.0
3 2015-10-27 New Orleans Pelicans 95.0 Golden State Warriors 111.0
4 2015-10-28 Philadelphia 76ers 95.0 Boston Celtics 112.0
5 2015-10-28 Chicago Bulls 115.0 Brooklyn Nets 100.0

A quick aside on that last block.

• dropna has a threshold argument. If at least thresh items are missing, the row is dropped. We used it to remove the "Month headers" that slipped into the table
• assign can take a callable. This lets us refer to the column in the previous step of the chain. Otherwise we would have to assign temp_df = games.dropna()... And then do the pd.to_datetime on that.
• set_index has an append keyword. We keep the original index around since it will be our unique identifier per game
• We use .rename_axis to set the index names (this behavior is new in pandas 0.18; before .rename_axis only took a mapping for changine labels)

The Question:

How many days of rest did each team get between each game?

Whether or not your dataset is tidy depends on your question. Given our question, what is an observation?

In this case, an observation is a (team, game) pair. Unfortunately we don't have that yet. We have two observations per row, one for home and one for away. We'll fix that with pd.melt.

melt works by taking observations that are spread across columns (away_team, home_team), and melting them down into one column with multiple rows. However, we don't want to lose the metadata (like game_id and date) that is shared between the observations. By including those columns as id_vars, the values will be repeated as many times as needed to stay with their observations.

In [9]:
tidy = pd.melt(games.reset_index(),
id_vars=['game_id', 'date'], value_vars=['away_team', 'home_team'],
value_name='team')

Out[9]:
game_id date variable team
0 1 2015-10-27 away_team Detroit Pistons
1 2 2015-10-27 away_team Cleveland Cavaliers
2 3 2015-10-27 away_team New Orleans Pelicans
3 4 2015-10-28 away_team Philadelphia 76ers
4 5 2015-10-28 away_team Chicago Bulls

The DataFrame tidy meets our rules for tidyness: each variable is in a column, and each observation (team, date pair) is on its own row. Now the translation from question ("How many days of rest") to operation ("date of today's game - date of previous game - 1") is direct:

In [12]:
# For each team... get number of days between games
tidy.groupby('team')['date'].diff().dt.days - 1

Out[12]:
0       NaN
1       NaN
2       NaN
3       NaN
4       NaN
...
2455    7.0
2456    1.0
2457    1.0
2458    3.0
2459    2.0
dtype: float64

That's the essence of tidy data, the reason why it's worth considering what shape your data should be in. It's about setting yourself up for success, so that the answers naturally flow from the (just kidding, it's still difficult. But hopefully less so).

Let's assign that back into our DataFrame

In [13]:
tidy['rest'] = tidy.sort_values('date').groupby('team').date.diff().dt.days - 1

Out[13]:
game_id date variable team rest
4 5 2015-10-28 away_team Chicago Bulls 0.0
8 9 2015-10-28 away_team Cleveland Cavaliers 0.0
14 15 2015-10-28 away_team New Orleans Pelicans 0.0
17 18 2015-10-29 away_team Memphis Grizzlies 0.0
18 19 2015-10-29 away_team Dallas Mavericks 0.0

To show the inverse of melt, let's take rest values we just calculated and place them back in the original DataFrame with a pivot_table.

In [18]:
by_game = (pd.pivot_table(tidy, values='rest',
index=['game_id', 'date'],
columns='variable')
.rename(columns={'away_team': 'away_rest',
'home_team': 'home_rest'}))
df = pd.concat([games, by_game], axis=1)

Out[18]:
away_team away_points home_team home_points away_rest home_rest
game_id date
18 2015-10-29 Memphis Grizzlies 112.0 Indiana Pacers 103.0 0.0 0.0
19 2015-10-29 Dallas Mavericks 88.0 Los Angeles Clippers 104.0 0.0 0.0
20 2015-10-29 Atlanta Hawks 112.0 New York Knicks 101.0 1.0 0.0
21 2015-10-30 Charlotte Hornets 94.0 Atlanta Hawks 97.0 1.0 0.0
22 2015-10-30 Toronto Raptors 113.0 Boston Celtics 103.0 1.0 1.0

One somewhat subtle point: an "observation" depends on the question being asked.

So really, we have two tidy datasets, tidy for answering team-level things, and df for game-level things.

One potentially interesting question is "what was each team's average days of rest, at home and on the road". With a tidy dataset (the DataFrame tidy, since it's team-level), Seaborn makes this easy:

In [24]:
g = sns.FacetGrid(tidy, col='team', col_wrap=6, hue='team')
g.map(sns.barplot, 'variable', 'rest');


An example of a game-level statistic is the distribution of rest differences in games:

In [27]:
df['home_win'] = df['home_points'] > df['away_points']

Out[27]:
away_team away_points home_team home_points away_rest home_rest home_win rest_spread
game_id date
18 2015-10-29 Memphis Grizzlies 112.0 Indiana Pacers 103.0 0.0 0.0 False 0.0
19 2015-10-29 Dallas Mavericks 88.0 Los Angeles Clippers 104.0 0.0 0.0 True 0.0
20 2015-10-29 Atlanta Hawks 112.0 New York Knicks 101.0 1.0 0.0 False -1.0
21 2015-10-30 Charlotte Hornets 94.0 Atlanta Hawks 97.0 1.0 0.0 True -1.0
22 2015-10-30 Toronto Raptors 113.0 Boston Celtics 103.0 1.0 1.0 False 0.0
In [28]:
delta = (by_game.home_rest - by_game.away_rest).dropna().astype(int)
ax = (delta.value_counts()
.reindex(np.arange(delta.min(), delta.max() + 1), fill_value=0)
.sort_index()
.plot(kind='bar', color='k', width=.9, rot=0, figsize=(12, 6))
)
sns.despine()
ax.set(xlabel='Difference in Rest (Home - Away)', ylabel='Games')
plt.savefig('../content/images/tidy_diff_in_rest.svg', transparent=True)


Or the win percent by rest difference

In [29]:
fig, ax = plt.subplots(figsize=(12, 6))
color='#4c72b0', ax=ax)
sns.despine()


# Stack / Unstack¶

Pandas has two useful methods for quickly converting from wide to long format (stack) and long to wide (unstack).

In [67]:
rest = (tidy.groupby(['date', 'variable'])
.rest.mean()
.dropna())

Out[67]:
date        variable
2015-10-28  away_team    0.000000
home_team    0.000000
2015-10-29  away_team    0.333333
home_team    0.000000
2015-10-30  away_team    1.083333
Name: rest, dtype: float64

rest is in a "long" form since we have a single column of data, with multiple "columns" of metadata (in the MultiIndex). We use .unstack to move from long to wide.

In [68]:
rest.unstack().head()

Out[68]:
variable away_team home_team
date
2015-10-28 0.000000 0.000000
2015-10-29 0.333333 0.000000
2015-10-30 1.083333 0.916667
2015-10-31 0.166667 0.833333
2015-11-01 1.142857 1.000000

unstack moves a level of a MultiIndex (innermost by default) up to the columns. stack is the inverse.

In [31]:
rest.unstack().stack()

Out[31]:
date        variable
2015-10-28  away_team    0.000000
home_team    0.000000
2015-10-29  away_team    0.333333
home_team    0.000000
2015-10-30  away_team    1.083333
...
2016-04-11  home_team    0.666667
2016-04-12  away_team    1.000000
home_team    1.400000
2016-04-13  away_team    0.500000
home_team    1.214286
dtype: float64

With .unstack you can move between those APIs that expect there data in long-format and those APIs that work with wide-format data. For example, DataFrame.plot(), works with wide-form data, one line per column.

In [35]:
ax=(rest.unstack()
.query('away_team < 7')
.rolling(7)
.mean().plot(figsize=(12, 6), linewidth=3, legend=False))
ax.annotate("Home", (rest.index[-1][0], 1.02), color='g', size=14)
ax.annotate("Away", (rest.index[-1][0], 0.82), color='b', size=14)
sns.despine()


The most convinent form will depend on exactly what you're doing. When interacting with databases you'll often deal with long form data. Pandas' DataFrame.plot often expects wide-form data, while seaborn often expect long-form data (more on that in a future post). Regressions will expect wide-form data. Either way, it's good to be comfortable with stack and unstack (and MultiIndexes) to quickly move between the two.

# Mini Project: Home Court Advantage?¶

We've gone to all that work tidying our dataset, let's put it to use. What's the effect (in terms of probability to win) of being the home team?

### Step 1: Create an outcome variable¶

We need to create an indicator for whether the home team won. Add it as a column called home_win in games.

In [37]:
df['home_win'] = df.home_points > df.away_points


### Step 2: Find the win percent for each team¶

We'll use a similar melt operation as early, only now with the home_win variable we just created.

In [38]:
wins = (
pd.melt(df.reset_index(),
id_vars=['game_id', 'date', 'home_win'],
value_name='team', var_name='is_home',
value_vars=['home_team', 'away_team'])
.assign(win=lambda x: x.home_win == (x.is_home == 'home_team'))
.groupby(['team', 'is_home'])
.win
.agg({'n_wins': 'sum', 'n_games': 'count', 'win_pct': 'mean'})
)

Out[38]:
win_pct n_wins n_games
team is_home
Atlanta Hawks away_team 0.512195 21.0 41
home_team 0.658537 27.0 41
Boston Celtics away_team 0.487805 20.0 41
home_team 0.682927 28.0 41
Brooklyn Nets away_team 0.170732 7.0 41

Pause for visualiztion, because why not

In [71]:
g = sns.FacetGrid(wins.reset_index(), hue='team', size=10, aspect=.5, palette=['k'])
g.map(sns.pointplot, 'is_home', 'win_pct').set(ylim=(0, 1));


(It'd be great if there was a library built on top of matplotlib that auto-labeled each point decently well. Apparently this is a difficult problem to do in general).

In [72]:
g = sns.FacetGrid(wins.reset_index(), col='team', hue='team', col_wrap=5)
g.map(sns.pointplot, 'is_home', 'win_pct');


Those two graphs show that most teams have a higher win-percent at home than away. So we can continue to investigate. Let's aggregate over home / away to get an overall win percent per team.

In [73]:
win_percent = (
# Use sum(games) / sum(games) since I don't
# know if teams play the same number of games at
# home as away
wins.groupby(level='team', as_index=True)
.apply(lambda x: x.n_wins.sum() / x.n_games.sum())
)

Out[73]:
team
Atlanta Hawks        0.585366
Boston Celtics       0.585366
Brooklyn Nets        0.256098
Charlotte Hornets    0.585366
Chicago Bulls        0.512195
dtype: float64
In [74]:
win_percent.sort_values().plot.barh(figsize=(6, 12), width=.85, color='k')
plt.tight_layout()
sns.despine()
plt.xlabel("Win Percent");


Is there a relationship between overall team strength and their home-court advantage?

In [76]:
(wins.win_pct
.unstack()
.assign(**{'Home Win % - Away %': lambda x: x.home_team - x.away_team,
'Overall %': lambda x: (x.home_team + x.away_team) / 2})
.pipe((sns.regplot, 'data'), x='Overall %', y='Home Win % - Away %')
)
sns.despine()


And get that back into df. You could you pd.merge, but I prefer .map when joining a Series.

In [77]:
df = df.assign(away_strength=df['away_team'].map(win_percent),
home_strength=df['home_team'].map(win_percent),
point_diff=df['home_points'] - df['away_points'],
rest_diff=df['home_rest'] - df['away_rest'])

Out[77]:
away_team away_points home_team home_points away_rest home_rest home_win rest_spread away_strength home_strength point_diff rest_diff
game_id date
1 2015-10-27 Detroit Pistons 106.0 Atlanta Hawks 94.0 NaN NaN 0 NaN 0.536585 0.585366 -12.0 NaN
2 2015-10-27 Cleveland Cavaliers 95.0 Chicago Bulls 97.0 NaN NaN 1 NaN 0.695122 0.512195 2.0 NaN
3 2015-10-27 New Orleans Pelicans 95.0 Golden State Warriors 111.0 NaN NaN 1 NaN 0.365854 0.890244 16.0 NaN
4 2015-10-28 Philadelphia 76ers 95.0 Boston Celtics 112.0 NaN NaN 1 NaN 0.121951 0.585366 17.0 NaN
5 2015-10-28 Chicago Bulls 115.0 Brooklyn Nets 100.0 0.0 NaN 0 NaN 0.512195 0.256098 -15.0 NaN
In [82]:
import statsmodels.formula.api as sm

df['home_win'] = df.home_win.astype(int)  # for statsmodels

In [83]:
mod = sm.logit('home_win ~ home_strength + away_strength + home_rest + away_rest', df)
res = mod.fit()
res.summary()

Optimization terminated successfully.
Current function value: 0.552792
Iterations 6

Out[83]:
Dep. Variable: No. Observations: home_win 1213 Logit 1208 MLE 4 Thu, 21 Apr 2016 0.1832 07:01:39 -670.54 True -820.91 7.479e-64
coef std err z P>|z| [95.0% Conf. Int.] 0.0707 0.314 0.225 0.822 -0.546 0.687 5.4204 0.465 11.647 0.000 4.508 6.333 -4.7445 0.452 -10.506 0.000 -5.630 -3.859 0.0894 0.079 1.137 0.255 -0.065 0.243 -0.0422 0.067 -0.629 0.529 -0.174 0.089

The strength variables both have large coefficeints (really we should be using some independent measure of team strength here, win_percent is showing up on the left and right side of the equation). The rest variables don't seem to matter as much.

It's easy to explore variations in formula.

In [87]:
(sm.Logit.from_formula('home_win ~ strength_diff + rest_spread',
df.assign(strength_diff=df.home_strength - df.away_strength))
.fit().summary())

Optimization terminated successfully.
Current function value: 0.553499
Iterations 6

Out[87]:
Dep. Variable: No. Observations: home_win 1213 Logit 1210 MLE 2 Thu, 21 Apr 2016 0.1821 07:02:58 -671.39 True -820.91 1.165e-65
coef std err z P>|z| [95.0% Conf. Int.] 0.4610 0.068 6.756 0.000 0.327 0.595 5.0671 0.349 14.521 0.000 4.383 5.751 0.0566 0.062 0.912 0.362 -0.065 0.178
In [88]:
mod = sm.Logit.from_formula('home_win ~ home_rest + away_rest', df)
res = mod.fit()
res.summary()

Optimization terminated successfully.
Current function value: 0.676549
Iterations 4

Out[88]:
Dep. Variable: No. Observations: home_win 1213 Logit 1210 MLE 2 Thu, 21 Apr 2016 0.0003107 07:03:09 -820.65 True -820.91 0.7749
coef std err z P>|z| [95.0% Conf. Int.] 0.3667 0.094 3.889 0.000 0.182 0.552 0.0338 0.069 0.486 0.627 -0.102 0.170 -0.0420 0.061 -0.693 0.488 -0.161 0.077