• Follow us on Twitter @buckeyeplanet and @bp_recruiting, like us on Facebook! Enjoy a post or article, recommend it to others! BP is only as strong as its community, and we only promote by word of mouth, so share away!
  • Consider registering! Fewer and higher quality ads, no emails you don't want, access to all the forums, download game torrents, private messages, polls, Sportsbook, etc. Even if you just want to lurk, there are a lot of good reasons to register!

tOSU @ Northwestern, Sat Nov 5, 12pm, ABC

Positives are we won the game. We only gave up 7 points. We scored the last 21 pts. CJ ran the ball and he did so effectively. We overcame the weather which took away our deep passing game. We are 9-0.

Negatives...don't get me started...
MORE POSITIVES
The three H's had very productive games:
Marvin Harrison kept moving the chains with numerous first down catches
Hickman was the star on defense
Zach Harrison had another solid day.
Running game was much better in the 2nd half
Four 4th down stops by the D
A shutout in the 2nd half by the D
 
Upvote 0
there's another tweet, of another run play, where williams does try to take exactly this cutback "across the RT's ass".

looks like he was wanting to hit the B-gap, but then stopped when stover got chucked into the gap, and then tried to cutback to the outside. and he probably would have made it except that he slipped when he tried to plant his left foot, and went down.

#99 (adebawore) absolutely mauls stover, and you can see that stover knows he got manhandled from his reaction (slamming his fist on the grass) after the play.




About this play.

- Cade played too high, didn't keep his outside shoulder controlled and overran this block. He used far more strength than he did technique here, because pinning that EMOLS in should have been a winnable assignment when the 7tech crosses your face. As a result, his man was able to work back across his body, disengage and get under that kick out from the backside lead. In the split zone it's a sift block, or U block, depending on what coach is calling it. Although in most split zones that block goes front side to weakside edge/kick out. In this case, the EMOLS (edge) attacks the interior shoulder of Cade, so now that sift can come down the line and look for work on a LB or DB as opposed to kicking out the edge.

- It's fun watching these designs because I swear so many of these calls are half gap, half inside zone in a lot of these systems.

- frontside 3 tech tries to backdoor this and Dawand picks it up nicely.

- another individual assignment defeat up front that blows the play up.


At times, I feel like I'm watching the Oline from the 2015 Browns. They came off a highly successful 2014 campaign (by Cleveland standards) rushing the ball. That was under Young Shanny. Sadly we lost Alex Mack middle of the previous season. But there are similar results there that I remember that team having - boom or bust running game. You'd either get explosive running plays, or you'd see TFL and TFNG. A lot of it stemming up front with one blown assignment or the running backs (Crow) missing their key, pressing a hole too long and cutting too late. It just feels like Deja Vu'.
 
Upvote 0
Watching this game again the ref crew serious got an F grade all the way around. Spots, no-calls, reviews, everything. Didnt change the outcome per se but maybe the score a touch and a bit of the stress level this game caused. Not the reason for a bad game by our Bucks though.
Officiating across the board this year has been dismal in CFB. I've been watching CFB for 55+ years and this year is the worst I've ever seen.
 
Upvote 0
About this play.

- Cade played too high, didn't keep his outside shoulder controlled and overran this block. He used far more strength than he did technique here, because pinning that EMOLS in should have been a winnable assignment when the 7tech crosses your face. As a result, his man was able to work back across his body, disengage and get under that kick out from the backside lead. In the split zone it's a sift block, or U block, depending on what coach is calling it. Although in most split zones that block goes front side to weakside edge/kick out. In this case, the EMOLS (edge) attacks the interior shoulder of Cade, so now that sift can come down the line and look for work on a LB or DB as opposed to kicking out the edge.

- It's fun watching these designs because I swear so many of these calls are half gap, half inside zone in a lot of these systems.

- frontside 3 tech tries to backdoor this and Dawand picks it up nicely.

- another individual assignment defeat up front that blows the play up.


