![]() |
Quote:
|
Quote:
Case Play: SITUATION A: Team A scores. As the official begins a five-second count the official glances at the running clock which reads 6.5 seconds. Team B commits a five second count violation. The official blows the whistle and looks at the clock which reads 1.8 seconds. A timing error is suspected. RULING: After conferring with the timer and your partners, it is determined that: a) the clock was prematurely stopped or had malfunctioned. b) the clock had not malfunctioned and was not stopped until the official's whistle for the 5-second violation. In a), use the procedure in rule 5.10.2 to correct the clock to 1.5 seconds. In b), make no change to the clock. |
Quote:
With all due respect, you're wrong. Don't forget, everything is being done simultaneously. You look at the clock and start your count at the same time. If your brain registers 5.3, then at the time your eyeballs saw it and you started your 5-second count, the time was about 5.4 (if u believe science). |
I'm not using my count to make the change or a fraction of a second in either direction. Accuracy across 5 or 10 seconds is just not high enough to correct such small differences.
If after starting a count at 5.3, someone gets to 5 and the clock still shows 1.6, one of a few things happened: the count was fast, the official observed the wrong time, the clock started late, or the clock stopped early. If the clock was already running, it can't be that the clock started late. It is very unlikely that clock stopped early. It happens but 99% of the clock errors deal with the starting of the clock or not stopping it in time. So, that leaves us with two most probable options that are both mistakes by the official. Regardless of the difference in the count vs what came off the clocks, if you don't know that it was not running at a time when it should have been, I don't think you can say that it is an obvious timing mistake when the difference is on the order of 1 second. |
Quote:
The delays of the brain at the observing, starting and stopping of the clock will cancel each other out thus making all of this irrelevant. |
Quote:
I thought it was a given in the OP that the clock stopped early. If not, I agree with you. And, I had the clock start early (when a missed FT hit the floor, and not when the ball was touched) this week. The ball was then immediately batted out of bounds. I saw the clock start early, saw the time when the ball was touched, and saw the time when the ball hit OOB. I took .5 off the time when the FT was shot, reset the clock, and off we went. Were my observations correct? I think so. WOuld someone else have observed something different? Possibly. (And, it all happened with < 10 seconds to go in the quarter). |
Quote:
|
I find it interesting that Case Book 5.10.1 SITUATION B states:". . . There is no provision for the correction of an error made in the official's accuracy in counting seconds."
. . .Kinda makes all our machinations on the subject moot, don't ya think? . . . |
Quote:
That is covering the case where an official calls a count-based infraction too soon or too late, such as calling a 10 second count after either 8 or 12 seconds have properly elapsed on the clock. The case play is saying that the violation stands regardless of information that indicates that the count is inaccurate. It is silent about changing the clock to match the official's count when there is no evidence that the clock was started/stopped incorrectly aside from it being different than the officials count. |
Quote:
It seems the discussion here is in regards to a coach or other party thinking that a correction must be made, and the procedure to make such correction. 5.10.1 A refers to the rule, and having "definite information." 5.10.1 D and 5.10.2 refer to "definite knowledge." Still, the entire rule allows for the less than accurate counting by the covering official, to serve as "definite information/knowledge," and on the less than perfect operation of the timing device and its control, by the Timer, as being precise. Thus, elements of less than perfect precision are inherently part of the entire process, but by rhetoric are accepted as accurate. It seems that the time-worn phrase applies: "Sometimes ya just gotta officiate the game." |
Quote:
The rules allow for some "human" discrepancy from when the official blows the clock dead to when it ACTUALLY stopped. For most of us it a few tenths to maybe even a half a second. In the second instance the timer said they stopped it when they heard the whistle and that accounts for a .3 second differential. We can live with that. IF the time says they stopped it before then we change it. You are not going to see a 1 second lag in this instance. In my experience it's about .1-.3. Your pseudo gibberish science and logic does not work here. It will not work in any game I work, and it makes no sense. You can try and confuse things but it doesn't work. |
Quote:
Quote:
Quote:
|
Quote:
|
All times are GMT -5. The time now is 03:55pm. |