Showing posts with label defensive efficiency. Show all posts
Showing posts with label defensive efficiency. Show all posts

Wednesday, February 1, 2012

Is Georgetown overrated?

Yes.

The Hoyas came into this week with their AP ranking dropping from 9th to 14th (or 18th on KenPom, if you prefer a rational metric), and fans across the Hoya-nation spectrum are fretting that their plans of a Final Four trip might not happen.

I think it might be time to lower your expectations a bit.


As our regular reader knows, we don't update this blog nearly as often as we used to - hell, it took me two weeks to get all the stats pages updated.  But there is one set of stats that we do track religiously around here, and that's the "Big East Snapshot" page.  Not so much because it's a better set of stats than the others, but because I actually bothered to make those stats more automated than the rest.

You probably don't check that page often, if at all, but you should.  It provides you with two main pieces of information: a set of summary tables (more on those in a minute) and a handy chart for each Big East team.  Here's the Georgetown chart (click to enlarge):


There's a previous post where I explain how to read these charts, but here's a brief summary:
  • The top of the chart shows how well the Hoyas played in any game, accounting for the quality of the opponent and the venue.  A black dot means a win, a grey dot means a loss. We rate the team's performance by the final score, and with some tricky math figure what rank you'd give the team based only on that single game.
  • The middle and bottom of the chart are how well the team played on offense and defense, respectively, again accounting for opponent and venue.  These are the offensive and defensive efficiencies (points per 100 possessions) that Ken Pomeroy made famous.
  • Home games are in all caps; since Chaminade is not a Division-I team, that game doesn't get rated.
Now if you put your thumb over that dot that represents the win at St. John's, you should notice a disturbing trend - since the second win against Memphis, the Hoyas have begun an inexorable slide throughout January.  Note: the chart is dynamic and will update as the season progresses, so the above discussion may or may not be valid in a few weeks.

Why?

