Posts Tagged ‘David Grimes’

You stay classy, Palo Alto.

Monday, November 26th, 2007

Crooked refs. Awful field conditions. An obnoxious stadium announcer. A dreadful marching band whose absurd antics amuse no one but themselves and their similarly drunk friends. A beautiful new facility gone to waste as one of America’s most esteemed universities presents a gameday experience matched only by the ineptitude of their football program. That’s right - another day, another dollar, another road trip to Stanford.

A few thoughts about the trip in general: as I said, the new Stanford stadium really is very nice. We had endzone seats in the upper tier, but the view was great - and right up above us there was a big grassy area where kids could play, and so my son really managed to enjoy himself. That’s why it’s such a shame that the other elements of gameday at Stanford are so embarrassingly horrible: at least when you used to go, you sat on splintered wooden benches in a dumpy stadium, so the rest of what was going on around you didn’t seem so bad.

And it was awful. The parking crew exercised no control over tailgaters taking up spaces the width of four cars to spread out their folding chairs, and the only way they managed to determine whether a lot was full was by directing a line of cars into it, having them drive around for ten minutes, and seeing whether they came out the other side. The pre-game “festivities” featured a mediocre cover band playing bad rock-and-roll, and then deciding to abandon their break so that they could drown out ND’s alumni marching band. The stadium announcer showed himself to be as classless as he was annoying when he twice referred to Jimmy Clausen as “Casey,” and also pretended to get him mixed up with Tom Zbikowski at one point. And the band - oh, the band. I understand that they’re having fun, but the stupid halftime shows really do nothing at all for the fans. No wonder the stadium was half-empty. Honestly, we felt embarrassed for Stanford University at any number of different junctures on Saturday afternoon.

Speaking of which, there was a football game as well:

  • Jimmy Clausen played very well - he completed 19 20 of his 32 passes for 196 225 yards and a touchdown. He also made some really nice moves to get away from would-be tacklers, though on some occasions he ran out of bounds for lost yardage instead of throwing the ball away. His downfield throws were a bit uneven, and the one play on which he was intercepted was a really bad decision. Altogether, though, it was a solid day for a true freshman quarterback who showed some nice improvement over the course of the year - now it’s time for him to hit the weight room, practice those deep routes, and soak up the rest of the playbook.
  • Duval Kamara - six receptions for 93 yards - had a really nice day catching the ball. It’s clear that he’s a tremendous talent, and there’s little doubt that he’ll be the #1 receiver on the team next year: the challenge is figuring out who else is going to catch it. George West was as invisible on Saturday as he has been for most of the season, Robby Parris saw the field sparingly, and David Grimes showed why he’s best suited to be a third option rather than a featured guy. Hopefully Will Yeatman and Mike Ragone have got the stuff to help replace John Carlson next year; I’d also look to see Michael Floyd see the field early and often, much as Kamara did this year.
  • Robert Hughes - 18 carries for 136 yards - had a spectacular game, as he became the first Notre Dame freshman to pass the century mark twice in a season since Autry Denson did it in back-to-back games in 1995. He could use a bit more speed, though, as both of his long carries really should have gone for scores. Armando Allen started off well, as he picked up 18 yards on his first three carries, but after that he started going backwards, and while the banged-up James Aldridge did manage to get into the game, he didn’t end up touching the ball. Asaph Schwapp had another dreadful day, as he gained only four yards on his three carries, fumbled the ball once, and did a less-than-stellar job of blocking. I really have trouble seeing why Charlie Weis bothers putting him on the field. Kudos to Travis Thomas, who made the most of what was (thankfully!) his last stand as a goalline back by punching his one carry into the end zone from a yard out, and to Junior Jabbie, who’s shaping up into a great situational back for third-down passing situations.
  • Once again, we saw a lot of Chris Stewart on the offensive line, as he pretty much switched off series-by-series with Paul Duncan at right tackle. And once again, the play along the offensive line, and in pass protection in particular, was pretty terrible: Clausen was sacked on five occasions and pressured pretty heavily on many others, and while the running game was effective, the Irish running backs netted only 3.15 yards per carry if we factor out Hughes’s two huge runs.
  • The defense played quite well, and in particular they did a much better job at containing the outside run than they had in weeks past. Ian Williams had six tackles in his second start at the nose guard position, and made a strong case for some heavy playing time or even a starting role next year. Darrin Walls got turned around on one or two plays but had a great game overall, Brian Smith played a nice game on the outside, and David Bruton was his usual athletic self. But missed tackles were still a significant problem, as was fatigue - Stanford possessed the ball for over 21 minutes in the second half, and you could see the Irish defenders tiring out.

At the end of the day, a win is a win, no matter how bad the opponent (and the venue). The Irish came out strong, played with emotion, and rebounded nicely from the things that set them back. But many of those back-setting things - in particular the three fumbles and the five sacks - were exactly the sorts of problems that have killed this squad all year long. A team that puts the ball on the carpet, and allows its opponents to do the same to their quarterback, with that kind of frequency is not a team that’s going to win many games. Maybe experience will cure all - but only time will tell.

Obviously there’s a lot to think about as we head from the season of our discontent to what will hopefully be the the looooongest offseason - 285 days to go! - the Fighting Irish will have to endure for quite some time. I’ll have plenty of “bigger picture”-type of thoughts in the days and weeks ahead. In the meantime, here’s to West Virginia and Mizzou in the MNC game!

Worst. Call. Ever.

Saturday, November 24th, 2007

Well, except perhaps for the phantom personal foul on Laws. I’ll have more on the game, and our trip to Palo Alto, later this weekend. For now, I’ll let a picture serve as a stand-in for what could very well be a thousand words:

(HT: KamaraPolice.)

[UPDATE: Check out Jeff Carroll's hysterical attempt to be diplomatic:

In the third quarter, the Irish again appeared to take the advantage, this time on a spectacular catch by junior wide receiver David Grimes. Grimes laid out parallel to the ground to snare a throw from quarterback Jimmy Clausen, and appeared to hang onto the football, holding it in the air as he slid across the turf.

However, officials decided upon review that the ball had touched the ground at some point during the catch, though it seemed difficult to detect on the replays shown on the ESPN broadcast.

"Appeared to hang on ... officials decided ... at some point ... seemed difficult to detect ..." LMAO. Well done, Jeff.]

[ANOTHER UPDATE: More here and here.]

[ONE LAST UPDATE: Here's home video of the incident, Zapruder Film-style:

The crowd reaction at the end pretty much gets it right.]

“Here we go again …”

Sunday, November 18th, 2007

