Bad Time for the Clock to Stop

[Coach Bill]

Originally Posted by Nevadaref

The officials don't have a video replay monitor or atomic clocks in their heads. If the timer screws up, the officials can only do their human best to correct it.
ALL of the blame in such situations goes to the timer.

I'm asking are u sure the timer screwed up? He looks up after he starts his count and sees 5.3 (so, maybe ~5.8 when he started), then he counts a little fast (~4.5 seconds), that gives u 1.3. Pretty close to 1.6. The OP never said the clock stopped before his whistle, just that he looked up and saw the clock stopped at 1.6. I don't think there was definite knowledge of any error. I don't think one can accurately mark a running clock to the tenths of a second. And, who knows what the visible count was? 4.9, 5.1, 4.5, 5.5?

If he knows the timer stopped it before his whistle, then ok, fix it. Otherwise, like you said, no atomic clock in his head, the time may have continued to run until he blew his whistle. I.e., no error.

[Nevadaref]

Thank you for clarifying. Perhaps the OP will return and answer the questions you've posed.

[kk13]

Originally Posted by Nevadaref

Thank you for clarifying. Perhaps the OP will return and answer the questions you've posed.

I checked the clock WHEN I started my count. I saw 5.3. I counted to 5 and blew my whistle at which point we realized the clock had stopped prematurely.

[Adam]

Originally Posted by kk13

I checked the clock WHEN I started my count. I saw 5.3. I counted to 5 and blew my whistle at which point we realized the clock had stopped prematurely.

Good job.

[referee99]

Great job.

[bob jenkins]

Originally Posted by kk13

I checked the clock WHEN I started my count. I saw 5.3. I counted to 5 and blew my whistle at which point we realized the clock had stopped prematurely.

Exactly what you are supposed to do.

[Coach Bill]

Originally Posted by kk13

I checked the clock WHEN I started my count. I saw 5.3. I counted to 5 and blew my whistle at which point we realized the clock had stopped prematurely.

I want to know how u saw exactly 5.3 on a running clock. That's amazing!

[BDevil15]

Originally Posted by Coach Bill

I want to know how u saw exactly 5.3 on a running clock. That's amazing!

For approximately .1 second the clock says 5.3, are you honestly saying you have never seen any digit in the .1 second it was on the clock? Is it just a blur when you look at the tenths digit when its running?

[Coach Bill]

Originally Posted by BDevil15

For approximately .1 second the clock says 5.3, are you honestly saying you have never seen any digit in the .1 second it was on the clock? Is it just a blur when you look at the tenths digit when its running?

No, I can see the digits quickly scrolling by.... Signals from the eye take about a tenth of a second to reach the brain. The blink of an eye is approximately two tenths of a second. When I go from looking away at my running timer on my phone and then glance at it, I can pinpoint it to a small range (maybe within .3 seconds), but I can't tell you exactly to the tenth of a second. The official has to see that the ball is at the disposal of the inbounder, glance at the running clock, and start the count. To say for certain it was exactly at 5.3 is not humanly possible. If his brain registers 5.3, then it was at least 5.4. That's the only point I'm trying to make. I would still ask the table when they stopped the clock, and not immediately go to 0.3.

[Raymond]

Originally Posted by Coach Bill

... I would still ask the table when they stopped the clock, and not immediately go to 0.3.

They stopped it at 1.6 seconds.

[Rob1968]

Originally Posted by Coach Bill

No, I can see the digits quickly scrolling by.... Signals from the eye take about a tenth of a second to reach the brain. The blink of an eye is approximately two tenths of a second. When I go from looking away at my running timer on my phone and then glance at it, I can pinpoint it to a small range (maybe within .3 seconds), but I can't tell you exactly to the tenth of a second. The official has to see that the ball is at the disposal of the inbounder, glance at the running clock, and start the count. To say for certain it was exactly at 5.3 is not humanly possible. If his brain registers 5.3, then it was at least 5.4. That's the only point I'm trying to make. I would still ask the table when they stopped the clock, and not immediately go to 0.3.

(from Wikipedia)
The human eye and its brain interface, the human visual system, can process 10 to 12 separate images per second, perceiving them individually.

[1] The threshold of human visual perception varies depending on what is being measured. When looking at a lighted display, people begin to notice a brief interruption of darkness if it is about 16 milliseconds or longer.

[2] Observers can recall one specific image in an unbroken series of different images, each of which lasts as little as 13 milliseconds.

Coach, it seems the ascertion regarding 10-12 visual images processed per second by a human brain, is modified by element [2], which explains why/how it is possible to perceive the presentation of individual tenths on the clock.

[MD Longhorn]

Originally Posted by kk13

I checked the clock WHEN I started my count. I saw 5.3. I counted to 5 and blew my whistle at which point we realized the clock had stopped prematurely.

I think the question is this - how did you definitively see exactly 5.3 on a clock that was moving.

[just another ref]

Originally Posted by MD Longhorn

I think the question is this - how did you definitively see exactly 5.3 on a clock that was moving.

I would say the words definitively and exactly are not the most appropriate. The answer to your question is: "I did the best I could."

[just another ref]

Originally Posted by Coach Bill

I'm asking are u sure the timer screwed up? He looks up after he starts his count and sees 5.3 (so, maybe ~5.8 when he started), then he counts a little fast (~4.5 seconds), that gives u 1.3. Pretty close to 1.6. The OP never said the clock stopped before his whistle, just that he looked up and saw the clock stopped at 1.6. I don't think there was definite knowledge of any error. I don't think one can accurately mark a running clock to the tenths of a second. And, who knows what the visible count was? 4.9, 5.1, 4.5, 5.5?

If he knows the timer stopped it before his whistle, then ok, fix it. Otherwise, like you said, no atomic clock in his head, the time may have continued to run until he blew his whistle. I.e., no error.

When the OP says that they did indeed put the .3 on the clock, this tells us that his best impression was 5.3 at the start of the count. Consider this, if there is a "normal" discrepancy between the whistle and the stoppage of the clock, there should be even less time left. Lag/reaction time is normal. Stopping the clock early in anticipation of the violation is unacceptable. One can only assume that he checked with the timer to be sure that the clock did stop before the whistle. If the answer is no, as you say, I don't see a lot of alternative but to say "Oh my gosh, my counting is abysmal!" and proceed from there.