Well, if I knew exactly what was wrong I probably wouldn't be posting from my mother's basement, but I think the chart shows two clear issues:
  • The defense stopped playing lights-out after the Memphis game (excluding the win vs. Providence), although there seems to be a trend towards getting back to the early season prowess.
  • The offense is going into the tank (and you probably didn't need a chart to know that).

Putting this in some context after the jump

Wednesday, February 16, 2011

Introducing a new stats page

I've been both sick and out in the field for the past week, so things have been more quiet than normal around here.  Most stats pages are updated - the rest will have to wait until the weekend.


Meanwhile, I've been sitting on a new stats page that has been gestating for the past couple of weeks - it's certainly not in a finished state (I've only been able to incorporate a couple of suggestions), but I figured I'd just get it out there with minimal explanation, and come back and clean it up when I get the chance.

The new page is currently called "Big East Snapshot" and can be found on the tabs at the top of the page.  It is a re-packaging of Ken Pomeroy's adjusted offensive and defensive efficiency statistics, so if margin-of-victory statistics are not of much interest to you, you should probably stop reading right here.


The purpose of the page is two-fold:
  • Give my reader an idea of how well each Big East team has played within conference so far this season, both over the entire conference season and over the last five games (the "snapshot").
  • Provide something of a new-and-improved version of the performance charts that I generate for Georgetown after each game, but now for all Big East teams.

This is a follow up on a previous post here, where I criticized John Gasaway for using unadjusted efficiency stats for his Tuesday Truths columns.  It occurred to me that it wouldn't be hard to generate the adjusted stats myself, and from that flowed the conference snapshot.

The idea is simply to correct each game's margin-of-victory statistics for both the quality of the opponent and the game venue. For instance, in Georgetown's last game, the Hoyas beat Marquette 69-60 in a 68 possession game.  This translates into offensive and defensive efficiencies of 102 and 89, respectively, for the Hoyas (or 89 and 102 for Marquette).

But if I account for who the Hoyas were playing and that it was a home game, we get adjusted efficiencies of 111 and 86 for Georgetown and 109 and 90 for Marquette.

That is to say, if Georgetown would have played equally as well, but on a neutral court and against the average Div-I opponent (right now St. Peter's), we'd expect the Hoyas to end with efficiencies of 111 and 86 for the game; if it were a 68-possession game, that'd be a final score of 75-58.  For Marquette, if they played equally as well as last Sunday, they would also beat St. Peter's, but with a final score of 74-61 in a 68-possession game.

The biggest difference between this analysis and the "Performance" stats is that here, I'm now giving equal credit to both teams for each game's result.  For instance, in the shellacking that Seton Hall put on Syracuse, I'm giving equal credit to the Pirates for playing out of their minds and the Orange for mailing in the game.


That's it in a nutshell, and I'm working this through for all games played by all Big East teams. The main caveat here is that Ken also employs a weighting factor for more recent games, which I'm currently not doing.  I think this is a very small effect (well under 1%), so the stats I'll be posting are very close to what Ken would have.

There are also couple of technical reasons why I'm unveiling this page, which you won't likely be much interesting in.  Suffice it to say that the underlying statistics for the new page are generated in a more automated fashion, so it takes only a few keystrokes to update the tables, and a few more to update the charts shown after the tables.



That's about all the time I've got right now, so I'll just go ahead and hit the publish button for now.  I'll try to come back and add another post discussing why I think the new page is kind of interesting.

Friday, January 14, 2011

Friday thoughts

Not really sure where I'm going with today's post, but just sitting here riffing on some stats.
--------------------------------------------------------------

One of the great conceits of being a sports fan is that we all think we know more than ______, and that if the coaching staff only listened to us, our team would be that much better.  Some of us even start blogs to make sure we can get the word out.

But, after a few years of blogging, it starts to become clear that maybe we don't know as much as we'd like to think.

Here's an example:  I can make a simple model using the four factors to estimate Georgetown's offensive efficiency for each game played so far this year, and from this I can give an estimate of how important each factor is to Georgetown's offense.
Factor      Weight
eFG%         0.64
OReb%        0.18
TO%          0.13
FTM/FGA      0.01
Total        0.96
That's to say, about 64% of the variability game to game in Georgetown's offensive efficiency can be explained by how well they shoot (eFG%). Once we account for that, about 18% of the remaining variability is due to how well they offensive rebound, etc.

I can even make a nifty graph to show how well the model works:


 I can also repeat the exercise for the defense (no nifty graph this time), for a slightly surprising result [this table has been revised]:
Factor      Weight
eFG%         0.36
TO%          0.46
DReb%        0.11
FTA/FGA      0.02
Total        0.95

But here's the thing - what can we do with this information?

I can demonstrate that Georgetown's offense is most dependent upon how well the team shoots from the floor, but I can't tell you how the Hoyas can improve their shooting accuracy from this exercise.

More importantly, just because their defense this year is most dependent upon how well they turn over the opponent doesn't mean the team should be running a full-court press all the time.  The law of unintended consequences reminds us that the result could just as easily wind up that teams would end up shooting more layups (and therefore improve their shooting accuracy) as a result, and Georgetown's defense wouldn't improve at all.

But it sure seems tempting.

Tuesday, March 2, 2010

Examining the slump -- offense or defense?

One of the first things I do when dissecting why a team is winning or losing is simply to check whether the offense or defense is more to blame. People inherently focus on scoring -- there will be a game where the team loses 97-95 and their fans will scream about a turnover or missed shot, all the while ignoring the sieve that was the defense.

So what about the Hoyas? The team is slumping badly with its most recent loss to a good WVU squad on the road (which, as Brian points out, was mostly caused by offensive turnovers and a distinct lack of defensive turnovers).

One simple way to look at a team is to look at offensive and defensive efficiencies. As of the WVU game, Georgetown has an adjusted offensive efficiency of 114.5, good for 20th in the country.

What does this mean? That Georgetown could be expected to score 114.5 points in 100 possessions against an average D-I team. Georgetown's defensive efficiency is 92.4 (43rd), which means it could expect to give up 92.4 points versus that same average team.

In short, the offense has been better than the defense right now.

But that hasn't always been the case.

I went game by game and took Georgetown's offensive and defensive efficiency in each game, adjusted for home/away games and the opponent's current efficiency for the season, to see how well Georgetown's offense and defense performed over the course of the season.

To put this in the context of a typical Georgetown game, I converted those efficiency numbers into points, based on a 67-possession game.

In short, the numbers below are the number of points per game that Georgetown played above or below an average NCAA in each game. The average NCAA team is someone like Loyola Marymount, Lipscomb or Indiana this year; so being average here is not a good thing, and decidedly worse that being an average team in the Big East.

How is this different than what Brian did here?

Well, Brian was looking at how Georgetown performed relative to its own expectation;. I'm trying to evaluate Georgetown's performance against a standard baseline (i.e. the average NCAA team) to see, overall, how the offense and defense have performed, given the competition.  It's really just an offset between the two analyses.
.                 (Above Avg. Team)  (Below Avg Team)
Games               Points Scored     Points Allowed
First 7 Games             7.8               9.2
Second 7 Games            6.3               8.2
Third 7 Games            12.1               4.8
Fourth 7 Games            8.7               4.2

In the first seven games, the Hoyas had some creampuffs, the Temple offensive debacle and a rather balanced performance versus Butler.

Starting with the Butler game and running through much of the second 7 games (including Washington), the defense carried Georgetown for the most part. In the Old Dominion game, the offense was actually below NCAA-average.

Starting with Seton Hall, the team started to get hot on offense, but also a bit schizophrenic. In four of the seven games in this quartile, the Hoyas posted offenses 18+ points above NCAA Average in a 67-possession game. Yes, NCAA-average isn't very good, but 18 points differential due to the offense in a regular Georgetown game is pretty darn good.

The defense started to decline, though, and in the South Florida game, neither the offense nor defense was any good.

By the last set of games, the offense had come back to earth but the defense hadn't revived.

Looking at the losses:
Game              Offense        Defense
ODU                 -1              5
South Florida       -1             -4
at Rutgers           8             -5
Notre Dame           3            -11

at Marquette         9              7
at Villanova         5             11
at Syracuse          0              7
Syracuse             6              6
West Virginia        6              5

I divided them up into perceived "bad" losses and "acceptable" losses. It's worth noting that versus Marquette and Nova, Georgetown played better than in some of their wins. The Syracuse games were pretty bad; at home the Hoyas played better than versus Temple but that's about it.  Overall, the defense plays as well or better than the offense in losses against marquee opponents.

In the three "bad" in-conference losses, the defense has been more to blame. But aside from the Rutgers game, the offense wasn't exactly pulling its weight, either. Still, 11 points worse than an average D-I (read: Indiana) defense versus Notre Dame? Ughh.  Overall, the defense plays terribly in losses against "easier" opponents.

Here's the whole season, along with the season to date running average after the seventh game -- you can see how the defense has slowly declined:
Game                   Offense  Defense  Total  O Avg  D Avg
Tulane                   12         5      17   
Temple                  - 9        19      10   
Savannah St.              6        10      16   
Lafayette                23         1      24   
Mount St. Mary's         10         6      16   
American                  2        13      16     7.5    8.9 
Butler                    9        11      20     7.8    9.2 
Washington                1        19      20     6.9   10.4 
Old Dominion            - 1         5       4     6.1    9.7 
Harvard                   6         9      15     6.1    9.7 
St. John's                9         3      12     6.3    9.1 
DePaul                   15        10      25     7.0    9.1 
Marquette                 9         7      15     7.2    8.9 
Connecticut               6         6      11     7.1    8.7 
Seton Hall               18         0      18     7.8    8.1 
Villanova                 5        11      17     7.6    8.3 
Pittsburgh               21         5      27     8.4    8.2 
Rutgers                  20         3      23     9.0    7.9 
Syracuse                - 0         7       7     8.5    7.9 
Duke                     22        10      32     9.2    8.0 
South Florida           - 1       - 4     - 4     8.7    7.4 
Villanova                16         7      23     9.1    7.4 
Providence                7        13      20     9.0    7.6 
Rutgers                   8       - 5       3     9.0    7.1 
Syracuse                  6         6      12     8.8    7.0 
Louisville               15        14      29     9.1    7.3 
Notre Dame                3       -11     - 8     8.8    6.6 
West Virginia             6         5      11     8.7    6.6

Notice that the offense got better as the season has progressed before stabilizing in February, while the defense has been steadily trending downward since the Washington game.

Wednesday, December 30, 2009

Looking back in anger, part 2

Last night I posted some tables showing the adjusted offensive and defensive efficiencies for the Hoyas over the past six seasons, broken into two groups:  early season (Nov. - Dec.) and late season (Jan. - Apr.).

Tonight I'll go ahead and run through the four factors tables that underlie each of the efficiencies we discussed.

Again here, I've adjusted each of the stats to account for the level of competition, but this is a much less certain trick then when I adjust efficiencies.  Without getting too technical, I have KenPom's adjusted efficiencies available for all of Georgetown's opponents over the past six seasons, but I have no adjusted stats for the four factors.  Think of the RPI, which uses record (25%), opponents' record (50%) and opponents' opponents' record (25%) - since I can't account for opponents' opponents for these stats, they are missing that component equivalent to about 25% with the RPI.

Also, I suspect that this will quickly turn into a stats dump, as it's getting late tonight. I'll try to come back and flush this out a bit more tomorrow.  At inspection before posting, this article looks like a mess, but I need to get to bed!

To start, let's take a look at the offense:
Offense - Early Season
Season    O. Eff.     eFG %     TO Rate    OReb %     FT Rate
2003-04    103.9      50.4       19.6       39.1  *    42.4
2004-05    106.9      53.8  *    20.8       36.7       32.4
2005-06    109.9      54.8  *    18.0       32.6       32.9
2006-07    113.8 *    55.6  *    21.7       39.8  *    34.5
2007-08    119.1 *    59.2  !    18.8       36.0       35.4
2008-09    117.4 *    57.2  *    20.1       36.8       54.7  !
What I've done is tag each column if the team was performing significantly better or worse than an average team.  Roughly put:
! = Top 10    * = Top 25    x = Bottom 50    X = Bottom 25

Before I delve into this table, I'll go ahead and post the late season stats for offense:
Offense - Late Season
Season    O. Eff.     eFG %     TO Rate    OReb %     FT Rate
2003-04     96.2      44.7  x    21.0       30.2  x    32.8
2004-05    113.2 *    55.0  *    22.2       33.9       32.8
2005-06    117.7 *    54.4  *    18.9       36.4       35.9
2006-07    125.9 !    58.2  !    20.6       42.1  !    38.6
2007-08    114.3 *    55.6  *    22.3  x    33.7       35.8
2008-09    108.3      52.5       23.4  x    34.6       38.2

At this point, I think there are at few truisms that become apparent:
  • For a team to operate at a very good (Top 25) or elite (Top 10) efficiency on offense, it needs to shoot extremely well.  Doing another thing very well is useful, but not necessary.
  • Being very good or elite at one of these skills in the early season is likely to translate to conference play, but not a guarantee.
  • Generally, expect performance to decline a bit in conference play.  This seems most likely with turnovers.
  • Getting offensive rebounds is nice, but not committing turnovers is nicer.

Now let's run the defense:

Defense - Early Season
Season    D. Eff.     eFG %     TO Rate    OReb %     FT Rate
2003-04    91.6       49.2       28.1  !    39.6  X    28.4
2004-05    97.3       47.1       23.0       37.2  X    39.5  x
2005-06    92.9       47.1       20.7       28.3  *    29.9
2006-07    89.1  *    44.6  *    21.1       29.1       36.3
2007-08    87.2  *    42.1  *    18.4       30.8       25.1  *
2008-09    82.6  *    39.8  !    25.1  *    36.7  x    27.5

Defense - Late Season
Season    D. Eff.     eFG %     TO Rate    OReb %     FT Rate
2003-04    92.8       50.5       24.8  *    34.4       43.1  x
2004-05    94.4       47.6       21.1       33.2       39.6  x
2005-06    92.6       47.7       20.0       31.1       27.5
2006-07    88.7  *    43.2  *    19.5       34.6       28.5
2007-08    85.3  *    41.8  *    20.7       31.1       41.4  x
2008-09    95.0       48.9       21.5       34.4       36.9

Here, the conclusions are similar:
  • Preventing teams from making shots is the best way to run an efficient defense.
  • Usually, early season field goal defense will translate well into conference play.
  • Bad rebounding early season can be corrected by conference play.
  • You can still have a great defense despite giving up fouls

So what happened last season?  A few things.
  1. The team shot less accurately from the field in conference than early season.  This wasn't dramatic, and I'd guess tied to the 3FG shooting (I'm too lazy to look right now).  I couldn't let that stand, so I've appended another table at the end with shooting percentages for all seasons. Turns out it was as much 2FG shooting as 3FG shooting.  Shows what I know.
  2. Offenisve turnovers went up quite a bit
  3. Items #1 and #2 also happened in 2007-8, but were a bit more severe last year.
  4. An elite ability to get to the FT line evaporated in conference play.  This may have been a bit of crutch propping up the offense early on.
  5. The defense was defending field goals at <40% eFG early season, but this fell to Esherick-level in conference.  This was the single biggest change in the factors for offense or defense last year, and was fundamental to the collapse in conference. 
  6. Better rebounding couldn't make up for the drop in turnovers generated by the defense.

Finally, how does the team's early season stats look, heading into the game vs. St. John's tomorrow night?

Season    O. Eff.     eFG %     TO Rate    OReb %     FT Rate
2009-10    114.4 *    57.7  !    23.2  x    39.3  *    37.7

.         D. Eff.     eFG %     TO Rate    OReb %     FT Rate
           81.9  *    42.5  *    20.9       27.8  *    25.7  *

The offense is currently rated as very good, but I expect that to drop down a bit in conference.  As likely as not, the shooting accuracy will drop down a bit against taller Big East clubs, and that lousy turnover rate is most likely going to increase even more.

Rebounding on both ends is very good so far, and while a small decline would be expected in each case, I don't think either will become the worry that we saw last year.

The overall adjusted def. efficiency is very good so far this year, and there isn't a single underlying stat that raises a red flag of unsustainability.  I suspect that this season, much like 2007-8, the Hoyas will go as far as their defense will take them.


Edited to add these table:
Offense
.           Early Season                Late Season
Season    2FG%   3FG%   FT %          2FG%   3FG%   FT %
2003-04   49.0   40.3   70.2          40.7   31.9   72.3
2004-05   51.6   37.9   69.7          51.8   35.8   70.9
2005-06   56.9   37.5   69.3          52.1   34.6   71.3
2006-07   59.7   36.9   70.8          56.8   37.1   71.2
2007-08   60.1   41.0   60.2          54.2   37.1   68.1
2008-09   58.1   34.6   75.3          53.1   32.4   68.2

2009-10   54.0   36.1   71.1

Defense
.           Early Season                Late Season
Season    2FG%   3FG%   FT %          2FG%   3FG%   FT %
2003-04   43.9   32.9   62.6          50.9   31.9   69.3
2004-05   43.2   33.9   66.7          45.8   33.2   73.8
2005-06   41.4   37.7   64.1          48.0   33.8   70.8
2006-07   42.8   30.6   71.0          43.4   30.2   71.0
2007-08   38.3   29.9   65.8          41.6   29.4   68.4
2008-09   36.8   28.8   71.6          49.5   34.0   70.5

2009-10   41.3   30.3   72.5

Tuesday, December 29, 2009

Looking back in anger

As the Big East regular season gets under way, it comes time to wonder what we've learned about the Hoyas so far this year.

About this time last season I also wondered what November and December had demonstrated - heading into a home game against Pittsburgh, Georgetown was ranked #1 overall by Ken Pomeroy, with a net adjusted efficiency (adj. off. eff. - adj. def. eff) of + 42. That is, we expected that the Hoyas would outscore the median Div-I team (e.g. Holy Cross or Hofstra in 2009) by 42 points in 100 possessions.

I was so excited that I made one of those fancy-pants graphs to demonstrate visually just how good Georgetown was (click any figure to enlarge):

2008-09 Big East Aerial (31-Dec-08)
You'll need to read this post to understand everything in this figure, but simply:  upper-right = good; lower-left = bad.

The Hoyas went 6-14 the rest of the way.  Obviously, that figure - and the Hoyas early season performance - didn't tell us what was to come, only what had happened so far.

Now I could simply knock out this year's version and let it rest, or I could stare at a bunch of numbers on a spreadsheet and try to understand why the early season performance by the Hoyas was such a poor predictor of the rest of the season.

Let's do both.

First, here's this year's aerial, through games played Monday:


2009-10 Big East Aerial (28-Dec-09)


As conference play gets underway, Syracuse and West Virginia appear to be the class of the Big East, both with fairly balanced teams (offense vs. defense efficiencies).

Georgetown, surprisingly, is a solid third by KenPom's ratings, although the team is highly dependent upon its defense (#1 in the conference) as the offense is merely average.

Following is an enormous cluster of teams, headed by Marquette and Villanova and followed by St. John's, Pitt, UConn, Louisville, Seton Hall, Cincinnati and South Florida.  That's nine teams all grouped together.

Notre Dame - which almost fell off the chart with its extreme of the league's best offense and worst defense - and Providence are slightly behind the peloton, and Rutgers and DePaul hold the final two spots.

A few points to make:
  • Note that the scaling on this year's aerial is slightly different than last year's.  The offensive scale doesn't go quite so high and the defensive scale doesn't go quite so low.  For instance, Notre Dame had better adj. off. and def. eff. stats last year, while this plot may lead you to think that their offense is actually better this year.
  • The elite teams this year aren't quite as elite as those from last season headed into January.  Since four Big East teams made it to the Elite 8 last year, a drop-off this time isn't unexpected.
  • No team last season made it to the NCAA tournament from behind the isopleth that crosses the solid diagonal at OE=107, DE=93.  This year, S. Florida sits just behind that line.  Three teams that were ahead of that line last year (Georgetown, Notre Dame and Cinci) failed to make the tourney, although they were bubblicious until the end.  If that's any sort of bellwether, it would mean 12 Big East teams are capable of making the NCAAs this year (although obviously some will not).
  • A few teams may look out of place:
    • Georgetown's pedestrian offense may seem unusual, but did you know that the Hoyas have finished higher than 8th in off. efficiency in the Big East only two times in JTIII's first five seasons (2006 & 2007)?
    • Louisville's offense is better than their defense?  The Cardinals have finished 4th, 2nd, 1st and 1st in def. efficiency in conference their first four seasons.  If the offense can tread water, expect Louisville to improve as its defense does.
    • Pitt was one of the most lopsided teams last year - they had a great offense and mediocre defense.  It's the opposite so far this year.
    • To my eye, the most dramatic year-over-year improvement is S. Florida, but I'm not sure how they'll do without Gus Gilchrist for the foreseeable future.  St. John's is also far ahead of last year.
----------------------------------------------------------------------------------

Okay, that was fun, but what about the real issue - how well can we predict the rest of the season from how well a team plays in November and December?

Here's Georgetown's won-loss record for the past 6 seasons in the early part (all games in Nov. and Dec.) and late part (Jan. - Apr. games) of the schedule:
.                Early                  Late
Season       W   L     Net         W   L     Net 
2003-04      9   0   + 28.8        4  15   - 11.8
2004-05      8   3   + 13.7       11  10   +  1.1
2005-06      8   2   + 21.2       15   8   +  7.7
2006-07     10   3   + 23.1       20   4   + 15.7
2007-08     10   1   + 31.9       18   5   + 12.1
2008-09     10   1   + 29.6        6  14   -  3.6
That third column for each segment ("Net") refers to the difference between off. and def. efficiency during those games.  It turns out that the best two W/L records, and the 2nd and 3rd best net efficiencies from early season preceded two epic collapses - yes, this dataset goes back to the final Esherick season, although this is just a coincidence since this is as far back as KenPom's database goes back in time.

Now hopefully, if you're my regular reader or you've bothered to make it this far down the article, you'll want to dig a bit deeper into those numbers above.  For instance, what was the quality of competition like during each early season?  If we adjust the underlying off. and def. efficiencies for that competition, what would the net eff. numbers look like?

Let me tackle those one at a time.  First, I'll re-post those net. eff. numbers with the opponents' average KenPom rating:
.             Early                    Late
Season      Net   Rating             Net  Rating
2003-04   + 28.8   258             - 11.8   63
2004-05   + 13.7   175             +  1.1   55
2005-06   + 21.2   190             +  7.7   49
2006-07   + 23.1   150             + 15.7   48
2007-08   + 31.9   160             + 12.1   59
2008-09   + 29.6   119             -  3.6   61
Clearly, JTIII does not subscribe to Esherick's (and by proxy, his father's) scheduling philosophy.  The 03-04 team was simply getting fat on a bunch of low-major teams early season, and never had its mettle tested until conference play got rolling.  The 08-09 bunch, however, played the toughest early-season schedule so far - remember that the UConn game last year was played before New Year's, so it is included.  The huge drop in net efficiency last year came after the team looked to be able to handle just about anyone early on.

Let's now take a look at each of the individual efficiencies, now adjusted for competition during the segment.  This is analogous to looking at KenPom's Adj. Efficiencies, rather than raw efficiencies.  As I mentioned at the top, when we discuss adj. efficiencies, what we mean is how would we expect the team to perform against an average Div-I team.

Here we go, looking at offense first:
.                Off. Eff.
Season     Early  Late   Diff.
2003-04    103.9   96.2  -7.7
2004-05    106.9  113.2   6.3
2005-06    109.9  117.7   7.7
2006-07    113.8  125.9  12.1
2007-08    119.1  114.3  -4.8
2008-09    117.4  108.3  -9.1
The last Esherick team was the worst offensive team in the group, both early and late season, once you adjust the stats for the level of competition.

One of the great mythical concepts of the Georgetown/Princeton offense is that it is massively complex and takes considerable practice time and game experience to master.  The first three seasons under JTIII certainly give evidence to that, as the team improved from early season to late season.  This wasn't the case in 07-08, where the team was stocked with upperclassmen and operated at a high level even with the step back in conference.  But last year's team showed the biggest overall drop intra-season, and the roster had only 1 junior and 1 senior - surely an improvement should have come.

It's also worth noting that, in spite of the collapse last year, the team was still scoring more than 12 points per 100 possessions more than the 03-04 club.

.                Def. Eff.
Season     Early  Late   Diff.
2003-04     91.6   92.8   -1.2
2004-05     97.3   94.4    2.9
2005-06     92.9   92.6    0.3
2006-07     89.1   88.7    0.3
2007-08     87.2   85.3    1.9
2008-09     82.6   95.0  -12.4
Excluding last season, this table just makes a lot more sense to me.  I can understand offenses going to slumps, for example due to a prolonged stretch of poor outside shooting, but I'd expect that a team's defensive ability will be fairly well established in the first two months of the season, once the level of competition is accounted for.

An important trend, and one that I don't think most fans or analysts are picking up on, is that each Hoya team in the JTIII era has been better defensively than the previous year's team, and had improved from early-season to late-season.  Heading into Jan. 2009, Coach Thompson was beginning to look like some sort of defensive genius.

Then the wheels came off.

If we use the Esherick team as an archetype for one that had lost its confidence, or perhaps better a coach that had lost his team, we still see only a small drop in the quality of defensive play.  Last season, there were no significant injuries yet the defense on the court in conference play not only didn't resemble the early season team, it broke with a general trend over a five-year period.

.                Net Eff.
Season     Early  Late   Diff.
2003-04     12.3    3.4   -8.9
2004-05      9.6   18.8    9.2
2005-06     17.1   25.1    8.0
2006-07     24.8   37.2   12.4
2007-08     31.9   29.0   -2.8
2008-09     34.8   13.3  -21.4
Finally (for tonight), I'll summarize the previous tables with the net adj. efficiencies for the past six seasons.  I think its worth noting that, as much as we like to decry the late season swoon last year, it's worth recognizing that the early season performance was about as good as the Hoyas have played since JTIII arrived, just a touch below the 06-07 team during its run to the Final Four.  The shock wasn't so much how poorly they were playing by the end of the season, but rather how far they had fallen in such a short period of time.

While the Esherick team's collapse wasn't nearly as large, that team simply wasn't good enough to start with to be able to collapse very far.

Tomorrow, I'll dig a bit deeper into the underlying stats, and take a look at what we've learned so far this year.

Tuesday, February 10, 2009

It's the (2nd half) defense, stupid

Following up on a point made by SFHoya99 over at Hoyatalk . . .


While I'm sure there is much gnashing of teeth in Hoya Nation, there is also quite a bit of casting about for who or what is to blame for the collapse of the team over the last 6 weeks.

One thing that I've noticed is that Georgetown seems to be losing the 2nd half in most games during this stretch. Taking the 12 games played from at UConn (29-Dec) through vs. Cinci (7-Feb), Georgetown has been outscored by their opponent by 41 points in the second half (or 3.4 points/game). In fact, the Hoyas have outscored their opponent by more than 5 points in only one 2nd half during this stretch - versus Providence.

So I thought I would generate a tempo-free box score for these last 12 games, broken out by half:
.                      Offense                            Defense
. 1st Half 2nd Half Total 1st Half 2nd Half Total
Pace 31.5 33.3 64.8

Eff. 100.7 104.9 102.9 98.6 115.0 107.1
Eff. Margin 2.1 -10.1 -4.2

eFG% 51.4 50.0 50.7 49.2 54.0 51.7
TO% 23.3 19.4 21.3 23.0 18.9 20.9
OR% 36.9 32.1 34.5 33.2 42.9 38.1
FTA/FGA 20.9 54.5 37.3 22.2 43.1 32.9
FTM/FGA 14.2 38.1 25.8 16.4 30.4 23.5

Assist Rate 60.5 58.6 59.6 55.7 54.3 54.9
Block Rate 13.5 10.4 11.9 9.0 7.8 8.4
Steal Rate 10.9 9.8 10.3 12.5 10.8 11.6

2FG% 49.8 51.9 50.8 47.9 54.5 51.4
3FG% 36.4 30.6 33.7 34.5 35.2 34.8
FT% 67.6 69.8 69.2 73.6 70.5 71.6

What can we learn? Well, it becomes clear that the problem for the Hoyas after halftime is the defense, not the offense. In fact, the offense actually becomes slightly more efficient in the 2nd half, largely through increased trips to the FT line and fewer turnovers.

However, the defense is much, much worse in the second half. The problems span the entire gamut - eFG% is worse (due to worse 2FG shooting defense), fewer turnovers are created, more offensive rebounds are allowed and more FTs are allowed (although that last stat may be due to giving fouls at the end of the game).

Interestingly, teams aren't shooting significantly better from outside or at the FT line in the 2nd half, so there is scant evidence to chalk this up to lucky shooting - opponents are simply getting more opportunities to score, and are making more interior shots. The Hoyas' block and steal rate also drop between halves, again indicating that it is G'town that is performing differently in the second half, rather than just their opponents.


What is especially frustrating as a Hoyas fan is that the team is better than their opponent, on average, in the first half. In fact, Georgetown has gone to the locker room down double-digits only twice during this stretch (-11 vs. Notre Dame & Duke); for whatever reason, Georgetown outscored each in the second half.

Monday, February 2, 2009

The Defense

In this post I took a quick look at the team's slide and saw that while the offense struggled in three of the five games, the defense struggled in all five, and has slipped significantly from last year.

The team's ability to force difficult shots has been a key issue:

Time Period            Opp. eFG%   
Last Year, Pre-BE 41.7%
Last Year, BE 42.9%
This Year, Pre-BE 38.1%
This Year, BE 52.0%


Well, there's a drop-off. Last year, the team all but held the opposing shooting percentage even to the softer pre-season schedule.

This, the opposing shooting percentage has skyrocketed. It's probably not the lack of defensive rebounding -- the 4% decrease we've seen going into Big East play isn't generating more than a couple extra shots a game. That can't account for a 14 point swing.

Where's the drop-off coming from?


Time Period            Opp. 3PT%    Opp. 2PT%   
Last Year 29.9% 40.5%
This Year, Full Year 31.1% 44.0%
Last Five Games 29.0% 56.0%


There's not a strong, consistent trend, game by game, despite the rather obvious conclusion of the table above. Marquette shot well from three and took 38 free throws. Duke also shot well from three. These games are probably what I am remembering when I see slow rotation after slow rotation.

Actually, that's not true. It's been true every game in the streak, but our opponents have only truly taken advantage in the Duke and Marquette games. Jeremy Hazell and Alex Ruoff were cold.

But the strongest theme has been the Hoyas giving up an abundance of two point baskets. There's two things going on here.

One, the Hoyas are giving up 45% shooting on two point jumpers. This isn't overly high, but usually, when these shots are contested well, the opposing shooting percentage is lower.

More importantly, the Hoyas are giving up baskets on 64% of the opponents' Dunk, Tip-in and Layups attempts. They are allowing 19 of those shots a game. The Hoyas simply are not contesting easier shots well.

Adding fuel to this idea is the fact that the Hoyas' foul rate this year has actually gone down on defense. The Hoyas' opponents took free throws totalling 42% of the field goal attempts they allowed last year. This year, that number is only 35%. That likely points to a lack of aggressiveness on defense.

The team's Achilles Heel so far, defensive rebounding, hasn't actually gotten worse during this span. Opponents have grabbed 37% of offensive rebounds compared to 36% in pre-Big East play and 40% in Big East play overall. The rebounding is bad, but aside from the West Virginia game, it hasn't been the reason the defense has declined from earlier play.

Earlier in the season, the Hoyas were making up for this rebounding weakness with forcing turnovers. The Hoyas aren't anymore.

Time Period            Opp. TO%   
Last Year, Pre-BE 17.6%
Last Year, BE 19.3%
This Year, Pre-BE 24.0%
This Year, BE 19.1%
Last Five Games 18.8%


While last year's team stepped up their defense against stronger opponents, this year's team has been unable to force turnovers against better ballhandlers.

---------------------------

What does it all mean? I admit, this analysis isn't overly illuminating in terms of what is actually happening.

The Hoyas are simply not contesting enough shots, especially down low. They've given up 36 fast break points in the last five games, which is a fairly high amount considering that the numbers are always understated. They gave up twenty eight tip-in, layup or dunks attempts to a small Seton Hall club. Opponents are getting their shots at the rim, and there isn't a seven-footer there to alter the shot.

And right now, there's really no one there to alter the shot. Rotations both on the perimeter and in the paint are looking a step slow right now, and it's leading to easy baskets. Is it because the team is looking to keep its big men out of foul trouble? Or is it simply poor defense? Either way, there's too many easy baskets.

Sunday, November 16, 2008

Another stats gimmick, and J'ville preview

Excuse this interruption of SFHoya99's season preview, but I thought I'd chime back in to introduce another stats feature that I've been working on behind the scenes.

If you're looking for the Jacksonville preview, you'll need to scroll down quite a bit.

My regular reader may have noticed by now that I've been loathe to assign credit or blame on specific players during a single game, but rather tend to present team stats. I do this in part because I think that it is difficult to evaluate individual play (especially defense) with a simple basketball box score.

There are tools available to glean some additional information when you look at a single game, notably the individual net score box that Dean Oliver describes in Basketball on Paper. Henry Sugar over at Cracked Sidewalks is a particular proponent of this, and has been providing Marquette fans with his version (which he calls "Individual Player Ratings") for most of last season. Here's an example from last year's game between MU and Villanova (hope he doesn't mind me linking):


Note that I've previously discussed this game when I introduced my version of the HD Box Score.

I won't explain Mr. Sugar's work here, but I will point to an excellent post he wrote last season covering the basics of each stat column listed. The bottom line for most fans is in columns 5 and 7 - points produced and net points added. This gives us an idea, based on tempo-free stats, of just how many points each player contributed towards the game result (in this case, a 10 point win for Marquette).

There are some limitations to this work.

Without going into too much detail here, I can assure you that the defensive rating assigned to each player for this game is just loosely tied to reality. Defensive stats are not available for most basketball games (NBA too) at the detail-level needed, so it is somewhere between difficult and impossible to assign blame for each player's defensive effort.

But more generally, the calculations used for the stats in the table above are underpinned by a large number of estimates, which should improve as we aggregate data over the course of a season, but which can be quite a bit off during an individual game. Here are just some examples of missing information needed to make the calculations for the stats above:
  1. How many possessions did a player have on offense? Defense?
  2. How many offensive/defensive possessions ended in a score?
  3. What percentage of field goals made by a player were off of an assist?
  4. How often are a player's missed shots rebounded by a teammate?
  5. How well did the team rebound while the player was on the court?
  6. How often did a player end a possession by making at least 1 free throw?
  7. How often does a player give a foul, and the opponent miss at least 1 free throw (e.g. Hack-a-Shaq)?
None of these questions - and others I haven't posed - can be answered by looking at the game box score. So the only recourse is to make estimates, based on a series of formulas introduced by Dean Oliver (and presumably used by Henry Sugar).

However, all of the questions asked above can be answered by parsing the available play-by-play from the game. And that is what I propose to do.

A few points to consider:
  • While I can improve the accuracy of the final stats by replacing estimates with actual tallies of various components of the calculations, I'm not modifying the philosphy (or math) of the final stats. That is, if you don't think individual player Offensive Rating is a good measure of how a player contributes on offense, there is little here to convince you otherwise. Of course, if your main quibble is with D. Oliver's many underlying estimates, keep reading.
  • As I've said before, the drawback of using play-by-play data is that there are inevitably errors in the transcript, which can lead to uncertainty in assigning credit or blame. However, I am not convinced that these same errors aren't also in the official box score, but are just hidden from view. Just for Georgetown, I know of at least one instance where Ken Pomeroy found an error in the play-by-play that propagated to the box score.
  • I am not exploiting the play-by-play fully yet, because if takes a lot of work. I've written over 5000 lines of code so far (yes, that was a brag) and my wife keeps mentioning how much time I spend working on the program, and something about a divorce (at least I think that's what she said, I wasn't really paying attention). For instance, I could record the shooting percentage of each player making an assisted basket, but I don't yet. I could distinguish between assisted dunks, layups and jumpers, but I don't yet.
A bigger point, and it goes back to an early post, is that I don't really believe in D. Oliver's defensive stats, and frankly I don't think he does either. They are merely an estimate, using an exceeding limited toolbox. Here's what I wrote there to briefly explain his Defensive Rating stat:

Defensive rating is an attempt to estimate the contribution of each player to the team's defensive efficiency. It is calculated as team defensive efficiency, plus one-fifth of the difference between team defensive efficiency and individual player stops per 100 possessions played. Player individual stops are estimated from the number of blocks, steals and defensive rebounds each player has, plus some team stats. Since it is not a simple ratio, it is more like being graded on a curve, such as that it is limited to the range of 80% - 120% of team defensive efficiency. So, a player who literally refused to play defense (e.g. Donte Greene) could score no worse than 80% of his team's efficiency. I would describe this stat as a very rough estimate of actual defensive worth . . .
Later in that same post, I discussed an alternative method, which was simply to use available plus/minus stats to calculate the team's defensive efficiency while the player was on the court, and use that (less the team's defensive efficiency while the player was off the court) to rate that player's defensive ability.

The drawback to this method, pointed out on this thread on Hoyatalk, is that it the quality of one's teammates can have a big effect.

So here, I'm proposing a new method: I am using Dean Oliver's basic statistics for player offensive and defensive rating, but the data I am feeding into the underlying equations are only those generated by his team while the player was on the court. This should especially help with defensive stats, in that the base team defensive efficiency used is now the def. efficiency while the player was on the court (i.e. the player receives no credit or penalty for great or lousy defense played by his teammates while he sat on the bench). The remainder of Dean Oliver's def. rating calc. (stops, stop %, scoring poss., etc.) is used as originally described. Additionally, as stated earlier I am removing as many of the estimates used by Oliver as I can, when I have time. The seven listed above are all incorporated, along with a few others (e.g. is a blocked shot recovered by the shooter's team?). I'll try to write up a FAQ covering all of the gory details at some point this season - likely when my wife is out of town.

As a test case, I've run the Marq/Nova game mentioned at the top of this post. Here's what I get:
INDIVIDUAL NET POINTS STATS

Marquette             Off    Poss           Individ     Def             Individ                             
Player                Poss   Used    ORtg   Pts Prod    Poss    DRtg   Pts Allow   Net Pts
HAYWARD, Lazar         59    12.5   111.2    13.9        59    100.9     11.9       +2.0                  
BARRO, Ousmane         51     3.5   149.3     5.2        51     95.4      9.7       -4.6                  
JAMES, Dominic         69    18.0   140.5    25.3        70     97.3     13.6      +11.7                  
MCNEAL, Jerel          66    18.6    79.0    14.7        67     96.4     12.9       +1.8                 
MATTHEWS, Wesley       42    11.7    92.8    10.8        42     86.0      7.2       +3.6                    
ACKER, Maurice         23     4.7   181.0     8.4        23     81.8      3.8       +4.7                  
FITZGERALD, Dan        16     0.3   280.0     0.9        17    104.5      3.6       -2.7                   
CUBILLAN, David        31     3.1    74.8     2.3        32    134.1      8.6       -6.3                   
BURKE, Dwight           6     0.0     -       0.0         7     62.9      0.9       -0.9             
MBAKWE, Trevor         12     2.0   100.0     2.0        12    124.4      3.0       -1.0                  
TOTALS                 75    74.3   112.4    83.5        76     98.7     74.6       +8.9          

Villanova             Off    Poss           Individ     Def             Individ                         
Player                Poss   Used    ORtg   Pts Prod    Poss    DRtg   Pts Allow   Net Pts
Pena, Antonio          62    12.9    75.6     9.8        60    123.0     14.8       -5.0                 
Cunningham, Dante      61    12.0    93.3    11.2        62    112.0     13.9       -2.7                     
Reynolds, Scottie      60    16.1    85.4    13.7        57    123.9     14.1       -0.4                     
Fisher, Corey          62    17.4    76.4    13.3        59    112.0     13.2       +0.1                 
Anderson, Dwayne       54     6.6   154.1    10.1        53    125.3     13.3       -3.1                    
Redding, Reggie        25     2.0   223.2     4.4        28     80.9      4.5       -0.1                   
Clark, Shane            8     0.8   333.3     2.5         9     70.2      1.3       +1.2                
Stokes, Corey          48     7.6   121.7     9.3        47    106.7     10.0       -0.7                 
TOTALS                 76    75.3    98.7    74.3        75    113.3     85.1      -10.8                    
The actual score of the game was MU 85, VU 75.

Several of the columns here are the same as Henry Sugar's above, but there are a few new ones as well. Briefly
  • Off/Def Poss - the number of offensive or defensive possessions that a player was on the court; I think this is more useful than minutes played.
  • Poss Used - the number of offensive possessions used by a player (partial credit due to assists and offensive rebounds).
  • Off. Rating - the number of individual points produced, divided by the number of offensive possessions used, multiplied by 100. This is an estimate of the number of points a player would produce (not simply score) in 100 possessions.
  • Points Produced - similar to possessions used, it is an estimate of the team points scored that can be credited to an individual player; again, partial credit due to assists and offensive rebounds.
  • Def. Rating - An estimate of the number of points a player would allow in 100 possessions. See the discussion above the table for the details.
  • Points Allowed - The actual number of points allowed by the player - again an estimate.
  • Net Points - The difference between points produced and points allowed.

I've also included a totals line for all stats, so you can actually check my work.

The total Off Poss & Def Poss are the actual number of possessions in the game.

The total number of possessions used by each team agree very well with the reality - for my data parser, total possessions used are typically within 5% of actual possessions played, but this game worked exceptionally well.

Total points produced for each team are also very close to actual points scored. These should be with 10%, and often with 5%.

The summed points produced divided by total possessions used gives an estimate of team off. efficiency. This is the value listed as the total of ORtg. The estimated team offensive efficiencies (112.4 & 98.7) agree extremely well with actual off. efficiencies for each team (113.3 & 98.7).

At least for this game, it appears that my method is giving a quite satisfactory measure of what happened on offense. It won't always be so accurate, but this is why I want to give these totals - it will allow my reader to decide for himself (do any women read this blog?) how well the stats analysis is working.

Defensive stats are more tightly coupled to team, rather than individual, data so the totals here aren't quite so useful. The DRtg totals are simply team defensive efficiencies, calculated as team points allowed divided by defensive possessions.

Here, the summed individual points allowed for each team agree within 1 point of the actual score, another excellent result - I find typically they will agree within 5 points.

Finally, the net points totals give two estimates of the margin of victory (or loss). The average of the two [(8.9 + 10.7)/2] = 9.9 is almost exactly the true margin. It usually doesn't work quite this well!

I think this method compares favorably to the "classic" method proposed by Dean Oliver. I will keep working at it to remove additional estimated values and fix any bugs (e.g. I wasn't counting missed dunks until last week), but I think the basic framework is now in place. Any feedback would be appreciated.

Edited to add: A year later, and I did incorporate some feedback into net points. See here for the gory details.

-----------------------------------------------------------------------

Jacksonville

Finally tonight, I thought I'd take a look at last year's game vs. Jacksonville, which the Hoyas won 87-55. That link will take you to my post-game post from last season, which includes the tempo-free and HD box scores (both will be part of each post-game analysis this season, when available). Here, I'll post the net points stats from last year's game - I've bolded and italicized any player who should play tomorrow.
INDIVIDUAL NET POINTS STATS
 
Georgetown            Off    Poss           Individ     Def             Individ                        
Player                Poss   Used    ORtg   Pts Prod    Poss    DRtg   Pts Allow   Net Pts
Wallace, Jonathan      26     9.3    71.7     6.6        25     91.3      4.6       +2.1                         
Summers, DaJuan        39     8.8   125.0    11.0        36    101.8      7.3       +3.7                           
Sapp, Jessie           36     9.2    61.8     5.7        35     75.0      5.2       +0.4                    
Ewing, Patrick         26     2.0   101.6     2.0        26     55.5      2.9       -0.9                      
Hibbert, Roy           24     8.7   115.6    10.0        24     84.4      4.1       +6.0                    
Macklin, Vernon        46     4.4   143.3     6.4        45     97.8      8.8       -2.4                       
Wright, Chris          40    10.0   137.2    13.7        40     74.5      6.0       +7.7                     
Rivers, Jeremiah       28     4.7   152.7     7.1        28     83.6      4.7       +2.4                        
Jansen, Bryon           4     0.0     -       0.0         4     80.0      0.6       -0.6                     
Freeman, Austin        42     4.3   255.1    10.8        43     76.6      6.6       +4.3                       
Crawford, Tyler        29     4.5   123.0     5.5        29     95.5      5.5       +0.0                       
Wattad, Omar           10     2.1   129.3     2.7        10     90.9      1.8       +0.9                    
TOTALS                 70    67.9   120.3    81.6        69     79.7     58.1      +23.5                 

Jacksonville          Off    Poss           Individ     Def             Individ                          
Player                Poss   Used    ORtg   Pts Prod    Poss    DRtg   Pts Allow   Net Pts
SMITH, Ben             54    16.8    64.3    10.8        55    115.1     12.7       -1.9                      
HARDY, Ayron           34     5.4    73.4     4.0        37    125.0      9.3       -5.3                    
MCMILLAN, Andre        37     5.6   143.8     8.0        37    119.7      8.9       -0.8                       
COLBERT, Lehmon        40     9.0    87.8     7.9        40    105.8      8.5       -0.6                           
ALLEN, Marcus          30     3.8    95.6     3.6        30    126.3      7.6       -4.0                         
COHN, Travis           16     3.4    62.0     2.1        16    135.0      4.3       -2.2                        
GILBERT, Brian         30     3.1    97.2     3.0        30    143.6      8.6       -5.6                          
KOHIHEIM, Paul         26     3.8    20.9     0.8        25    120.5      6.0       -5.2                      
BROOKS, Aric           19     5.9    80.9     4.8        19    116.6      4.4       +0.4                        
LUKASIAK, Szymon       33     5.0    79.1     3.9        35    138.1      9.7       -5.7                            
JEFFERSON, Evan        26     5.1    59.6     3.1        26    139.5      7.3       -4.2                       
TOTALS                 69    66.9    77.8    52.0        70    124.3     86.9      -34.9              
DaJuan Summers had a great offensive game, but a lousy defensive game against the Dolphins, while Jessie Sapp was just the reverse (bad O, great D). Austin Freeman was his typical efficient self on offense but didn't use up a lot of possessions (~10%), while Chris Wright was player of the game on both ends of the court. Even Omar Wattad did his thing on the offensive end (1-1 2FG, 1-2 3FG).

I won't go into the Jacksonville players (you can see how they played last year).

The Dolphins lost to Florida State on Saturday, 59-57. J'ville was trailing 57-40 with 3:30 left and proceeded to go on a 15-1 run to bring the score to 58-55 with :20 left in the game, thanks in part to 2-8 FT shooting by FSU.

Saturday, October 18, 2008

Individual Offensive & Defensive Ratings - 2007-8 Review

General comment about the edits - I realized soon after originally posting this article that the underlying numbers just didn't look right. Sure enough, I tracked down at least 2 mistakes in my math. I think I've got everything correct now, but I make no warranty. I reserve the right to continue to make mistakes, but I will do my best to avoid them.


Before I get started, I just want to point out that the player +/- stats page has been updated, and now includes all available games for the last 2 seasons.

-----------------------------------------------------------------------------------------------

In my last few posts, I've be touting my new HD Box Score MakerTM, which uses game play-by-play data to extract a lot more info than a standard box score yields (all available HD boxes for the last 2 seasons now posted).

In my never-ending quest to keep you, my only reader, ahead of the curve when it comes to basketball knowledge, I thought I'd start a series of posts using the data generated by my HD Box Score MakerTM to learn a bit more about your Georgetown Hoyas.

To start, I thought I'd try to take on one of the questions that I raised at the end of my intro post to HD box scores:
2. Was J. Rivers really that great of a defender? I'll look at the team's offensive and defensive efficiencies with each player on or off the court, to see if I can learn a bit more about the defensive side of things.

Analogous to fielding defense in baseball, individual defense in basketball is not well-described by traditional basketball statistics. We can talk about team defensive stats (Def. Efficiency, DReb %, Def 2FG%, Def eFG%, Block %, etc.) with some confidence that we are able to describe what is actually taking place on the court, but the difficulty comes in attributing the individual defensive stops, rather than just taking a holistic view.

There are a few ways to tackle this problem:
  • Watch each game, and chart each defensive possession for who was responsible for stopping (or allowing) the defense from a score. This has been advocated by Dean Oliver, the father (mid-wife?) of advanced basketball statistics - but, as far as I know, simply isn't available for college basketball games.
  • Use the available box score data to estimate the number of stops each player makes, based on some rather large assumptions; one example of this metric is called Defensive Rating (also developed by Dean Oliver). This is similar to his Offensive Rating for individual players, which I, Ken Pomeroy and many others calculate, but uses less certain assumptions. Currently, I'm only aware of Henry Sugar at Cracked Sidewalks reporting Def. Ratings (example linked), although I'm sure there are others. I'll talk more about this stat below.
  • Use the available play-by-play data to estimate the importance of each player to total team defense. Your first thought might be that we could use the play-by-play data to determine actual defensive stops by player, but we can't. The play-by-play doesn't tell us who is guarding whom, so we'd be back to the same assumptions that Dean Oliver uses. However, there is a simple analytical tool that we now have available to us: we now know how many points each team scored when any player was on (or off) the court. That is to say, we can calculate a team's offensive and defensive efficiency (points per 100 possessions) as a function of whether any player is on the court, and thereby look at what impact each player has on team offensive or defense.

At this point, I will explain some basic terms as a refresher, and also cover what's new here. All of this is explained in much more detail at the web pages linked to the right under "Tempo-Free Stats 101." Feel free to skip ahead if this is all familiar.

Possession-based (tempo-free) statistics is a concept in basketball going back at least as far as Frank McGuire, and is useful for comparing players and teams who operate at different paces, or speeds of play. A possession ends either by a made basket (including some made FTs), a turnover or a defensive rebound - that's it, that's the list. Offensive rebounds don't create new possessions, only prolong the current one. If you use this definition, two teams will end up with either the same number (± 1) of possessions at the end of any game; since possessions go back-and-forth, it must be so. The equation for estimating total possessions per team per game is floating in various forms around the internet, but I will add to the clutter:

Possessions = FGA + 0.44 * FTA - OReb + TO

Since this formula is only an estimate of the actual number of possessions, I find that it is best to solve for each team, then take the average. Any team's (or player's) stats should be instantly comparable to any other with a per-possession system, since what is expressed is team (or player) efficiency rather than counting stats.

Offensive (and defensive) efficiency is a team statistic expressed in the units of points per 100 possessions (why per 100 possessions? so there aren't so many digits to the right of the decimal). This statistic is rather simple to calculate, once you've worked out how many possessions have been played with the equation above. Ken Pomeroy, one the populists of tempo-free stats, has an additional version of this stat, called adjusted off. (or def.) efficiency. Here, he attempts to weight points per possession based upon quality of opposition.

Offensive rating (as mentioned above) was created by Dean Oliver in an attempt to better rate individual basketball players on offense. The calculation of this stat is not simple - I've had people ask me in the past for the equation, but it's actually a bunch of equations (see this book for details). In simple terms, it is the ratio of points produced (not scored) by any player, divided by possessions used (not played), with both of these terms estimated from normal box score data. It is a tempo-free statistic, since it is expressed in points per (100) possession. Since players should be credited for assists and offensive rebounds as well as actual points scored, this rating is just an estimate of actual player worth, but the underlying assumptions are well thought out (you'll have to trust me, or read the book).

Defensive rating is an attempt to estimate the contribution of each player to the team's defensive efficiency. It is calculated as team defensive efficiency, plus one-fifth of the difference between team defensive efficiency and individual player stops per 100 possessions played. Player individual stops are estimated from the number of blocks, steals and defensive rebounds each player has, plus some team stats. Since it is not a simple ratio, it is more like being graded on a curve, such as that it is limited to the range of 80% - 120% of team defensive efficiency. So, a player who literally refused to play defense (e.g. Donte Greene) could score no worse than 80% of his team's efficiency. I would describe this stat as a very rough estimate of actual defensive worth . . .

. . . which leads me back to the point of this post (there really is a point). Now that I have access to the play-by-play of most G'town games, can I use this to better estimate the defensive contribution of each player, on a possession-basis? If so, we could finally talk about the overall value of a player to his team, rather than just his offensive contribution. The play-by-play shows who was on the court at any point during the game, so we can assign partial credit to each player for how well the team plays at both ends while he's in the game; likewise, we can see if the team plays better or worse when he leaves. This is really just applying the concept of plus-minus and Net/40 (or Roland rate), but rather using possession info to speak in tempo-free terms, rather than per-minute.

To explain explicitly here, I've taken each player, and added up the points that G'town scored and allowed while he was on the court. and how many were scored and allowed when he was off the court. In each case, I also know how many offensive or defensive possessions he participated in, so I can divide each point total by respective possessions (times 100) to find the team's offensive of defensive efficiency while he was on or off the court. Then, I find the difference between on- and off-court efficiency (either off. or def.) and add that to the team's efficiency.

For example, to calculate Jessie Sapp's Net Offensive Efficiency:

Jessie Sapp played 1171 offensive possessions, and the Hoyas scored 1298 points while he was on the court.
[1298 / 1171 x 100 = 110.8 Off. Eff. on-court]

He sat for 561 offensive possessions, and the Hoyas scored 585 points while he sat.
[585 / 561 x 100 = 104.3 Off. Eff. off-court]

So Jessie Sapp's Net Off. Eff. is equal to:
(Off. Eff. on-court - Off. Eff. off-court) + Team Off. Eff. =
(110.8 - 104.3) + 108.7 = +6.5 + 108.7 = 115.2 pts/100 possessions


Before I jump into the defensive analysis, I first want to see if my idea that player-based on-court / off-court net efficiency correlates to individual player rating holds water. To do this, I'll take a look at each player's net offensive efficiency versus individual offensive rating for last season.

One last point before I go on, the individual player ratings here won't match exactly with what either Pomeroy or I post for season totals. Since I don't have play-by-play data for all games, I re-ran the player ratings using box score data only for games that also had p-b-p data [to see which games are missing, go to the player +/- page].

Let's take a look (as always, click any image to enlarge):




This seems to work quite well! Players in the upper right of the graph are the best offensive players by either metric, while players in the lower left are not carrying their weight. The red line is a linear fit to all the data (r = 0.81), excluding Bryon Janson, who just doesn't have enough playing time to generate meaningful stats. The slope of the line is about 0.55, significantly less than 1, which is actually to be expected. The Net Team Efficiency stat doesn't completely isolate a player from his teammates in the way that Off. Rating attempts to do; since there is variability player-to-player, the range of the Net. Team Eff. stat gets compressed - a bad offensive player surrounded by good players will look better than he is.

The strong correlation indicates that the two statistics are highly coupled (co-variant). Individual offensive rating is a fairly well-accepted statistic, and it seems to do a good job of measuring how important a player is to team efficiency. Of course, the converse should also be true - team offensive efficiency as a function of each player on or off the court is a good measure of individual offensive value.

Moreover, and here's where I may be stretching the statistics a bit, the scatter plot can tell us a bit more: if a player is above the line, he makes the team more efficient than expected based upon Off. Rating (i.e. the player is underrated by Oliver/Pomeroy/etc.) while if he is below the line, he is overrated. Keep in mind that there are considerable uncertainties for the data on both axes that are not shown or even calculated, because that would make my life a lot harder. But it looks like Jessie Sapp and Roy Hibbert were underrated offensively last season, while Patrick Ewing Jr. and Vernon Macklin were overrated.


Now, let's now take a look at the defensive side. The math as the same as presented above, just looking at defensive possessions now.




Things here are not so clear-cut as for offense. There is poor correlation between the two data sets (r = 0.11), so I've just thrown a 1:1 line onto the chart. Note that both axes have their scaling reversed (they get smaller as you head away from the origin), since a lower defensive rating or efficiency is better. Again, players in the upper right corner are the best defenders, those in the lower left are the worst.

One thing that I notice immediately is that the scaling for the two statistics is much closer to 1:1 than for offense. We already expect that Net Def. Rating should be compressed since we can't isolate individual players, only their effect on the team while on the court. But here, the Def. Rating stat shows about the same scaling meaning either a) there isn't as large a difference between a good and bad defensive player as there is for an offensive player, or b) the Def. Rating stat isn't able to isolate individual defensive skills.

To take this a bit further, we demonstrated above that the Net. Efficiency methodology for offense seems to work quite well in correlating to a "good" measure of offensive prowess, albeit on a somewhat compressed scale. Since the method is identical for defense and offense, there's no reason to expect Net Efficiency to stop working for defense. Therefore, it could be argued (I just did) that Net. Def. Eff. is a better measure than Def. Rating.

If you've not read Basketball on Paper, you should probably just skip over the next paragraph.

Digression: Before I go on, I should point out that I'm using a slightly modified version of D. Oliver's Defensive Rating calculation. His formula estimates defensive stops in two parts, and the second has a necessary assumption that he, himself, acknowledges to be poor with regards to position-specific uncredited stops. Since centers get a disproportionate number of stops by way of blocks, they tend to be overweighted by his formula (for reasons far too obscure to explain here). I've added a simple weighting factor, based on Steals/(Steals+Blocks) to correct this. For this data set, the effect of this correction ranges from -2.7% for Roy Hibbert to +2.3% for Jonathan Wallace and Chris Wright. (n.b. - The weighting factor is based on Oliver's own data).

Returning to the scatter plot, once again we can find over- and underrated players by using the fitted line.

Now, Tyler Crawford and Chris Wright are the most overrated defenders, while Jonathan Wallace (!), Roy Hibbert and Jessie Sapp are underrated. Of course, that only looks at the comparison between two poorly correlated stats; the real take-home message is that Hibbert, Sapp, DaJuan Summers and Patrick Ewing anchored last year's excellent defense, just as Hibbert, Wallace and Austin Freeman were the most effective on offense.

And to answer the question that started this whole thing - yes, Rivers was a good defender, but not extraordinarily so, and not as important as Hibbert, Ewing or Summers. In fact his stats are not obviously better than either Sapp's or Wallace's(!). I will speculate that Rivers was the best on-ball defender as a guard, but Wallace and Sapp were more sound within the defensive schemes used last year (I just made that up). And I'm not sure why Omar Wattad looks like Gene Smith on this plot, but I'll guess it's just the result of a small sample size (n = 58 def. possessions).


Finally, we can combine the offensive and defensive metrics on a single plot, to get a rank of the overall value of each player. Here, I'm simply taking the average of Off. Rating & Net. Off. Eff. for the y-axis, and the average of Def. Rating & Net. Def. Eff. for the x-axis. Here, I'm hoping that the averages of two measures of the same variable come closer to describing its true character than either measure on its own.





This plot is a bit more complicated, as I'm trying to convey a lot of information.

Again, you'll need to re-jigger yourself to the axes. Offense is on the left-axis, with up equaling better performance; defense is on the bottom axis, but still with reversed scaling, so that right equals better performance. Players in the upper right are most valuable, players in the lower left are least valuable; those closer to the upper left have more value on offense, those down and to the right have more value on defense. This last bit looks to be well correlated with expectation, as the two players best know for offense rather than defense (Wallace & Freeman) show up right about where you'd think.

The size of the names are now scaled by possessions played, so Omar Wattad's newly-discovered value as an all-world defender is now tempered by the fact that he rarely plays. DaJuan Summers somewhat swallows up Patrick Ewing because of this, but I think you can still make them out.

Finally, the series of diagonal lines (isopleths) on the chart mark show contours of total player value (i.e. the difference between off. and defensive worth). For example, Jessie Sapp's off. worth = 108.9 and his def. worth = 89.8, so you'd expect that he'd provide +19.1 (= 108.9 - 89.8) pts./100 poss. to the team. Meanwhile, Austin Freeman's off. worth = 115.4 and his def. worth = 95.8, so you'd expect that he'd provide +19.6 pts./100 poss. That is, Sapp and Freeman were essential equally valuable to last year's team on a per possession basis, although they did it in different ways. Because they are rated at equal value, they both lie on about the same position relative to the diagonal lines.

Moreover, if you had a team of players all equally efficient overall as Sapp and Freeman, you'd expect the overall difference in team Off. Eff. and Def. Eff. to be around +19 pts/100 poss. FWIW, last year, G'town's efficiency difference was +18.8 (raw, not adjusted), good enough for a #2 seed in the NCAA tournament.

Here's a summary table of off., def. and total player worth for all the players:
                      Off.      Def.    Total
Hibbert, Roy 122.3 90.2 32.1
Wallace, Jonathan 118.7 94.0 24.7
Freeman, Austin 115.4 95.8 19.6
Sapp, Jessie 108.9 89.8 19.1
Ewing, Patrick 106.1 90.5 15.6
Summers, DaJuan 105.6 90.6 15.0
Wattad, Omar 103.3 88.3 14.9
Wright, Chris 100.8 93.2 7.6
Crawford, Tyler 95.6 95.4 0.1
Rivers, Jeremiah 90.1 94.4 -4.3
Macklin, Vernon 94.4 100.0 -5.6

We will miss Roy Hibbert. On a team that was ranked 7th by Ken Pomeroy after the NCAA tournament, Mr. Hibbert was the best Hoya player on the court by a large margin.

Next comes the gang of five (+1), who were the other important contributors to the Hoya's success; in very rough order of importance: Wallace, then Freeman and Sapp, then Summers and Ewing. Wattad sneaks in right behind this group, despite his few possessions (who knows, maybe the whole point of this article was to find a new player to champion; after all, the last time went so well).

By my reckoning, the two soon-to-be-transfers were not helping much last season. In the end, Rivers' defense just couldn't make up for his offensive woes, while Macklin struggled at both ends of the court. I never gave much thought to Macklin's defense, but he was easily the worst defender on the team by my numbers. Does that seem right? Tyler Crawford struggled with his outside shooting last year (3-22 3FGs), and wasn't able to make up for it with great defense.

There's one returning player that I haven't mentioned - Chris Wright. He missed the majority of the season with a foot injury, and ended up with a little more than half of Macklin's total time played. After struggling early in the season, he seemed to have a breakthrough in the 2nd half against Derrick Rose and Memphis, only to go down 2 games later. And while he played in 5 post-season games after getting healthy (3 in the BET, 2 in the NCAA), I only have the Pitt game in the BET finals in this analysis, since I don't have p-b-p for the other 4 games. From looking at the box scores, 3 of the 4 games I'm missing (Villanova, UMBC, Davidson) were among his best.

What I'm saying is that I think Wright is being undervalued here, not because there's anything wrong with the analysis, but because his underlying data doesn't do him justice. I hope I'm right.