A phantom personal foul after a long completion just outside the goal line. A missed field goal. An inefficient drive following a defensive stand, and then a late hit in punt coverage that gets flagged for 15 yards. These are the kinds of plays that have killed the Irish offense all year long, and for a while on Saturday they did the same.

Mistakes breed mistakes like rabbits in the Spring: a false start on fourth-and-two, a beautiful pass on fourth-and-17 that goes through the receiver’s hands, and suddenly you’re staring at 0-0 halftime score against one of the worst teams in college football.

And then, the momentum changes: the defense forces turnovers on consecutive drives, and each of them is turned quickly into seven points. It’s 14-0 at the half. You’ve got things back under control.

THAT’S the storyline that matters from Saturday’s game. Not the 400 yards of total offense, not the three touchdown passes by Jimmy Clausen, not even the explosive emergence of Robert Hughes or the always-gratifying Senior Day win. For once, this team showed a bit of resiliency: they didn’t let themselves get overwhelmed when things went badly. And say what you will about the quality of their opponent, but a 28-7 win (which could very well have been more like 42-0 if not for mental mistakes and bad calls) is a 28-7 win. Suddenly the future looks a lot brighter.

A few numbers to take away from the game:

  • Hughes (17 carries for 110 net yards, and a reception for another 13) obviously earned that game ball, though Armando Allen (nine rushes for 43 yards, and two receptions for 17) and James Aldridge (eight carries for 28 yards, plus a catch for another seven) had solid days as well. One of the biggest challenges facing Charlie Weis (or whoever is calling the plays) in 2008 will be finding a way to get enough carries for each of his three horsemen, together with throwing enough balls in the direction of Duval Kamara, George West, Robby Parris, and Golden Tate, not to mention David Grimes, Will Yeatman, Mike Ragone, and Michael Floyd. The talent is there; I imagine they’ll enjoy letting the spotlight fall where it may.
  • Clausen’s numbers (16-of-32 for 194 yards and three touchdowns) don’t speak to how well he played, especially given that at least four or five catchable balls were dropped. He also showed some good presence in the pocket, and did a good job of avoiding pressure, picking up 25 yards on his six scrambles.
  • The offensive line continued to show some signs of improvement, though pass protection was still a bit spotty at times. It was especially nice to see the screen game start to click.
  • Joe Brockington, David Bruton, Trevor Laws, and Darrin Walls each had a half-dozen tackles, and the defense on a whole played very well. This was the first time this year we saw freshmen Kerry Neal and Brian Smith both starting at the outside linebacker position, and they had quiet but solid days with three tackles a piece. Freshman Ian Williams getting his first start at the nose guard position, also played well, picking up three tackles and generally doing a good job of clogging up the middle.
  • The Irish possessed the ball for over 35 minutes, the first time all year they’ve really managed to control the clock - their previous high had been 32:02 against UCLA.

Finally, a few areas where a good deal of work is still needed:

  •  I’ve already mentioned the troubles in pass protection, as well as the dropped balls by the wide receivers. Clausen’s never going to be able to win those seven Heismans if his teammates don’t help him out.
  • While the Irish pass defense was largely sound, giving up only 138 total passing yards, there were still some blown coverages, and Duke could have picked up some more yardage if open receivers hadn’t been missed.
  • J.J. Jansen’s long-snapping was iffy once again, though Eric Maust made a remarkable play to bail him out and get the punt away under pressure.
  • Notre Dame continues to lack any semblance of consistency in the kicking game, as Brandon Walker missed his lone field goal attempt, from 30 yards out. It may have had something to do with the weather, but those are the kind of kicks you’ve got to make. It will be a shame if the Irish continue to cripple themselves by having to go for broke on fourth down instead of putting points on the board the cheap way.
  • Lastly, penalties were a problem once again: the Irish were whistled eleven times for 103 yards, after committing only nine penalties in their previous three games combined.

All in all, a solid day against an undermanned opponent. There should be plenty more of those in the future as this team continues to develop.

Thought experiment

Monday, November 12th, 2007

From a commenter, identified as “Hal,” on a post at Blue-Gray Sky:

I’d like to do an experiment:

Take a team like Michigan and put them in ND’s shoes. Remove Hart and Henne for the whole season, and replace them with Frosh and Sophs. Take away Manningham and replace him with a Frosh. Then, remove a couple of O-line starters. Lastly, take the junior and senior classes and remove a dozen of the most talented guys, including those who might fill those holes in the O-line. Throw in a bit more inexperience at some key positions on D.

What’s Michigan’s record now? I’d say 3-8, 4-7.

I’m not picking on Michigan, and I’m not saying we should be losing to Navy and Air Force. I’m just saying that there are some pretty serious extenuating circumstances going on here. This is hard to stomach, but it’s not inexplicable.

It’s not time to panic.

At this point in the season I’m about as despondent as one can be about the future, and pretty much fed up with excuse-making, but something about this really speaks to me. A few other variables not mentioned here include:

  • Playing an insanely difficult schedule, composed almost entirely of away games, to start the season.
  • Having your best quarterback trying to recover from off-season elbow surgery, with your top two tailbacks coming off of injuries as well.
  • Seeing lots of key players (Aldridge, Grimes, Wenger, Kuntz, Bruton, etc.) go down with injuries at various points during the season itself.
  • Bringing in a brand-new defensive coordinator who’s trying to implement a new scheme using personnel recruited for the old one.

Add to this distractions like the Demetrius Jones situation and the (rumored, though perfectly predictable) tensions between the upper and lower classes, and you’ve got a recipe for a season that starts badly and quickly snowballs into mind-numbing awfulness. No doubt the coaching staff has failed MISERABLY in getting things back on track, but that doesn’t change the fact that the circumstances they’re dealing with have been, as Hal says, “serious[ly] extenuating.”

THAT’S why Charlie Weis will be back in 2008, this year’s suckitude notwithstanding. And it’s also why I’m done complaining about 2007 … unless we lose to Duke, that is.

Taking Stock, Part I: 19 reasons why Notre Dame’s offense has sucked so badly in 2007

Tuesday, October 30th, 2007

I don’t know about you, but it feels like the middle of the season to me: Fall Break and the bye week are behind us, the complexion of the schedule has changed dramatically, and we’ve hit what can only be described as rock bottom after the Loss that Shall Not Be Discussed. So it’s in this spirit that the Irish Roundup brings you “Taking Stock,” a three-part series (wow, doesn’t that sound fancy?) evaluating the 2007 season up to this point and looking ahead to its remainder.

