AE 87
Helluva Engineer
- Messages
- 13,030
Okay, so just to review: Points/Drive is a calculated, raw (not adjusted for opposition) stat. It functions as an alternative to the pts/game stat which is sometimes labeled scoring offense.
I see two main advantages for it over the more traditional scoring offense stat. First, it does not count return scores (kickoffs, turnovers, punts) as offensive scores, which most calculations of points/game do. Second, it offers a better comparison between more deliberative offenses that run more (and so have fewer drives in a game) and more high-paced offenses that pass more (and so have more drives in a game).
It shares the same drawback of other raw stats in not being adjusted for the quality of opposition. It has a further drawback that it counts all turnovers as ends of drives when calculating the number of drives, meaning, for example, that Nealy's lost fumble in returning the interception counted as an offensive drive.
So, where do we stand after week 12?
Offense: Over the first 12 weeks, our offense has averaged 3.52 points/drive. By this measure, we have the #5 offense in country. If you're wondering, it would be 3.55 ppd and #4 if we remove Nealy's drive, so it's not that big of a deal. After week 8, UNC, we were also #5 averaging 3.4 ppd.
Defense: Over the first 12 weeks, our defense has allowed on average 2.32 ppd, for a #98 ranking in scoring defense. This is a significant improvement over where we were after the UNC game, Week 8: 2.88 ppd allowed, #115. To put some numbers on this improvement, over the last 4 weeks, we've allowed on average 1.48 ppd, a 95% improvement (I know that technically we should look at opposition strength, but we're just looking at the raw data). To put this improvement in perspective, that 1.48 ppd allowed would be good enough for #19 in scoring D, tied with TCU, if extended across the whole season.
I see two main advantages for it over the more traditional scoring offense stat. First, it does not count return scores (kickoffs, turnovers, punts) as offensive scores, which most calculations of points/game do. Second, it offers a better comparison between more deliberative offenses that run more (and so have fewer drives in a game) and more high-paced offenses that pass more (and so have more drives in a game).
It shares the same drawback of other raw stats in not being adjusted for the quality of opposition. It has a further drawback that it counts all turnovers as ends of drives when calculating the number of drives, meaning, for example, that Nealy's lost fumble in returning the interception counted as an offensive drive.
So, where do we stand after week 12?
Offense: Over the first 12 weeks, our offense has averaged 3.52 points/drive. By this measure, we have the #5 offense in country. If you're wondering, it would be 3.55 ppd and #4 if we remove Nealy's drive, so it's not that big of a deal. After week 8, UNC, we were also #5 averaging 3.4 ppd.
Defense: Over the first 12 weeks, our defense has allowed on average 2.32 ppd, for a #98 ranking in scoring defense. This is a significant improvement over where we were after the UNC game, Week 8: 2.88 ppd allowed, #115. To put some numbers on this improvement, over the last 4 weeks, we've allowed on average 1.48 ppd, a 95% improvement (I know that technically we should look at opposition strength, but we're just looking at the raw data). To put this improvement in perspective, that 1.48 ppd allowed would be good enough for #19 in scoring D, tied with TCU, if extended across the whole season.