Camron Rust |
Wed Jan 22, 2014 04:21pm |
Quote:
Originally Posted by AremRed
(Post 919631)
JetMet, looks to me like you blew at 20. Isn't the violation supposed to occur at 19, due to 30 not being a whole second?
|
Quote:
Originally Posted by CountTheBasket
(Post 919632)
No, think about it like this:
20.0-20.9999 (1 sec).....21.0-21.99999....all the way to 29.0-29.99999 (10 sec)
|
It depends on the design of the clock. At least two styles exist....most, I think, operate like CountTheBasket is implying.
The clock, internally, starts at 30.000000 but only displays 30.
At the very instant it is turned on, it internally drops to 29.999999. However, it may either still show 30 (rounding up) or it may show 29 (rounding down). In either case, it will remain the same until is crosses below 29.000000.
In the case of a clock that rounds up for the display, the violation would occur the moment it shows 20. In the case of a clock that rounds down for the display, the violation would occur when it shows 19.
An easy way to tell is to see if the horn sounds the instant it reaches 0 (a clock that rounds up) or if there is a delay of 1 second between the horn reaching 0 and the horn (a clock that rounds down).
I believe that most, if not all, modern clocks operate by rounding up so that when it shows 0, it is truly 0.0000000 and not 0 and a fraction.....or that when it shows any whole number, it has passed below that whole number but not yet reached the next whole number.
|