Up first, a detailed evaluation of why the Notre Dame offense has been so dreadful this year. We all know the statistics, so I’m not even going to bother listing them again: the question I’m going focus on here is “Why?” rather than “How bad?” Here are what I - with the invaluable help of the rest of the IrishEnvy crew - take to be the nineteen biggest problems, in inverse order of importance:

19) Too much hype: No doubt Charlie Weis did the right thing by refusing to throw his players under the bus by calling 2007 a “rebuilding” year, but did we all have to believe him? Nearly all ND fans had the Irish winning at least three of these first eight games – a clearly unreasonable expectation. The team’s current 1-7 record would be completely satisfactory if they’d played hard, scrappy football and shown improvement from week to week, but the burden of everyone’s high hopes can’t have been a help in making that happen.

18) Scheduling: A calendar front-loaded with top-notch opponents, with all of the easy games at the end of the year. Four of the first six games played on the road. A bye week after USC (though having extra time to prepare for Navy never hurts). No doubt it’s difficult to put together ND’s schedule, but this year’s version was just atrocious.

17) Recruiting: Many are going to wonder why this isn’t higher on the list. The reason for that is that the talent gap between the Irish and their opponents doesn’t even begin to account for the awfulness of their offensive (ha!) game. No doubt the paucity of upperclass talent feeds into many of the more serious problems in a major way, but in itself it’s only the tip of a very large iceberg.

16) Too much shuffling of the depth chart: I’ve already been over this in some detail, and I still stand by the analysis I gave there, namely that while many of these shifts have been due to injuries or other unpredictable things, some – in particular taking so long to settle on James Aldridge as the #1 tailback, and even then giving too many carries to other players – were clearly mistakes.

15) Distractions: The obvious example of this is Demetrius Jones not showing up for the team bus to Michigan, after which the Irish played what was clearly their worst, and least-inspired, game of the season. But there have been other cases as well, such as Derrell Hand’s arrest, the ongoing quarterback controversy, the departures of Konrad Reuland and Matt Carufel, the rumors of dissension among Irish players, and so on. These are not the sorts of things that help a young team get over their struggles.

14) Penalties: Obviously there are some – Mike Turkovich’s touchdown-negating hold against BC, for one – that stick in the forefront of your mind, but the fact is that false starts, holding calls, and other offensive penalties have been a huge problem all year long, regularly putting the offense in a position where it has to pick up huge yardage to move the chains. Thankfully there were far fewer such mistakes against USC, so maybe that’s the beginning of a trend.

13) Injuries: Aldridge, David Grimes, Matt Romine, and Dan Wenger have all missed significant time with injuries, and Jimmy Clausen and Golden Tate have been banged up as well. For a team as thin as this one is, having front-line players like these get injured is obviously a big problem, and keeps the squad from developing a consistent rhythm.

12) Play-calling: Once again, this is a factor that a lot of people are going to want to put a lot higher, though see my lengthy post from after the BC game for why I thought that in that case at least, this issue was WAY overblown. There’s no doubt, though, that there have been some huge mistakes made in this department: the obvious examples are the crazy schemes employed at the starts of the games against Georgia Tech and Michigan, though there are others as well. This team has to do more than just develop its “bread and butter” plays in practice; it has to run them on the field as well. Of course, that’s hard to do when players consistently fail to execute the plays you’ve called.

11) Inexperience: You could try to lump this in with recruiting, but it’s really a different issue, since it’s meant to pick out the fact that many of even the more “veteran” players – Turkovich, Paul Duncan, Evan Sharpley – saw very little playing time before this year, and so aren’t able to do as much as one would hope to bring the younger players along. I’ve been told that last year, Bob Morton and the other offensive linemen were telling Sam Young what to do on almost every play – this year, there’s only one lineman with more than one year of experience other his belt.

10) A rift within the team itself: I’m putting this right in the middle of the list only because I obviously don’t know if the various rumors that have swirled around are true. But the fact is that there have been some pretty clear signs – both on the field and off – that this squad hasn’t really come together well. Some of this is natural, as younger players and veterans compete for playing time, but if it’s as bad as some have said it is, then its ramifications may be extensive indeed.

9) Lack of leadership: This isn’t just about the veterans; underclassmen can be leaders as well. Some of this is the result of the “musical chairs” that has been played with the depth chart, whether due to injuries, poor personnel decisions, or surprising performances by players (whether of the good variety or the bad). No matter what the cause, though, not having players who can bring everyone together in the huddle or on the sidelines and focus their energies on the task at hand is going to be a huge problem for any team.

8) Failure to execute the “finesse” plays: What I have in mind here are the dropped passes or missed receivers that we’ve seen so often this year. In countless cases, a player has been open and either the ball has gotten there and he’s failed to catch it, or the ball has been thrown over his head or at his feet. Mistakes like this stall an offense like nothing else, except perhaps for …

7, 6) Poor pass- and run-blocking: I can’t figure out which of these to put first, since each feeds into the other in countless ways. But it’s important to emphasize that the problems here haven’t just been with the offensive line: whether it’s tailbacks whiffing or getting run over on pass protection, fullbacks failing to open up holes in the running game, or wide receivers missing blocks downfield, there’s no getting around the fact that the blocking on this team has been atrocious at every level.

5) Lousy position coaching: When you have a team composed almost solely of either young players recently out of high school and “veterans” who’ve barely played a down, what you need is a group of assistant coaches able to teach them the proverbial fundamentals. So far this year, there’s been little evidence that that’s happened, and the lack of week-to-week progress suggests significant deficiencies in the sort of training these players are receiving.

4) Practice routines: The influence that having had contact-free practices for so much of the season and pre-season has had on this team probably can’t be overstated: once again, many of these players are new to college football, and they just don’t know what real “game speed” looks (and feels) like. But there have been other problems as well: to give just one example, there is no doubt that the decision to develop overly creative plays rather than taking a “building-blocks” approach did a great deal to set this team back and prevent real progress in the early weeks.

3) Tentative play: The USC game was a paradigm of the tendency among offensive players to look like they’re more concerned with avoiding mistakes than with doing something right. Whether it’s the overly-complicated character of the offense they’re running, the shock of game speed, the burden of high expectations and the consequent fear of criticism, or whatever, there’s no doubt that many of this offense’s failures – dropped passes, missed blocks, inability to hit holes in the running game, and so on – can be attributed to an all-around tentativeness.

2) The “snowball” effect: With the exception of the post-halftime spurts against Purdue and BC, one steady tendency for this team has been that when things go bad, they get worse. The offense has shown very little resiliency, whether to their own mistakes or to those of the defense and special teams, and we’ve often seen the proverbial wheels fall off at the first sign of difficulty (the Michigan State game was the paradigm instance of this). Once again, this can be traced to many of the other problems above, but it’s clearly a place where this team’s many defects have often come to a head.

