Dumb question about time penalties
So Santa Clause got me a big yellow XC watch. :lol: I've already been playing with it and trying to get used to what speed feels like what. I have a question about XC times. Say your optimum time is 5:30. I know you get penalized for every second you come in over optimum time, but what's the buffer on the other end for coming in too fast? I've been looking in the rule book, and cannot find the answer. I'm working an overnight tonight, so hopefully some you gals on the other side of the world are up and surfing today so I have someone to play with.
Ok, USEF rules:
a. Optimum Time—The distance divided by the designated speed gives the optimum time.
Completing the course in less than the optimum time results in zero time penalties. A competitor
exceeding the optimum time will be penalized in accordance with EV141.2.a. Time is
counted in whole seconds, parts of a second counting as the next whole second (e.g. 30.25
seconds is recorded as 31 seconds.)
b. Speed Fault Time—For the Beginner Novice, Novice and Training Levels, the distance divided
by the speed fault speed gives the speed fault time. Completing the course in less than the
optimum time is not penalized up to the speed fault time. Completing the course in less than
the speed fault time will be penalized in accordance with EV141.2.b. Time is counted in whole
seconds, parts of a second counting as the next whole second (e.g. 30.25 seconds is recorded
as 31 seconds.)
c. Time Limit—The time limit is twice the optimum time. A competitor exceeding the time limit
will be eliminated.
d. Timing - Time is counted from the instant the starter gives the signal until the instant when
the mounted horse reaches the finishing line. Time is counted in whole seconds, parts of a
second counting as the next whole second (e.g. 30.25 seconds is recorded as 31 seconds).
great copy of the USEF rules here http://useventing.com/sites/default/...r_Eventing.pdf this is the set of rules we use here.
You will have to find out your course length for each event.
Posted via Mobile Device
the course map for the xc will tell you the length, optimum time, and when speed penalties start at on it !
It depends on how you want to keep time. I preferred having it count up from zero. I would measure on the course where each minute should be (i.e. right before fence 5 etc.) and listen for it to know if I was right on time, early or ahead. Or you can set the optimum time and have it count down from there.
I actually stopped measuring my minute markers for events below preliminary, just because it's pretty easy to stay on time, but like I said it all depends on how you think and how you want to keep track of your time. The only time I ever used it to count DOWN from a certain time was when I was doing conditioning work and gallop sets. I'd just set it at (for example) 5 minutes and start cantering; when it got to zero I'd have the walk break, reset it to whatever time I needed, then continue my conditioning.
This watch starts beeping for a full minute when it switches to counting up. We set it to 5 seconds countdown to simulate the start box, it counts down the 5 and then beeps for a full minute when it starts counting up. I might just mute the thing since I really just want an idea of how we're doing on overall pace. My horse seems to move along but ultimately has a short canter & gallop stride, so his pace can feel misleading if I'm just up there having fun.
Weird. Mine doesn't beep for a full minute. o_o Maybe because it's an older model or something?
It better not be an older model! That thing is brand new. Maybe I should call Smartpak and ask if they have a less annoying one? My friend said they all do that...guess not.
|All times are GMT -4. The time now is 05:02 AM.|
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2016, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.