At times, I feel like I'm watching the Oline from the 2015 Browns. They came off a highly successful 2014 campaign (by Cleveland standards) rushing the ball. That was under Young Shanny. Sadly we lost Alex Mack middle of the previous season. But there are similar results there that I remember that team having - boom or bust running game. You'd either get explosive running plays, or you'd see TFL and TFNG. A lot of it stemming up front with one blown assignment or the running backs (Crow) missing their key, pressing a hole too long and cutting too late. It just feels like Deja Vu'.
it's a small thing, and maybe it's nothing, but he's had a brace on his left arm for about three weeks now. i was wondering if he tried to overcompensate on this block with his right arm / right shoulder and adebawore basically just brushed him off.
and there's no way adebawore is 6'-2" as he's listed on the NW roster. no way.
fun stuff to take a deep dive on. it also shows how many little things have to go perfectly for these kinds of plays to work. if they do, though, it's a huge huge payoff.
 
Upvote 0
it's a small thing, and maybe it's nothing, but he's had a brace on his left arm for about three weeks now. i was wondering if he tried to overcompensate on this block with his right arm / right shoulder and adebawore basically just brushed him off.
and there's no way adebawore is 6'-2" as he's listed on the NW roster. no way.
fun stuff to take a deep dive on. it also shows how many little things have to go perfectly for these kinds of plays to work. if they do, though, it's a huge huge payoff.

Brace might have something to do with it, playing through shoulder and elbow pain as a lineman or TE is insane. But it still doesn't excuse some of the technique, that's just flat out losing your head in the moment.

And yes, it's fun to go back and watch how things unfold. Football is such a fast and complex sport that you truly have to do these things to better understand them. But the running game is really not different than limiting the run on defense. Takes effort, execution, being assignment sound and most importantly - selfless play.
 
Upvote 0
Thoughts and observations before we move on to the Indinia game:

The rushing offense had fans pulling hairs out again, and understandably so. But if one just watch the box score instead of the game, it was hardly a bad day for the run game in the office:
Team O
Rushing 207
Rushing Attempts 35
Yards per rush 5.9
That was a better ypc average than TTUN did against Butgers:
Team M
Rushing 282
Rushing Attempts 53
Yards per rush 5.3
I also charted all tOSU runs from the NW game, and the rolling 3-play ypc:
upload_2022-11-12_5-3-48.png

tOSU had bad stretch in the 1Q (culminated in the failed 4th-and-1 rush), but actually recovered or adjusted fairly well afterwards; their rolling 3-play ypc never dropped below the critical 3.5 line until the final drive when they just couldn't wait to get out of Evanston. (If a team is averaging more than 3.5 ypc consistently, it can keep drives alive by rushing exclusively ... without risking it on 4th.) IMO the bad stretch in the 1Q skewed our perception of the rush O adversely.

However, we do have a short yardage problem (dating back to summer camp, or even laster year). Remember this nugget from August?



All the short yardage runs from the NW game (any down, distance < 3):
perioddowndistanceyardsGainedathleteName
1413Miyan Williams
1310Miyan Williams
1310Miyan Williams
1410Miyan Williams
2332Miyan Williams
24116C.J. Stroud
33327Miyan Williams
4222Miyan Williams
4326Miyan Williams
That was a conversion rate of 5/9, or 55%. Definitely needs more work. If we count consecutive 3rd & 4th down runs as 1 data point, the conversion rate looks a little better at 5/7, or 71%.

For reference, I found an article charting average 3rd down conversion rate based on distance from Covid-shortened 2020 season:
league_averages.png


Now regarding the rush defense, NW gained 200+ yards, but scored only 7 points (61 rush yards on NW's only TD drive in the 1H).

In general, tOSU played bend-don't-break defense. NW would break occasional big runs, especially early in drives, but never had sustained success. This can be visualized in the following chart. NW's run game was very herky-jerky, every spike (big run from NW to start a drive) was followed by a trough below the critical 3-play 3.5 ypc mark (consecutive run stops by tOSU to kill a drive):
upload_2022-11-12_5-25-35.png

The spike-and-plunge pattern actually repeated itself throughout the game, making one wonder whether this was by design from Knowles? Nobody likes to give up yards, but it was a much better alternative than giving up points, especially in an extreme weather game where scoring was a premium. The way to lose a game to an inferior opponent in a low scoring affair is to give up fluky or "cheap" big-play touchdowns. So bend-don't-break would make sense here.

Or, I have another theory that I didn't bother to verify. Was the pattern a result of the DL substitutions? i.e. 1st string DL takes a break, big run from NW; 1st string DL comes back, put out fire. Probably too much work for a game against NW, but if any of you managed to chart the players on the field for each defensive play, this would be an interesting point to look for.
 
Upvote 0
Back
Top