1) Charlie Weis: Sorry coach, but the buck stops with you. I’m going to have more to say about this in a post tomorrow, but for now just let me say that I think Weis has done a simply terrible job coaching this squad, and while I don’t think this one season is sufficient to show that he’s the “worst coach in the universe,” I also don’t think that the old “learning curve” excuse is good enough. In my mind, there’s reason to think that Weis is a good-to-great coach for seasoned veterans, and an outright terrible one for young players. If this is right, then the key question is whether he can transition this group from the latter category to the former without doing irreparable harm to them – I’ll have much more to say about this tomorrow and Thursday in Parts II and III of this series.

Trojans inspect playing field, continue to whine

Saturday, October 20th, 2007

I know I promised an injury update for today’s game, but this article in the LA Times was just too funny to let pass. So instead of the usual detailed breakdown (quick version: Aldridge won’t play, Grimes has reportedly looked a bit hobbled in practice, Wenger is back, no word that I’ve seen on Crum; and see here for the veritable litany of busted Trojans), I submit to you: The Victors, Two Years Later.

SOUTH BEND, Ind. — Most of USC’s players strolled casually onto the field at Notre Dame Stadium on Friday for the Trojans’ walk-through before today’s game against the Fighting Irish.

But Desmond Reed never broke stride as he sprinted to the far end zone on grass significantly shorter and more manicured than it was in 2005, when Reed suffered torn right knee ligaments and nerve damage while turning to field a ball on a kickoff return. [Ed: TURNING to field it, mind you - on which see more below.]

Reed said last year he thought the grass was grown long intentionally to slow down the Trojans and that it caused his injury.

“They actually cut it,” defensive line coach Dave Watson said.

