As one of the "negative posters" if a positive statement is required from me
about the event it would be that the new display boards continued to work
throughout the event despite the brutal weather, and it felt good to be
dodging cones again despite the problems. The solution I'd like to see is
for this event to be declared a "null" or test event, without it counting
for season points or as one of the first 4 events run. This to me is the
fair and correct solution.
I also propose that in the future, when an operational problem affecting
scoring like this is identified or suspected, the event should be halted
immediately until a determination can be made if a problem really does
exist, how much of the event has been affected by it, can it be rectified in
time to continue the event normally, or does the event need to be modified
to continue. ALL competitors should be informed of the problem as quickly as
possible, and if it has not affected everyone evenly what will be done to
equalize the event (reruns, blocks of times thrown out, whatever). If the
event cannot be continued normally and/or there is no viable solution to
equalize the event, we should be given the option to withdraw from the
event, or it be declared a null, or no points event for everyone.
In retrospect, a "potential problem red flag" probably should have gone up
earlier when drivers who were not completely staged upon tree activation did
not get an automatic red light. I personally witnessed this twice Saturday.
I definitely will wait to see what the home office does about this event,
but expressing concern at this point demonstrates to them that the problem
may have had a bigger impact than originally thought, negatively affected
more than just a couple people, the event was not equal for all or properly
handled, and it should not be simply shrugged off.
PS: Why do you consider it "good" that the problems cropped up at this event
"not later in the season"? If you mean before more events and competitors
were affected by them, then I'm offended by your "as long as it wasn't in my
backyard" attitude in critcizing us for being unhappy that it WAS "in our
backyard"! We did not sign on to be the crash test dummies or beta testers
for the rest of you when we registered for this event. If this event is
counted for us, then I think it's only fair that ALL the REST of the events
this season are run with the same problems still in place.
----- Original Message -----
From: Scott Troyer - TestEng TMR DDR <stroyer@micron.com>
To: The Fine's <webefine@qcol.net>
Cc: <autox@autox.team.net>
Sent: Friday, February 20, 2004 3:22 PM
Subject: Re: Timer Glitches in Atlanta
> You know, I've seen two very negative posts on this now on team.net and
also
> a discussion on SCCA forums. Do you have anything positive to say? Are
> you
> ready to offer any sort of solutions? What is it you want? Do you want
> them to
> throw the event out? If so then come out and say so (though I doubt
> Larry minds
> that 1st place finish in AS).
>
> I am sure the National staff was doing their best in what looked to be
> extremely
> miserable conditions. If this brought out problems in the new timing
> system then
> it is good they are being found now and not later in the season. I'm
> also sure
> they are aware of the issues and are working at correcting any problems
> before
> the next event.
>
> The results are still marked as unofficial so the national office may
> not have decided
> on the final solution to the issues. I think we should wait and see
> what they are going
> to do.
>
> Scott Troyer
> Snake River SCCA
> Nampa, Idaho
|