![]() |
|
|
|
|||
|
Quote:
Scientific facts are now being called "Hypothetical nonsense". I haven't picked any arbitrary numbers, I've just suggested that the accuracy "may" be off, and showed how it easily could be, and if you had video replay, I would guarantee it would be, by some fraction. I guess you defy the laws of nature and are perfect. You can read a running clock to the accuracy of the exact tenth of a second and your 5 count is always exactly 5 seconds, and you always start them exactly simultaneously with your clock glance. Good for you. You should work at the NBA replay center and just tell everyone how much time was left when the ball went through the hoop. It would save a lot of time. Everyone else, I recommend spending a few seconds at such a critical time in the game, to make sure everything is what you think it is. |
|
|||
|
you have done a great job of complicating a very simple task. We work with definitive knowledge and what we see is what's definitive. I would not trust anyone else's opinion except my partners in dealing with this. If neither of us have any clue we have bigger issues. Until replay is allowed this is what we work with.
Your hypothetical's are just pure hogwash. You haven't offered anything of substance except we "may" be off, which is 100% correct, and 100% useless. Then you offer a potential solution and what if, that we do not have the luxury of. Instead of thinking what things "may" be go with what they are and what you know, that's our limitation. In this case the OP handled it correctly and that's what any official should do. Hypothesizing on the passage of time and what may or may not be adds complications that are not needed. I would not ask the timer or anyone else if my partner tells me he saw X time and had Y count. I would do what the rules say and common sense dictates and I would subtract Y from X. It's not any more complicated than that, and it needn't be. For your information my 5/10 second counts are about +/- 1-2 tenths of a second. IMO, that's pretty good and I can live with that.
__________________
in OS I trust |
|
|||
|
Quote:
I agree, I think it's a stretch for 1.6 to be left. I'd bet they stopped it by mistake, started it, and stopped it on the whistle. But, if the clock said 0.6, and you went up to the timer, and they said I didn't touch it until you blew your whistle, then I think you would be wrong to change it. |
|
|||
|
Quote:
Do you have a suggestion as to what else we might do, both within the current rules and with any proposed rules change? |
|
|||
|
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. |
|
|||
|
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.
__________________
Owner/Developer of RefTown.com Commissioner, Portland Basketball Officials Association |
|
|||
|
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). |
|
|||
|
I suppose it could be read that way. I read to to say that when he got to 5 and called it, he looked up ans it was stopped at 1.6, which didn't make sense.
__________________
Owner/Developer of RefTown.com Commissioner, Portland Basketball Officials Association |
|
|||
|
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? . . .
__________________
To be good at a sport, one must be smart enough to play the game -- and dumb enough to think that it's important . . .
|
|
|||
|
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.
__________________
in OS I trust |
|
|||
|
Quote:
Quote:
If you're going to jump someone's case, you should at least be right.
__________________
Owner/Developer of RefTown.com Commissioner, Portland Basketball Officials Association |
|
|||
|
Quote:
|
![]() |
| Bookmarks |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Stop the clock? | GPC2 | Football | 29 | Fri Sep 15, 2006 01:16pm |
| When does the clock stop for OOB? | ChuckElias | Football | 16 | Mon Jan 30, 2006 08:30pm |
| stop clock? | CABA | Football | 2 | Tue Oct 26, 2004 10:26am |
| Stop Clock | ridavis13 | Soccer | 4 | Wed Sep 15, 2004 11:09pm |
| stop the clock to fix the net | Troward | Basketball | 34 | Thu Jan 23, 2003 10:47am |