Said Dennis Slutak, USC’s director of football operations: “You could actually hit a golf ball out of this.” [Ed: Apparently Slutak isn't much of a golfer. Somebody want to get Ty Willingham on the phone to help him out?]

That’s right, folks. Two years after winning - WINNING!! - at Notre Dame stadium in a game that ended with a series of questionable calls and non-calls which Charlie Weis and (so far as I can recall) the rest of the Irish chose not to question, and after which Weis took his son into the SC locker room to congratulate the players and coaches on their victory, following which the Trojans won out the rest of the season on their way to the BCS national title game, their players and staff are STILL complaining about the length of the grass back on October 15, 2005.

Nor are their gripes limited to Irish fields of lore. Pete Carroll, for one, is already gearing up to make excuses for this year’s game:

… on Friday, after walking the field, Carroll said he was surprised it did not have a uniform feel.

“I don’t understand why it’s like that, I mean who plays here?” he said. “They sharing it with a local JC or something?”

It’s hard not to take this as evidence that either (1) Carroll can’t read or understand English, or (2) he’s a whiny scumbag who’s unwilling to respect what an opposing coach has to say about the state of his own playing field. Otherwise, the Poodle’s remarks might have taken account of this, from Weis’s Tuesday press conference:

this is the Midwest, and we’re going to play five games in a row at home. That’s where we are right now. Now, fortunately this is only game two. But it isn’t like our grass grows like we’re living in the south. It is what it is. It’s patchy and it’s not the same as playing on Bermuda grass in the south. It isn’t like we were playing on field turf; I don’t think that would go over too well in Notre Dame tradition. It’s grass, it’s mid October, it’s not as perfect as it would be earlier in the year. That’s just the way it is.

That’s right, Petey. It’s SOUTH BEND FRICKING INDIANA. It’s either too hot or too cold or too sunny or too rainy or too damn snowy about, oh, 257 days a year, and so the grass don’t grow quite like it does in sunny LA. And no, the only junior college with which the Irish are sharing their field is the one whose football team you coach. (Zing!)

Now, you might think that Reed’s gripe is a bit more legitimate, given the seriousness of the injury he suffered against the Irish two years ago. But if you did think that, then you’d be failing to take into account the excellent detective work that the guys at the IRT did before last year’s SC game:

How many of these pundits have actually gone back to watch the play which ended Reed’s season? Not many. If they did, they would clearly see that this was a player way out of position in the first place. It is our assertion that the grass was not the culprit here, but a player out of position.

Now, with the help of photographic evidence obtained through NBC we can reconstruct the play and prove that Reed is to blame for the injury. Not the grass.

Reed1.jpeg

This is the first screenshot from the kickoff where Reed was injured. This is the first moment the Reed enters the screen. He is the cut off figure on the right hand side of the photo near Notre Dame’s 14 yard line.

Reed2.jpeg

Here is Reed running back to field the kickoff between the 8 and 9 yard lines.

Reed3.jpeg

At the five yard line Reed makes a weird turn to try and field the ball flying over his head. This is where he goes down.

Reed4.jpeg

Here is Reed laying on the 2 yard line as the ball sails over his head. Clearly, if Reed was positioned to field the kick-off on the goal line, there would be no discussion of tall grass and Weis’ desire to injure and maim opposing players.

You make the call. Here at the Roundup, though, the company position is that the Trojans are a bunch of whiny bitches, and they’re going to get their asses handed to them this afternoon, no matter what the field may look like.

Go Irish, dammit.

Personnel notes

Wednesday, October 17th, 2007

With the Southern Cal (yeah, that’s what I said) game just a few days away, there’s a bunch of news to cover regarding depth chart moves, injury updates, and the like. I’m going to run down the highlights position-by-position, but for the quick version, see the summary below:

  • Running backs: First-string tailback James Aldridge suffered a high ankle sprain against BC and is officially listed as “doubtful” for Saturday’s game, and Michael Rothstein quotes Charlie Weis as saying that while Aldridge “intends to play this week,” “the odds of that happening aren’t that high.” Given that all season even players who have been described as “probable,” “game-time decisions,” or even “ready to go” haven’t ended up playing much if at all (think David Grimes, Dan Wenger, and Maurice Crum last week), I’d say there’s just about no chance that Aldridge ends up seeing the field, which is really bad news for the Irish. With the injury to Aldridge, former co-#2’s Travis Thomas, Armando Allen, Junior Jabbie, and Robert Hughes are now listed as co-#1’s on the new depth chart, with Aldridge’s name in italics. Here’s what Weis said about this in his Tuesday press conference: “Well, I think what we would not do this week, since this is USC, is just throw Robert (Hughes) in and Armando (Allen) in there right off the bat. I think that we would go a little heavier with Travis (Thomas) being involved in this mix, too, more than he has this year. I think that that would be part of that combination. I’m not saying by committee, but I think that he would probably take off some of the pressure of James, and obviously Robert and Armando would be much more involved.”
  • Wide receivers: David Grimes didn’t play against BC, but Weis said in his Tuesday presser that it sounds like Grimes has “a legitimate chance of playing” in the Southern Cal game: he “was close to being able to go on Saturday (vs. Boston College), but it’s always tough when you haven’t practiced all week long to try to go when you haven’t had a meaningful rep in practice.” Meanwhile, as Rothstein notes in his excellent breakdown of this week’s depth chart changes, Grimes is now listed behind Robby Parris at the “Z” receiver slot, and fellow former #1 George West is now behind freshman Duval Kamara at the “X” position. Golden Tate, meanwhile, is still listed as third string for the “Z” slot, and Weis made a helpful clarification in his presser as to why Tate didn’t play much on offense against BC, saying that it wasn’t because of injury: “That was because we were going to play a significant amount of no huddle in the game, and in the no huddle our outside receivers do not flip flop positions, so they need to know both outside positions both as the weak side receiver and the strong side receiver. And really at his experience level, you want him to be able to play one position. Not (put him in a position) where he has to know both the X and the F and know both right and left. That was not the type of game that you want a guy with very little experience to be involved in.”
  • Offensive line: As I noted earlier, Dan Wenger sat out his fourth straight game last week with a leg injury. But when asked about Wenger’s health on Tuesday, Weis was unambiguous (for once): “He’s back. I think I would list Tom (Bemenderfer) down there [as the backup at right guard], but I think if I needed a backup inside, Danny (Wenger) would be the first backup inside at all three positions. I know I only list him at one. I list him (Wenger) as the backup center but he’d probably go in first at right guard and he’d probably go in first at left guard, as well.” On the new depth chart, Wenger is in fact listed as the backup to both John Sullivan at center and Eric Olsen at right guard, with Bemenderfer listed as Mike Turkovich’s backup at the left guard slot. Weis also noted that Chris Stewart, who saw the first game action of his career against BC, has been working both at right tackle and at right guard in practice, though the former position is his primary responsibility. Finally, Rothstein notes that Matt Romine, who’s missed several games with a right elbow injury, was wearing a “slightly less bulky” brace on Tuesday. He’s still probably a ways away from being back, though.
  • Linebackers: I also noted that Maurice Crum sat out the BC game, because of a turf toe injury he suffered against UCLA. Weis described Crum, like Grimes, as having a “legitimate chance” of playing against SC, noting that he “is walking without a limp this week, and that’s a good thing.” But both Rothstein and Ben Ford note in their reports from Tuesday’s practice that Crum looked a bit slow, so it’s perhaps reasonable to think that his status may be up in the air. The new depth chart, meanwhile, lists Anthony Vernaglia, who had been a starter at outside linebacker until last week but saw time at ILB against UCLA as well as BC, as Crum’s backup, with freshman Brian Smith taking over Vernaglia’s position from last week as the backup to John Ryan, and Morrice Richardson now in Smith’s old position as the backup to Kerry Neal.
  • Cornerbacks: Thankfully there’s no injury news to report here, but there has been a little bit of shifting on the depth chart: Darrin Walls is now listed as a co-#1 with Ambrose Wooden at the left cornerback spot, and at RCB, former tailback Munir Prince - who as I noted before the BC game has been seeing more playing time recently - is now listed as a co-#2 with Raeshon McNeil, behind Terrail Lambert.

Okay, that’s all. Here’s a quick summary for anyone who might have been overwhelmed by all that text:

  • James Aldridge is injured and probably won’t play against Southern Cal. Travis Thomas will play a key role backing him up, together with freshmen Robert Hughes and Armando Allen.
  • David Grimes will probably be back for the SC game, though he is now listed at second string behind Robby Parris. George West has also been bumped to second string, by freshman Duval Kamara. Golden Tate is not injured.
  • Dan Wenger is healthy and back on the offensive line, listed as a backup at two positions (center and right guard). Tom Bemenderfer is the backup at the other guard position.
  • Maurice Crum has reportedly looked a little slow in practice, so it’s fair to say that his status for Saturday may be uncertain. Anthony Vernaglia is now listed as his backup, with Brian Smith taking over Vernaglia’s spot from last week as the backup to John Ryan and Morrice Richardson taking Smith’s spot behind Kerry Neal.
  • Ambrose Wooden is now listed as a co-#1 with Darrin Walls at one cornerback slot, and Munir Prince as the co-#2 with Raeshon McNeil at the other.

That’s it! I’ll be back tomorrow with some analysis of the team’s depth along the offensive line, pre- and post- the departure of Matt Carufel.

It’s the execution, stupid.

Tuesday, October 16th, 2007

Amidst all the armchair analysis of Saturday’s loss to Boston College, many excellent points have been raised about what the Irish are and - especially - aren’t doing right: offensive line and quarterback play on the bad end; the all-around liveliness of the defense and the play of individual standouts like Trevor Laws, Brian Smith, and Darrin Walls on the good. But one point that many people, both on the IrishEnvy boards and elsewhere, have kept coming back to as an area that has hurt the Irish is Charlie Weis’s play-calling. I’ve said in many little discussions already that I think this argument is silly, but I thought it was worth writing a longer post detailing exactly why I think this.

Let me preface my argument by saying that I’m well aware that I know absolutely nothing about play-calling. Heck, I don’t even play Madden. But given the specific sort of argument I’m going to make here, I think that’s a good thing: I’m not going to sit here and tell a Super Bowl-winning offensive coordinator how to do his job; instead, I’m going to show you exactly how the plays that Weis called against BC regularly put the Irish in a position to convert simple first-downs and so move the ball down the field. My focus, in other words, will be (once again) on specific boneheaded mistakes rather than abstract generalities.

To start, let’s look at OCDomer’s breakdown of Saturday’s offensive drives:

  1. 6 Plays, 3 yards, punt.
  2. 5 plays, 16 yards, punt.
  3. 3 plays, 9 yards, punt.
  4. 3 plays, 9 yards, punt.
  5. 10 plays, 22 yards, ball turned over on downs when punter’s knee touches ground while fielding low snap.
  6. 5 plays, 9 yards, Clausen pass intercepted.
  7. 1 play, 0 yards, Clausen pass intercepted.
  8. 7 plays, 79 yards, TD pass from Sharpley to Parris.
  9. 3 plays, 7 yards, punt.
  10. 6 plays, 16 yards, punt.
  11. 6 plays, 15 yards, missed 41 yd FG attempt.
  12. 11 plays, 53 yards, ball turned over on downs.
  13. 4 plays, 0 yards, ball turned over on downs.
  14. 1 play -1 yard, game over.

It’s certainly easy to look at that drive chart, together with a box score that shows that the Irish had only 222 total yards to BC’s 459 (not to mention the fact that ND is still ranked 111th or worse in every major (andminor“) offensive category) and conclude that coaching is at fault, and - as I’ll argue shortly - I think you’d be quite right to do that. But that doesn’t mean the fault is with PLAY-CALLING. Here’s a breakdown of what brought those drives to a halt (some of which is noted by OCDomer):

  1. 6 Plays, 3 yards, punt. [Holding by Young forces 2nd-and-20.]
  2. 5 plays, 16 yards, punt. [Clausen fails to hit open Parris in near field on two consecutive throws.]
  3. 3 plays, 9 yards, punt. [Allen fails to convert on third and three.]
  4. 3 plays, 9 yards, punt. [Hughes fails to convert on third and one.]
  5. 10 plays, 22 yards, ball turned over on downs when punter’s knee touches ground while fielding low snap. [Olsen false starts on 2nd-and-10; Clausen under huge pressure next two plays.]
  6. 5 plays, 9 yards, Clausen pass intercepted. [Drive starts with 1:19 on clock. Young called for holding on 1st-and-10.]
  7. 1 play, 0 yards, Clausen pass intercepted. [Dangerous pass by Clausen bounces off Carlson's hands and is picked off.]
  8. 7 plays, 79 yards, TD pass from Sharpley to Parris.
  9. 3 plays, 7 yards, punt. [Kamara drops a first-down throw on 3rd-and-3.]
  10. 6 plays, 16 yards, punt. [Sharpley misses on two consecutive downfield passes to Parris.]
  11. 6 plays, 15 yards, missed 41 yd FG attempt. [Turkovich whistled for holding on 1st-and-10; Duncan burned badly to give up a sack; Walker misses FG attempt.]
  12. 11 plays, 53 yards, ball turned over on downs. [Turkovich called for holding on 4th-and-1 TD throw.]
  13. 4 plays, 0 yards, ball turned over on downs. [Parris drops a downfield throw by Sharpley; Sharpley throws the ball to nobody on 4th-and-10.]
  14. 1 play -1 yard, game over. [Kneel-down to run out clock.]

So there you go. Out of twelve failed offensive drives (obviously the last one doesn’t count), the Irish had five that were handicapped by penalties along the offensive line, two that ended on failures to convert short yardage on third down, two that each involved a pair of poor throws to open receivers, and two others that ended when third-down throws were dropped by wide receivers. Put that together and you get six of twelve drives that would have been sustained if not for straightforward offensive incompetence (dropped or mis-thrown passes and an inability to convert short yardage) and five more where the offense had to face extra-long yardage situations because of penalties. That’s eleven of twelve failed drives (the one that is left out here is the one that started and ended with Clausen’s second interception) grinding to a halt because of nothing but old-fashioned on-field ineptitude.

So here’s my question: how is ANY of this the result of the plays that were called? It seems to me - and perhaps someone who knows more about football can show me where this is wrong - that all a coach can do in the play-calling department is put his team in a position to convert one first down at a time so that they can move on down the field. This is going to be immensely hard to do when the offensive line moves your team backwards rather than forwards with dumb penalties, and it is also going to be hard to do when you call plays that should be good for first downs and your team FAILS TO EXECUTE THOSE PLAYS. So far as I can tell, not even ONE of ND’s failed drives on Saturday is attributable to Weis having called the wrong plays (whether it was not running enough, not passing enough, not passing the ball downfield enough, and so on and so forth): instead, in every case where there weren’t penalties along the o-line to move the team backwards (and indeed in some of those cases, too), the offense had a chance to convert a third down and extend their drives, a play was called on which they could clearly have done just that, and they failed to do their job. It is simply beyond me how this loss could be ascribed to the plays that were called rather than what was done with them once the huddle was broken.

None of this is to say that Weis’s play-calling has been beyond reproach in PREVIOUS weeks; I no longer have my notes on them, but I sincerely doubt you could make this same sort of argument (at least with this same force) in those cases. (The Georgia Tech and Michigan games are especially striking examples of goofy scheming.) Nor - as I’ve already mentioned - is it to say that he’s beyond criticism for Saturday’s loss. In fact, I can think offhand of at least ten other things for which Weis deserves a lot of flack:

  1. An offensive line that can’t block.
  2. The fact that the (in many case most veteran) members of said line continually commit dumb penalties.
  3. A team that is unable to convert in short yardage situations.
  4. A pair of quarterbacks who were barely above 30% passing on the day.
  5. A veritable smörgåsbord of dropped passes by the wide receivers.
  6. The fact that his team seems regularly to come out flat in big games.
  7. The fact that his practice routines didn’t get his players ready for “game speed.”
  8. The way the wheels have tended to fall off for this year’s team as soon as they’ve faced the tiniest bit of adversity.
  9. The fact that many of the members of his coaching staff don’t seem to be able to get their jobs done.
  10. The fact that the Irish are 1-6 this year (and 1-8 in their last nine games).

All of these things are, in part at least, the fault of the head coach, and many of them bring out the sorts of problems that doomed the Irish against BC. Weis DESERVES to be blamed, in other words, for the way his team has failed to execute: but last Saturday at least, the plays he called would have enabled his team to move down the field if they’d managed to do just that (i.e., execute).

(While we’re at it, let me point out a few things that handicapped the Irish against BC but were NOT Weis’s fault:

  1. The fact that his #1 tailback (Aldridge) left the game with an injury after getting only five carries.
  2. The fact that his #1 wide receiver (Grimes), his top middle linebacker (Crum), and a starting offensive lineman (Wenger) as well as a backup (Romine) all weren’t able to play because of injury.
  3. The fact that that was one of the worst-officiated football games I’ve ever seen.
  4. The fact that BC has sold its soul to the devil in exchange for theological liberalism and a win-streak against the Irish.
  5. Ty Willingham’s recruiting (yes, that old hat).

Again, I’m certainly not saying Weis is blameless - on that, see the above. I’m just saying we’ve got to keep the whole picture in mind.)

Whew. That was a long post for such a silly argument. But in many ways I think the complaints about the plays that were called on Saturday illustrate people’s inability to look realistically at a game and diagnose what actually went wrong as opposed to trotting out the same old gripes week-in, week-out. There is a LOT that is wrong with this team, and a LOT of that is arguably the fault of Charlie Weis. Foremost among these problems is a failure to move the ball on offense - but so far as I can tell, the chief problem against BC wasn’t on the sidelines. It was on the field.

Gameday news and notes (ND vs. BC)

Saturday, October 13th, 2007

Here are few updates on the Irish depth chart, and the health of ND’s various injured players, heading into this afternoon’s game against Boston College.

* * *

It was reported on the Web Thursday night, and yesterday the Chicago Tribune picked the story up: sophomore offensive lineman Matt Carufel, who started the past three games at right guard after classmate Dan Wenger went down with an injury and was listed to start again against Boston College, has been excused from the team for undisclosed personal reasons and will miss today’s game:

Irish guard Matt Carufel, who started the last three games, has returned home to Minnesota and is expected to decide on his future at Notre Dame by Sunday, the Tribune has learned.

Carufel has been excused from practices this week due to “personal reasons.” On Friday, Carufel was at his former high school in St. Paul, Cretin-Derham Hall, spoke extensively with assistant coach Andy Bishoff, and indicated that he may not return to the Irish.

“He’s struggling with if he’s going to stick around there or not,” Bishoff told the Tribune. “He just doesn’t know if he fit at Notre Dame like he thought he would.”

Carufel also could return to Notre Dame to finish out the semester. If Carufel decides not to return to the Irish, Bishoff said Minnesota and Iowa are two schools likely to be at the top of the list of potential destinations.

Apparently Carufel was absent from practice on Wednesday, Thursday, and Friday. His departure, together with the elbow injury (I am told it involves torn ligaments) that is going to keep freshman Matt Romine out for the foreseeable future and the obvious questions of whether Wenger’s leg is 100% healed, suddenly leaves the Irish almost paper-thin along the offensive line. Carufel’s backup on this week’s official depth chart (which I’ve already discussed at some length here) is fellow sophomore Eric Olsen, who had previously been listed behind Mike Turkovich on the other side of the line at left guard, and who has played in ever game except the loss to Michigan. Olsen saw the field by far the most of any of the backup offensive linemen through the first five games, so hopefully he’ll be ready to play.

But after that, the rest of the second string o-line consists of freshman Taylor Dever behind Sam Young at left tackle, junior transfer Thomas Bemenderfer behind Turkovich at left guard, Wenger behind fifth-year senior John Sullivan at center, and sophomore Chris Stewart behind Paul Duncan at right tackle. If Wenger is ready to go, it’s obviously not a stretch to see him splitting minutes with Olsen in Carufel’s place, since Sullivan essentially never leaves the field. Stewart and Dever, meanwhile, haven’t gotten into any games yet this year.

(It’s perhaps worth noting that the Notre Dame depth chart published in the South Bend Tribune this morning lists Stewart as the starter at right guard, with Olsen listed as backing up both Stewart and left guard Turkovich, and Bemenderfer as the backup center to Sullivan. Wenger, meanwhile, is completely absent from that chart, though Romine is listed as Duncan’s backup at right tackle. It’s hard to believe this chart is accurate, though, since there are also several other funny things about it, including Eric Maust listed ahead of Geoff Price as the team’s punter, and Anthony Vernaglia absent from the chart altogether.)

So obviously we’re not going to know for sure who’s going to play where until the game is underway, but I’d be surprised if what we see at the right guard position doesn’t primarily involve Olsen and/or Wenger, depending especially on the health of the latter (on which see below).

* * *

Up next, a couple of quick injury updates:

  • David Grimes, who ended up not dressing for the UCLA game because of an ankle injury suffered against Purdue, was back in practice this week, albeit with a heavily taped ankle. Watching Grimes on Wednesday, Ben Ford thought that he was “still having a little bit of trouble with the initial burst and explosion when he makes a break from a standing position.” Charlie Weis was quoted in Eric Hansen’s excellent column in today’s SBTrib as saying that Grimes hadn’t participated in any cutting drills this week, and that he would be a game-time decision, but that he “still doesn’t look full speed to me … If he doesn’t look close to full speed, then I just won’t play him.” My gut here says that we don’t see Grimes on the field today.
  • Meanwhile, I haven’t seen any reports of how Dan Wenger looked in practice this week, but an article from Wednesday’s SBTrib has this little nugget: “We’re finally getting him back on a more full-speed basis this week,” Weis said of Wenger. “He’s not automatically going to get thrown (into the right guard mix). He’s going to have to earn his way back out there.” It could be, in other words, is that the reason Wenger was made the backup to Sullivan on the depth chart for this week is that he’s not fully healthy, and less will be expected of him there because of how little Sullivan comes out of the game. But once again, I wouldn’t read into the fact that Wenger isn’t listed in the SBT depth chart, since they list Romine as a back-up, and Weis has said that he’s at least a few weeks away from returning.

* * *

Finally, one more personnel-related note. Pat at BGS noted earlier this week that sophomore Munir Prince, who was recruited as a tailback but made the switch to cornerback in the off-season, saw some playing time on defense against UCLA. A question in Michael Rothstein’s mailbag from this week picked up on this point:

I noticed late in the UCLA game when the Irish were on defense, Darrin Walls nor Raeshon McNeil were on the field. Is this because the Irish were running a prevent zone and those guys match up better in man-to-man, or did the coaches feel better with the more experienced dime lineup of (Terrail) Lambert, (Leo) Ferrine, (Ambrose) Wooden, (David) Bruton, Zibby but then there was (Munir) Prince, what gives? Thanks.
-Pete McLoughlin

Pete,
Honestly, we’re not sure. From the television view we had, we didn’t even notice the shift in this package and who was in. What we can tell you is we noticed Prince in the game a lot. It shows more than anything that the sophomore is finally adjusted to his move to cornerback. As for that package, we’ll take a good look this week when we’re back on site for games.

Anyway, just thought that was worth noting. That’s great for Munir, and hopefully he’ll continue to get on the field and play well the rest of the season.

[UPDATE: The always-insightful OCDomer has this to say, over at NDLNA:

I noticed Munir in at corner for stretches against UCLA. It seemed he was man-up on UCLA's best wide-out. Coach Weis has always said Munir was very fast. If he has developed his footwork at DB to the point that he is trusted to cover the fastest receivers on the other team, that's awesome. It means we shouldn't see the other team's speed burner running wide open down the field any more. It's also great for Munir. He's obviously been working very hard to learn the new position - hats off to him!

Good stuff.]

* * *

That’s all for today. Go Irish!

Musical chairs

Tuesday, October 9th, 2007

As Michael Rothstein noted yesterday, the latest version of ND’s official depth chart is out, and it’s different in some pretty significant ways from previous installments. Rothstein does a good job of noting the major changes, but I thought it was worth looking in a bit more depth at who’s moved where, and also relating these changes to some of Charlie Weis’s remarks from his Tuesday press conference.

Running back: James Aldridge / Travis Thomas OR Armando Allen OR Junior Jabbie OR Robert Hughes

What this means: I noted last week that there were reports that Aldridge had been made the official #1 tailback, but this is the first time I’ve seen it reflected in the depth chart. This is also a sort of a promotion for Hughes, who had been listed behind each of the other four backs in previous depth charts. While the Irish will certainly continue to change personnel in their backfield, it’s likely that a bit more consistency will help this team to establish a real offensive identity.

“Z” Wide Receiver: David Grimes / Robby Parris / Barry Gallup Jr. / Golden Tate

What this means: There’s actually no change here, though some may be surprised to see Tate still listed so far down. Weis was asked about this in his press conference today, and he said that Tate “got dinged a little bit in the [UCLA] game. He got knocked in the head a little bit.” But he insisted that Golden “will be involved in this mix right here.”

Center: John Sullivan / Dan Wenger

What this means: Wenger, who had been the starter at the right guard position earlier in the season, has been out the past few weeks with an injury suffered against Michigan, but he did travel to Pasadena and was supposed to be available, though he didn’t end up playing. Weis said in his press conference today that Wenger “hasn’t practiced that many reps full speed yet,” and that he won’t “just automatically get thrown in there” until he’s completely ready to go. The position switch could be simply a matter of putting him behind a more experienced player so that less is demanded of him, but it’s hard to know for sure.

Left Guard: Mike Turkovich / Thomas Bemenderfer

What this means: Bemenderfer had been listed as the backup center behind Sullivan, so this is a position switch of sorts for him, though he hadn’t seen more than a couple minutes of playing time in the first five games according to Lou Somogyi’s breakdown from last week. Once again, it’s hard to know whether it’s permanent.

Right Guard: Matt Carufel / Eric Olsen

What this means: I’ve already noted that Ben Ford wrote something last week about how Carufel didn’t want to give Wenger his starting position back, and it’s possible that he’s succeeded there. Meanwhile, Olsen had been the backup to Turkovich at left guard, so this is a switch for him, and a strong indication that Turk has managed to hold on to his position.

Right Tackle: Paul Duncan / Chris Stewart

What this means: Matt Romine had been listed as the backup to Duncan a few weeks back, but now he doesn’t appear on the depth chart at all, and Weis said in his press conference today that his elbow injury is “a little ways away” from being sufficiently healed, and that “I don’t expect to see him any time soon.” Stewart, meanwhile, had previously been listed as the backup to Matt Carufel at the right guard position.

Left Defensive End: Trevor Laws / Derrell Hand OR Paddy Mullen

What this means: Hand had been listed as the third-string right defensive end, so this is a minor position switch for him. Mullen, meanwhile, had been listed as Laws’s sole backup but had only seen a few minutes of playing time. Bringing Hand over to help the sophomore out might mean that Laws will be able to take a few more breathers, though Weis also indicated (see below) that Justin Brown might be the first off the bench to spell Laws.

Right Defensive End: Dwight Stephenson Jr. / Justin Brown

What this means: Brown and Stephenson had been listed as co-#1’s before, and when Brown went down with an injury Stephenson didn’t always start in his place. Stephenson did start last week, but Weis said in his press conference today that Brown could be in the game for either Stephenson or Trevor Laws, and that he’ll “go in first,” before Hand or Mullen.

Right Outside Linebacker: Kerry Neal / Brian Smith / Morrice Richardson

What this means: With the freshman Neal starting, senior Anthony Vernaglia is now a backup at the other OLB spot (see below). This is a big move for Neal, who’s played really well the last few weeks but of whom Weis said after the Michigan State game that he wasn’t ready to play consistently against the run. Weis said in his press conference today that Neal has “a bigger body than some of those other guys, and he’s more of a — he’s not as tall as John — but he’s more of a John Ryan type of player. So it kind of gives you — when those two guys are out there — it gives you more of a mirrored look on the right side and the left side.”

Left Outside Linebacker: John Ryan / Anthony Vernaglia

What this means: When asked why Vernaglia played at inside linebacker against UCLA, Weis said that this was done “out of need,” but that “this week he’s going to practice at both inside and outside. He’ll be listed at one (position on the depth chart). I think I put him as the backup Sam behind John Ryan. I think that’s where I put him, as the best backup left outside linebacker, but he’ll practice at both inside and outside this week.” We’ll see how much this ends up affecting Vernaglia’s playing time, but it’s clearly hard to see it as anything but a demotion for a player who has only thirteen total tackles on the season.

Strong Safety: Tom Zbikowski / Sergio Brown / Ray Herring

What this means: Herring had been ahead of Brown on the depth chart before, but Zbikowski rarely comes off the field except to bring in an extra cornerback, and so it’s hard to see this as a very big deal. (By Somogyi’s count, Herring had played a total of 6:23 at safety through the first five games, and the game participation statistics don’t show him as having played at all the past two weeks, even on special teams.) It’s perhaps worth noting, though, that there had been some whispers that Brown might be unhappy with his roles on the team and thinking of leaving, so the fact that he’s moved up on the depth chart may make him feel a bit better about his future.

Place-Kicker: Brandon Walker / Nate Whitaker

What this means: After he won the kicking competition this past week and hit two field goals, including a 48-yarder, against UCLA, there was little doubt that Walker would be ND’s placekicker for the foreseeable future. Whitaker will still handle kickoffs, though.

Punter: Geoff Price / Eric Maust

What this means: Maust replaced Price in the Michigan State game and handled the punts against Purdue, but Price returned last week and had a strong game. Weis said today that Price’s biggest problem has been with inconsistency:

We all know that he’s got the leg that can hit the ball 70 yards. But when you go out in the game and hit two or three crummy ones and then drop a snap on top of it, at that position you can’t hide.

I never call a player out, but there’s certain positions, the quarterback throws three interceptions, everybody in the stands sees it. An offensive lineman misses three blocks, you might not see it, depending on what happened on the play. But when a punter is out there and the ball goes 25 or 30 yards, it’s tough to hide that.

But I think that he’s really working on his consistency. I think that last week with the exception of one kick that he didn’t hit very well, I think that he kicked — he punted nine times and I think he had a very, very good day.

Hopefully Price can return to the consistently excellent performance we saw in 2006 that made him a preseason All-American candidate this year.

Anyway, that’s all I see for now. I’ll try to find some time tomorrow to write something about BC.