On Wed, 4 Aug 2004, Glenn Ellingson wrote:
> Red flags are for SAFETY isues. If the course isn't set up it's up to
> the driver to decide whether to stop or to take the risk they'll be
> called. The use of red flags should NOT be blurred/diluted by
> non-safety issues.
Don't know where you got that. Red flags are to stop drivers. There are
regularly used to stop drivers for administrative reasons such as timer
errors, etc. at all levels of Solo competition including Nationals.
So, your perspective is at odds with the rest of the Solo world. How do
you reconcile that?
> Consider too that one driver stopping and pointing and resuming at 80%
> probably delays the event by 25 seconds (his/her rerun); a red flag
> stops (or at least, should stop) the course, causing several reruns and
> slowing things down more.
What's your point? Overlap is introduced into the event for
administrative purposes, not competition purposes. Competition is the
primary purpose of the event, and if the course is significantly altered
by downed cones, runs need to be stopped until it's stood up again.
> Kevin Stevens wrote:
> > Yes, though depending on the cone and what course the following driver
> > takes, I've seen people decide to let it go. It's up to the driver to
> > stop and point out a displaced cone that might be erroneously charged
> > to them, or that makes the course more difficult; but if the displaced
> > cone alters the course for the better the course workers should stop
> > runs. The basic guide is that all cars should be competing on the
> > same course.
KeS
|