ohio state blogs will post literally anything
Is Spartan Bob back??
Edit: I see you've fixed the glitch.
Never mind nothing to see here...
Considering the Big East already came out and said it was handled correctly I would say no, he is not back.
It's up to the officials to whistle for a delay of game.
Spartan Bob was having lulz with the GAME clock.
Thankfully, SpartanBob doesn't do that anymore. The Big Ten was sufficiently embarassed by his shenanigans in '01 to make timekeepers neutral, starting the next season.
You guys do realize that after the '01 MSU-UM game the Big Ten's head of officiating made a public statement that time was kept 100% correctly during the end of the game, right? Just checking.
Yes, they issued a cover-their-asses statement (though not as strong as the "100% correct" claim you make) - but then changed the timekeeping rule for the next season.
were as incredulous as everyone else. "Nice to have that home timekeeper, huh?", they said.
It wasn't until about one year ago that you EVER saw a sport or conference's governing body say that an official was wrong.
"Reasonable Lag Time" is to college football this week as "The Process of the Catch" was to the NFL last week.
Or having "the intent to blow the whistle" in hockey?
I hadn't heard this....
Honestly, I thought the play clock gaffe was much worse live. After watching the video for 79th time, it really isn't a big enough disparity to get angry about no flag (unless I was a Notre Dame fan). Helluva play call.
i heard there is some kerfuffle about the place holder's knee being down, but did not hear any rule quoted about why that doesn't count as being down. i have looked, but can't find the actual rule or ruling. did anyone else hear or see this?
The reason is because of Rule 4-1-3(b, exception). This rule creates the exception to the ball being declared dead when a player's knee is down touching the ground. The exception applies only to the HOLDER when an offensive player kicks or simulates kicking the ball for a place kick (Field Goal). By rule the ball may be advanced, kicked or passed.
In college football the hold may place his knee on the ground and the ball is not declared dead.
thanks. guys on the radio were going on and on this morning, i had to leave the car eventually.
Notre Dame Fans hate facts. They always seem to challenge their unrealistic outlook on their team.
Outlook: "His knee was down, Sparty cheated! We got robbed"
Outlook: "We are a Top-25 team"
The holder's knee being down does not count as "down" when he takes possession of the football. I had to coach my holder last week to that effect.
Did you just skip over Sunday?
the whole lag-clock rule is bull. time is kept on the field now so they dont have to look at the scoreboard. the playclock on the board was started when the ref signaled it so it should be accurate. msu got away with one
As for this line -- I have been seeing this meme all over the Sparty boards:
"...time is kept on the field now so they dont have to look at the scoreboard."
And it is, I think, untrue. I don't think that there is any "different" or "other" time being kept on the field. I looked at NCCA Rule 3-2 Article 4, and a careful read does not indicate that there is a guy on the field keeping a different clock. The rule specifically empowers the referees and the stadium "managment" to run the game clock and the play clock with an off-field official. Which, as a practical matter, everybody does.
The clock we saw on ESPN was the same as the scoreboard claock, and that was the one, only, "real" clock, and it got to :00 before the ball was snapped, whatever anybody wants to make of that.
Spartan Bob has been living with a very happy "retirement package" from the folks at MSU ever since he gave them that game in 2001. But I'm sure he loved this clock issue for the ND game.
I spent most of the day getting to or from Neyland Stadium for the Florida game, and the first thought when seeing this was "There's no way anyone saw this live." If one slows down the footage and watches, the exact margin between the clock hitting zero and the snap of the ball is something like a fifth of a second or so. An official is standing right over the play in full sight of a functioning play clock behind the offense. No Notre Dame coaches protested the call at the time, and none have protested it since. DVR has created a new, more exacting kind of viewer than those sitting in the stadium, where so much is going on at once that fine fractions like these go completely unnoticed.
The downside comes with making the natural--and this next part is important--necessarily forgivable portions of game officiating. We're not talking about in bounds versus out of bounds, or what constitutes a catch, but the areas of officiating where even in game there are understandable buffers: a fraction of a second (see: Big 12 Championship Game 2009) or a shadow of an inch on ball spots. While it's not soccer and the card system, football officials do employ a certain amount of human error at all times in football. DVR makes it that much easier to spot those from the godlike eye of the camera, and--this will burn us personally later when Florida is screwed on a call, but here it comes--that much more necessary to forgive the truly imperceptible marginal errors.
He is a good writer. Now go read this weeks Alphabetical: http://www.sbnation.com/2010/9/20/1698683/the-alphabetical-week3
I suppose I don't see how this situation is any different than a basketball official reviewing the tape to see if the player shot the ball before the buzzer. When you have the technological ability to be exact and 100% correct, why not be?
The play clock wasn't a bad call.big deal. The worst one, in my opinion, was how Cunningham's TD wasn't called back. He wasn't touched by the corner as he ran out of bounds, he simply ran out to avoid him... THAT is not being forced out and should not count imho. I am not positive on the rule here, but I believe that the defender has to physically force the receiver out for him to be allowed to catch the ball. I don't believe that this was the case Saturday night.
The rule (7-3-4-IV) reads that the exception only applies when the player goes out of bounds due to "contact by an opponent" so avoiding a player doesn't count.
The clock read zero and right or wrong, the big East refs threw no flag...? Their response to the handling of it seems reasonable to me.
I fail to see how pointing a finger at MSU impropriety even works in this case?
If it were a Spartan Bob-like transgression, wouldn't the time keeper have started the playclock late or somehow slowed the clock down to be sure to avoid a delay of game penalty and thusly the clock would never have reached zero?
But it did, so....
Wait.....State played Saturday night?
Even considering all this (FTR: I agree 100% with the Big East's explanation of the play), the entire point of penalizing a team is because they are gaining an unfair advantage. Snapping the ball 1/5 of a second late gains no advantage whatsoever. It doesn't as all affect the fairness of the game, especially in OT when there's no game clock. It's not even worth discussing.
Get over it folks, game is over and they won. Time for Michigan to think about Bowling Green and State to think about whomever......