Football Scatterplot!
Special holiday weekend edition scatterplot:
Technical explanation:
- Data based on 8 conference games only for each team. Sacks (and associated negative yardage) counted as pass plays.
- Horizontal axis shows differential between pass yards per attempt and rush yards per attempt.
- Vertical axis shows percentage of total plays on which a team attempted a pass (or was sacked).
- Dashed line is trend line based on linear regression.
The premise here is that, the better a team is at passing the ball vs. running the ball, the more often that team will pass the ball. And, for the most part, Big Ten coaches look pretty darn rational. The data points show a clear linear trend. The teams above the trend line (Indiana, Purdue, Illinois) were generally playing from behind and would have passed the ball more out of necessity. The teams below the trend line, on the other hand, are teams that were usually playing with a lead (Ohio State, Wisconsin, Penn State) or had interception-prone quarterbacks (Michigan, Iowa). (Data are not adjusted in any way for interceptions. Also, interpreting the data for teams with running QBs like Illinois and OSU may not be quite so straightforward.)
I had originally constructed this scatterplot to see if I could confirm my intuitive judgment that the MSU coaching staff didn't utilize the Cousins-led passing attack to the full extent it should have. If you trust the dashed trend line as a good approximation of where a team's run-pass balance should be based on the relative strengths of its passing/rushing attacks, though, the aggregate data would indicate the balance was about right.
One caveat: MSU's rushing numbers may be skewed high by two Keshawn Martin end-around runs totaling 154 yards. Take those two runs out of the sample and MSU's rushing yards/attempt figure drops from 4.6 to 4.0 and MSU's data point on the scatterplot moves very close to the right-hand boundary. Of course, it's possible other teams also have big runs on nonstandard rushing attempts in their data. And you could argue the Keith Nichol garbage-time TD passes vs. Wisconsin and Penn State skew the passing numbers upward, too.
Regardless, MSU did attempt to pass the ball at the 4th highest rate in the conference, behind two teams that played from behind most of the season (probably a 50/50 split for MSU on playing from behind/in front) and a team that runs a pure spread offense designed for frequent, short passes (Northwestern).
Still, I can't shake the intuitive judgment that, while MSU may have passed the ball with a reasonably-high frequency, it did so in a much-too-predicable fashion. Fairly-fresh-in-my-mind example: The opening drive of the Penn State game (when MSU had won the toss and chosen to take the ball first).
Wagner, Collin kickoff 65 yards to the MSU5, Martin, Keshawn return 25 yards
to the MSU30 (Timmons, K.).
M 1-10 M30 Cousins, Kirk pass incomplete to White, Blair.
M 2-10 M30 Caper, Larry rush for loss of 1 yard to the MSU29 (Bowman, Navorro).
M 3-11 M29 Cousins, Kirk rush for 7 yards to the MSU36 (Bowman, Navorro).
M 4-4 M36 Bates, Aaron punt 40 yards to the PSU24, Astorino, Drew return 8 yards
On the first play, White went in motion from right to left toward two receivers on the other side. At that point, I'm pretty sure every MSU fan in the stadium--not to mention the Penn State defense--knew what was coming: a flare pass to White behind the line of scrimmage. The Penn State defensive backs moved aggressively toward the line of scrimmage and blew the play up.
Next up? Well, if you didn't run the ball on first down, you certainly have to try to run it on second down, right? The result was, not surprisingly, a loss of yardage.
Finally, Kirk Cousins gets the chance to throw the ball downfield on the third down. But the Penn State defense knows what's coming, Cousins can't find an open receiver, and he's forced to scramble for a gain well short of the first down.
So there's an example of MSU passing on 2 out of 3 plays, but doing so in an entirely predictable and defensible manner. With Kirk Cousins--the clear front-runner for first team All-Big Ten quarterback, and perhaps Big Ten Ofensive POY, in 2010--back for two more seasons, that kind of predictability (predicated on the notion that running the ball on early downs is the basis for your offense, darn it all) sure seems like it wil continue to be an impediment to the team's success if it isn't addressed by the coaching staff--before the bowl game, ideally.
Data Appendix:
| Team | Rush Att | Rush Yds | Rush Y/A | Pass Att | Pass Yds | Pass Y/A | Differential | Pass% |
|---|---|---|---|---|---|---|---|---|
| Michigan St | 239 | 1,092 | 4.6 | 267 | 1,923 | 7.2 | 2.6 | 52.8 |
| Iowa | 254 | 918 | 3.6 | 252 | 1,538 | 6.1 | 2.5 | 49.8 |
| Northwestern | 275 | 988 | 3.6 | 353 | 2,031 | 5.8 | 2.2 | 56.2 |
| Michigan | 292 | 1,094 | 3.7 | 254 | 1,476 | 5.8 | 2.1 | 46.5 |
| Penn State | 279 | 1,458 | 5.2 | 243 | 1,747 | 7.2 | 2.0 | 46.6 |
| Purdue | 240 | 1,023 | 4.3 | 324 | 1,989 | 6.1 | 1.9 | 57.4 |
| Indiana | 217 | 978 | 4.5 | 321 | 2,005 | 6.2 | 1.7 | 59.7 |
| Minnesota | 245 | 960 | 3.9 | 251 | 1,402 | 5.6 | 1.7 | 50.6 |
| Wisconsin | 350 | 1,698 | 4.9 | 238 | 1,462 | 6.1 | 1.3 | 40.5 |
| Ohio State | 335 | 1,721 | 5.1 | 176 | 948 | 5.4 | 0.2 | 34.4 |
| Illinois | 297 | 1,553 | 5.2 | 247 | 1,272 | 5.1 | (0.1) | 45.4 |
P.S. If I can work up the gumption, I'm intending to go through this same exercise for defensive stats.
3 comments
|
0 recs |
Do you like this story?
Comments
Interesting
The way I see this graph, the farther you are to the right, the more you should be passing.
The x-axis is the difference in YPA. MSU has the largest difference between passing and rushing indicating that MSU should have passed the ball more often, if not the most often in the conference. MSU was more successful passing than they were rushing.
This chart is basically a success chart for the passing game. If you are on the right of the graph, you can throw the ball but not run. However, the opposite is not true. If you are on the left, you could be both good at rushing and passing, or bad at both.
Maybe some sort of normalization of the passing YPA would make the chart more valueable. IE passing YPA divided by the conference average or a standard value, 6.5 YPA is basically an average value. (IE if you are good, it is above 6.5, bad is below 6.5) Then the same for rushing, ie 4.5 ypc being the average value. Then it would show a significant difference between the “goodness” of rushing/passing.
That make any sense?
On second thought
I think it would better display the data to graph passing YPA versus rushing YPA, then add the percent pass as a number on the data point.
This would show if a team is good at passing and rushing they would be in the top right of the graph, a team that is good at running but bad at passing would be in the top left, a team good at passing but bad at rushing would be in the bottom right, and a team bad at everything would be in the bottom left.
Then it would clearly show what a team is good at then have the pass/run percent added to the data point to show how they got to that point.
3-dimensional scatterplot!
The data’s there if someone with the ambition wants to give it shot.
Fight for The Only Colors: Green and White!
by KJ@theonlycolors on Nov 28, 2009 11:00 AM CST up reply actions

by 





















