-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review A6b threshold of 0.06 #1124
Labels
Comments
There was a very weird malfunction with a Gen 4 (IIRC) at one of our Ontario comps once where the timer was stopping without the competitor making full contact with the timer. IIRC that incident actually resulted in two DNFs over .06 which lead to E2 being given. |
To add, I've seen quite a lot of malfunctions on Gen 4, when the timer stopped itself at 0.1*, but I rarely saw malfunctions with the time below 0.06 too. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As far as I can tell, the 0.06 threshold in A6b was introduced more than 10 years ago (when Gen 2 timers were mainly used). I am curious if we have data or evidence that supports a time strictly below 0.06 being indicative of a malfunction on Gen 3, 4, and 5 timers.
I would push for removing A6b1 (automatic extra if the timer "malfunctions" to a time strictly below 0.06). I've seen other types of timer malfunctions that are reproducible (these should of course warrant extra attempts), but never a timer that consistently malfunctions to a time strictly below 0.06 seconds. My theory is that times below 0.06 are due to an extremely nervous competitor's hands shaking as they start the timer, which causes them to accidentally stop the timer.
The text was updated successfully, but these errors were encountered: