![]() |
What would you do?
Team A losing by 2 end of the game, goes up for shot to tie, misses, in the scrum after the rebound, the ball goes out on the endline (to Team A), L blows whistle to kill clock, as whistle blows T looks up and sees time still on the clock (tenths of a second, but how many?), then horn blows....
|
Quote:
|
You Have definite knowledge of time on the clock, so you have to put some back on. We all know that less than 3/10's does not allow for a shot, and that it takes time to hear the whistle and Then look. Was the time between the whistle and the look long enough to shoot a ball?
|
Quote:
|
Quote:
You put up what you see on the clock. Period. End of story. The rule was changed to simplify the call. Don't overthink the play. |
Quote:
|
Quote:
|
Quote:
|
Quote:
I would also say that if you look up and see tenths running but don't get one pulled out, you have definite knowledge that at least .1 is left, and if you see multiple numbers then at least .2. Others will certainly argue otherwise, but I can say that if I look up and see multiple numbers run off before 0.0, then I have definite knowledge that at least .2 was left... |
Quote:
So, I'm just going to highlight the major problems. 1. If you didn't see a number, then you don't have definite knowledge. That's what definite knowledge means. 2. You can't suggest anything. You have to know. What you did was guess and that's not allowed. If you can't say I saw X on the clock, then you can't put any time back on. 3. So did she release the ball before the horn or not? You can't employ any other standard for making the call in such a situation (barring a clear timing error). 4. There is no "definite knowledge test". :confused: There is only definite knowledge. Final summation thought: Why do people always want to invent strange concepts instead of just following the rules as written? |
Quote:
|
Quote:
This situation is exactly why you should ALWAYS count! |
Quote:
|
Quote:
If the timer is a couple of tenths slow and the player actually gets .7 to make the play, that's the way it goes. I have no way of addressing that. That is the timer's job and I can't do it for him. Perhaps he's been a touch slow all game. Those are the breaks and part of the human factor in sports. What I will not do is use some arbitrary standard such as you suggest based upon the movements of a player to declare the period over and the try no good. There is no rule basis for that. Finally, if the horn came simultaneously with the release, then the try was not in flight when the horn sounded as required by the rule and therefore the ball is dead and the try doesn't count. The horn is what determines the call and that is for what you need to be listening. Don't bring other factors into it. |
in these type of situations ... Just count - it will make your life easier!
|
Quote:
BUT - that said I understand what he is saying about the player movement and I guess the basis he might have used is that the Fed says you cannot catch and shoot with .3 sec or less - it has to be a tip. So, using that standard, if a player caught the ball it would have to be .4 and if they did any other motion it would be longer than that. |
Quote:
What if the clock had read 0.8, 1.4, or 2.6? How many dribbles and pivots is he going to allow before he declares time to have expired? Thinking in such a manner is dangerous as it can only lead to problems and wrong decisions. Simply put his advocated criterion has no validity under NFHS rules and shouldn't be used. |
Quote:
|
Quote:
|
Quote:
In the case above with 0.4 seconds on the clock, if the ball is in the air when the horn goes, and you don't have definite information as to whether the clock was started properly or not, the rules say that you do have to count the basket. |
Quote:
Best Wishes. |
Quote:
Obviously with .4 we are only getting to 1.0 with our count and if the ball is not out of hands, we have dead ball. |
Quote:
|
Quote:
(corrected spelling for juulie's enjoyment) |
Quote:
|
Quote:
kbilla -- what you do is whatever thought process you are going to do, and then DON"T POST THAT THOUGHT PROCESS ON THE BOARD. You post the question without admitting what you did. That way you get the answer you need for next time, without the abuse. Got it? |
Quote:
You are wise beyond your years grasshopper. |
Quote:
|
Quote:
You definitely have to put time back on the clock -- even if you aren't quite sure if it is 0.6 or 0.4 ... you have definite knowledge that there was time left and it is the right and fair thing to do! And for all of you counters out there... How the hell do you count in tenths of seconds?!? Counting doesn't really do you a bit of good in the situation outlined here. |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
Doesn't he have definite knowledge that there was NOT zero seconds on the clock? If we agree on that, how can he leave 00:00 up there? |
Quote:
What is a player able to do in that time? |
Quote:
|
Quote:
|
Quote:
|
Quote:
That's exactly what I've been saying. |
Quote:
I say that's definite knowledge. |
Quote:
You can put back up the exact time that you first see when you look at the clock. And that's not what I'm saying. That's what the <b>rules</b> are saying. When they got rid of lag time last year, this is what was stated in the COMMENTS on the new rule: <i>This change eliminates the need for lag time or reaction time on the part of the clock operator. The referee may put the <b>exact time observed</b> by an official back on the game clock. The committee felt that with new clock technology and the ability to observe tenths of a second, when an official has definite knowledge relative to the time involved, he/she should have the ability to put the correct time on the game clock."</i> If you don't get a clear view and see an exact time, then <b>NO</b>, you can't put any time back on. What you actually <b>see</b> is the only time that can go back on. Dem's the rules. |
Quote:
|
Quote:
|
Quote:
To say that you can't put any time back on because the clock was a little blurry to the official is absurd. |
Quote:
|
"Definite" vs. "Exact" - the debate rages on...
|
Quote:
It's the rules, whether you happen to agree with them or not. Definite knowledge is what you see, not what you guess. If you can find a rule <b>anywhere</b> that will let an official <b>guess</b> at how much time to put back up on the clock, please feel free to cite it. If you put "something" back on the clock even though you aren't sure what that "something" should accurately be, what do you plan on using to justify your actions post-game? |
Quote:
|
Quote:
That's not a guess, and that's all the justification I'll need post-game. |
I think that you are reading the rule wrong. The first part states...
The referee may correct an obvious mistake by the timer to start or stop the clock properly only when he/she has definite information relative to the time involved. You have definite knowledge if you see time still on the clock. Period. Thus, you are able to put time back on the clock. The exact time observed by the official may be placed on the clock. This part of the rule does not say that ONLY the exact time can be put back on the clock. It states that the exact time MAY be put back on the clock. Why? Because the rule in years past was that you had to allow for lag time. They have since changed that rule to allow officials to observe the EXACT time and put that back on. Think about another situation -- if you have 30 seconds left in a game and inbound the ball in the backcourt. You get to a count of 5 and they still have not started the clock, so you stop the game, have the timer reset the clock to 25 and inbounds nearest to where the ball was when you blew your whistle. That is definite knowledge but it is not "exact" -- but it is a perfectly legitimate situation under the rules. The first statement of this rule -- that an official can correct an obvious mistake by the timer as long as the official has definitely knowledge, is independent of the second sentence that the exact time may be put back up. |
Quote:
|
Quote:
|
Quote:
One thing is for sure...definite != exact. |
Quote:
|
Quote:
If you watch just a few games, it becomes clear that an overwhelming majority of HS officials counts are ridiculously slow. Most that I've observed are ~50% off or more. I'd bet that my sense of time at less than 1-2 seconds is more accurate (as a percentage) than the average official's count. That definite enough for me. The whole point of the rule change was to not penalize a team when a foul clearly occurs before the horn but the clock doesn't stop. If don't or can't look at the clock or can't just know how much time should be there with your own faculties, that's not my problem. |
Quote:
The rule was put in because the idea of "lag time" had become outdated. Starting in the NBA, then the NCAA, and now high school, officials can put back exactly the time that they observe on the clock -- rather than having to account for the 1 second "lag" time that was the previous rule. That is what "exact" means in the second sentence of the rule. That the official MAY put back the exact time. It does NOT mean that the official cannot put back any time if they did not observe EXACTLY what was on the clock when it should have been stopped. |
Quote:
Please tell me where I can find in the rules that it's OK to put <b>any</b> time back on the clock that you feel like if you didn't see <b>exactly</b> what was on the clock. What <b>exactly</b> are you guys using for "<b>definite</b> in formation"? "Exactly" is seeing something like 1.5 seconds on the clock. You and Camron are trying to say that you can pick(guess) some other time. Well, what time are you guys going to pick? 1.4 seconds? 1.3 seconds? 1.6 seconds? etc.,etc.? And what are you basing your pick(guess) on anyway? Saying "I just know it", as Camron said? We'll have to disagree on this one. |
Quote:
I agree with your position when we're talking about several whole seconds and trying to arrive at some sort of estimate based on how many seconds it takes to dribble this far and pass once, and which coach I'm less patient with tonight. But in the sitch we're discussing, I think a reasonably close guess with a tolerance of a couple of tenths isn't really what the rules are trying to eliminate. |
Quote:
|
Quote:
I have definite information that the clock was not stopped correctly. I have definite information that it should not read 0:00. At this point you use your judgement, along with information from your partners (and possibly the table) to determine the correct amount to put back on. Quote:
Remember the spirit of the rule here is to correct an obvious timing mistake. If you want to say, "Sorry, coach, I do know that the clock didn't stop, but I didn't see exactly at the point at which it should have, so I can't put anything on." then, yeah, we are going to have to agree to disagree... because that is horrendous. |
Quote:
|
Quote:
What if there are 3 seconds left and you blow your whistle, but don't look at the clock. Then after a few more seconds the horn blows and you look up at 0:00??? Are you going to end the game then since you don't know the exact time to put up??? |
All times are GMT -5. The time now is 10:33pm. |