Math 9314: O-h…Oh No

We all know what happened in Columbus last week. After three thrilling wins in Maui, Duke suffered a major letdown against a surefire national title contender. Ohio State utilized their home court advantage to the fullest, gaining momentum early and exploiting Duke’s weaknesses en route to a convincing win. Funny how much of a factor the three keys I mentioned in my preview column played into last week’s outcome. Just in case you missed the game or are willing to relive the demoralizing experience, it’s that time of the week to take a look back at our favorite Blue Devils’ performance (or lack thereof) using advanced metrics, which can be viewed on our fancy shmancy motion chart.

Let’s take a look at last week’s game beyond the box score:

It seems like every week there are always a few players whose GameScores hover around zero or even slightly in the negatives—this is not uncommon. Typically these are players that played very few minutes in the game and may have missed their only shot attempt, but not this week. If you take a look at the players located in the bottom left hand corner of our chart (for all intents and purposes we’ll call this “The Zafirovski Zone”), you’ll be shocked to see three Duke starters with negative GameScores. In fact, four out of the top seven in the Duke rotation—Andre Dawkins, Ryan Kelly, Seth Curry, and Tyler Thornton—could not record positive GameScores last week. They were essentially nonfactors in this game, playing a combined 68 minutes against Ohio State, as compared to a combined 127 minutes in Duke’s Maui Championship victory over Kansas. The group shot a combined 3-13 from the field and will need to make vast improvements as Duke looks to get back on track.

On the other hand, while many of Duke’s starters struggled, the Blue Devils were able to get positive production from players that often reside deeper in their rotation. Note: by positive I mean “greater than zero”, though their outputs were positive they all still registered below 6.6. Miles Plumlee, Josh Hairston, Michael Gbinije, and Quinn Cook all ended up outside of The Zafirovski Zone this week, each playing significant minutes down the stretch with the game out of reach. They did provide some bright spots, however. Cook added four points and four assists in just 14 minutes and Hairston played his usual physical defense while shooting a perfect 3-for-3 from the field.

Austin Rivers sweeps in for a layup, two of his 22 points against Ohio State (photo courtesy of DukeBluePlanet)

Austin Rivers and Mason Plumlee were essentially Duke’s only two efficient offensive options against the Buckeyes. Rivers’ GameScore of 12.1 was his second highest this season as he poured in a career-high 22 points on 8-of-18 shooting. Although he was receiving little-to-no support, Rivers looked like a dangerous offensive weapon for much of the game, knifing through the defense and attacking the rim for easy buckets. Mason, who had the toughest task of any Duke player in guarding Preseason All-American and Naismith candidate Jared Sullinger, was able to fight off early foul trouble to contribute 16 points and eight rebounds. His final GameScore was only 10.9 as he committed four turnovers and three personal fouls, but he continued to assert himself with his improved low post game.

Unfortunately, there has not been much discussion of effective field goal percentage (eFG%) in this post, simply because other than the few players that made their only two or three shots, we did not have much of an eFG% to speak of. This is puzzling because Duke finished shooting 47.3% from the floor from the game, which is better than they shot in the Maui final against Kansas. However, Duke had a low eFG% because they only shot 3-of-15 from beyond the arc, and the eFG% formula weights three-point shots higher than field goals.

Ultimately GameScores are meant to take into account all of the positive and negative aspects of a player’s performance and measure of the amount of points you contributed to your team. This tells the tale of the Ohio State matchup for the Blue Devils, whose combined team score was a mere 36.2. We can only hope that a tough week at practice helped the team regain focus, and we can be almost certain that you’ll see some changes Wednesday night against Colorado State. Be on the lookout tomorrow morning for our game preview of that matchup. Until then, stay Crazie, my friends.