Peppers at 10, which seems low.
Try as he might, Dave Brandon couldn't get the Huskies to acknowledge their football team is utterly irrelevant except for its proximity to New York.
How this works again:
- I put up a winnable prize that consists of a desirable good.
You guess the final scores of this weekend's designated game (football or hoops, depending on the season), and put it in the comments like so:
[Michigan Score]-[Opponent Score]. First person to post a particular score has it.
- If you got it right, we contact you. If not, go to (5)
- The desirable good arrives at the address you give us.
- Non-winners can acquire the same desirable good by trading currency for it.
Last Week's Game:
You, Khan vs. any hope that events which occur follow the events that preceded them, with the hopeful exception of any event from last Saturday.
And the Prize:
Sorry, Brian, but we couldn't get the rights to, while for the other the photographer was only too happy to oblige.
If you can read this you don’t need glasses:
One entry per user. First user to choose a set of scores wins, determined by the timestamp of your entry (for my ease I prefer if you don't post it as a reply to another person's score--if you do it won't help or hurt you). If nobody gets the score, this week's prize carries over to the following week's unless we beat Akron 28-24 when they had the ball at the Michigan 1 with time left in which case I am burning the prize. Deadline for entries is 24 hours before the start of the game (since I won't have time to pull them on gamedays). Those caught changing their scores after the game has started will be disqualified for life. MGoEmployees and Moderators--anyone else with moderator privileges--are exempt from winning because you could change your timestamp. If you choose the score that Brian published in the official preview and it actually ends up the final score, well, that would be pretty amazing because Brian picks scores like 29-11 all the time. We did not invent the algorithm. The algorithm consistently finds Jesus. The algorithm killed Jeeves. The algorithm is just a regional rivalry. The algorithm is banned in China. The algorithm is from Jersey. The algorithm constantly finds Jesus. This is not the algorithm. This is close.
Oh man, not again. Last week in this space, Akron's offense was represented by a tire fire, their defense a dumpster fire. Assumptions were made about the past having some bearing on the future, the Zips were dismissed as cannon fodder, and ... well, you saw how that turned out.
This week's opponent is UConn, which lost to Towson at home by 15 points in their first game, outgained by over 100 yards by an FCS opponent. After an oddly-timed bye week, the Huskies hosted Maryland last Saturday; once again, they lost the yardage battle by over 100 yards, and only a meaningless 75-yard TD pass with 22 seconds to play kept the score semi-respectable at 32-21. It could've been much, much worse:
- Maryland went for it on fourth-and-short twice in first quarter. Instead of spreading the field and either running to the outside or hitting a quick pass—both of which worked very well all game—they tried to attack the strength of UConn's defense and were stuffed on interior runs, failing both conversion attempts.
- The Terps drove all the way from their 17 down to UConn's 22 in the first quarter, only for an open screen pass to bounce off the hands of their running back and get intercepted by UConn's Taylor Mack. Maryland's three previous plays had gone for 26, 21, and 14 yards.
- By the end of the third quarter, Maryland would lose two fumbles by their running backs, one of which came after an easy ten-yard gain. The second led directly to a UConn field goal that would bring the Huskies within seven points.
When not shooting themselves in the foot, Maryland completely controlled the game, averaging 5.2 yards per rush and 9.9 yards per pass attempt. Take out the irrelevant late touchdown pass and UConn averaged 2.7 YPC (with five sacks removed!) and 6.1 YPA.
I promise to mock the Huskies as little as possible, however, after what went down last week. That said, I can only work with what I'm given, and for the second straight week what I'm given is, by all appearances, a really bad football team that lost to a I-AA squad.
Quarterback Chandler Whitmer (via The UConn Blog)
Spread, Pro-Style, or Hybrid? Spread, mostly. UConn operated either from the gun or an ace set; no fullback got a snap that I saw (I charted until Maryland took a 19-point lead midway through the fourth quarter). They had one snap from what Madden/NCAA deem the "pro" set—the QB under center with two backs split behind him.
Basketball on Grass or MANBALL? Basketball on grass. UConn ran a lot of inside zone and showed some zone read looks; none of this was very effective.
[Hit THE JUMP for the rest of the breakdown.]
FORMATION NOTES: Discontent with trying to file plays on which a tight end motio`ns inside of the tackle box but does not line up as a pure fullback as either "ace" or "I-Form," I've created new lingo. This is "Ace H":
Welcome it. It will be your good friend for a long time.
As the coaches mentioned, Akron spent much of the day in bear fronts. That means they folded linebackers inside of their ends at the LOS like so:
I noted this as 6-2 bear. When only one Akron player was folded inside it was 5-3 bear. (On almost all plausible run snaps Akron showed an eight-man front.)
PERSONNEL NOTES: OL was the usual, with Magnuson making his regular goal-line cameo. AJ Williams didn't play and Funchess went out late, paving the way for a lot of Jake Butt and the debut of Jordan Paskorz, runnin' routes with a broken hand.
Green got two snaps, I think, and Justice Hayes was briefly featured as a second back in a shotgun 2-back formation; all he did was pass block. Wideouts were as usual. If you squint maybe you can perceive Chesson getting more time than he has in the past.
Oh: again there was a small Norfleet package. Hopefully as the season goes along "Norfleet is on the field" starts being less than 90% "Norfleet is getting the ball."
[After THE JUMP: wha happen]
- Boo boo watch: Courtney Avery and AJ Williams are back at practice. This is not a drill.
- Boo boo watch part 2: Taylor Lewan didn't practice yesterday but will today. He's fine. Mario Ojemudia will be the most limited of the boo boo watchees. I don't know if he'll play.
- The offensive line is in an introspective phase. Changes might occur as early as this week. However, the bye week presents a much better opportunity to shake things up.
"Good practice yesterday. Thought we came out and competed very hard, which you expect every day. But I thought we physically were getting after each other, and we'll do the same thing today. We've got to play the run better, run the ball better, same old stuff you always hear, but it's the truth and it is what it is. I liked how we came out and competed with each other."
Noticeably different from last week?
"On a Tuesday? Probably a little bit."
A lot players said last Tuesday was lackluster. Can you tell that?
"They would know best if they felt that way. Maybe it's an individual thing, too."
Can you talk about UConn's defensive front?
"Yeah they're a big front. Not quite Notre Dame big in some ways, but they're a big front. Active in the linebackers. I think Smallwood is a guy who is their main bellcow when it comes to tackling and getting the ball on the ground. Just reading some of the comments Paul has made, I know they want to play better against the run also. I'm sure they've worked their tails off like we are."
Did Taylor Lewan practice?
"He didn't do anything yesterday. He did some alternate conditioning stuff, but he'll practice today. He's fine."
The weekly roundtable wonders about this whole "let's not get another Gardner" plan (that isn't the plan). Our depth chart:
|What, my Henson-ian athleticism isn't good enough for ya? [Upchurch]|
- Brian Cook: Field General!
- Seth Fisher: Legit 4.4 Speed!
- Ace Anbender: Top Recruiter!
- Heiko Yang: Huge Arm!
- Blue in South Bend: Super Accurate!
- Coach Brown: Reads Defenses!
- Mathlete: Academic All-American!
This one comes from the mailbag, a guy appropriately named "Dual Threat." If you notice a whole lot of positivity in it, it's because it was sent before last Saturday. I'll posit his question as he sent it:
My point of view is we should be recruiting more dual threat-ers. While Morris and Speight are no doubt going to be good pocket passers, leaving the running aspect of the position off the table leaves a huge hole in the offensive arsenal going forward.
I feel dual threat QBs are going to be the future of dominant college football programs going forward (I see Alabama as a current exception, not the norm in the future). Would you not sacrifice a bit of QB passing ability for a chunk of QB running ability to open up that attack dimension? Wouldn't you be foolish not to? Thoughts?
Brian: It's clear that all things being equal, Michigan's going to prefer advanced passers to guys who can glide for 35 yards without looking like they're moving particularly fast. And that's a little bit of a bummer to me, since a guy who can make people pay with his legs opens up many more possibilities in your offense.
What remains to be seen is whether Michigan is going to completely eschew athletic types that need some molding. Would they go the Charlie Weis route and recruit Terrelle Pryor as a wide receiver? I have nothing to base this on but I don't think so. If there's a Gardner or Pryor in the area, Michigan will probably go after them as hard as they would Morris.
"Okay. Anybody? Heiko, you don't have a question? You always have a question."
MGoIAmAboutToLookReallyStupidIn321: I do. I was just waiting for someone else to break the ice. Anyway, regarding the offensive line, a couple times during the game Akron lined up both of their defensive tackles in the A-gaps, and that sort of screwed up Jack Miller's blocking -- [MGoContext: Someone mentioned during the game that this happened. As it turns out, this may not have actually happened. MGoFail.]
"Well first of all, they didn't do that. They lined up in a double-eagle defense. Every time he blocks one direction he's covered the other direction, so the decision never should be bad, but it's all a matter of technique and fundamentals. On the first play of the game, he was lined up at nose guard and we just didn't get it covered. He stepped one direction and there was too much space between him and the left guard, and a guy leaked through. What they did in the game, they had done in other games. They didn't do it as much. They walked up on our weakside guard and was in essence a double-eagle or bear type defense, which wasn't anything new, it just wasn't run as often as we had seen on video. So we made some adjustments at halftime, handled it pretty good in the second half. We ran a little more directly at them the second half, a little less sideways, and that helped. That helped our running game."
[I recover! Eventually. Hit the jump.]