1073 cars x 6 runs each = 6438 total runs x 5 seconds saved per run = 32,190
seconds -- or 536 minutes 30 seconds, or 8 hours, 56 minutes, 30 seconds. Or
1 hour, 7 minutes, 3.75 seconds per course per day.
Sam says it "only" came to 75 minutes per course per day? That's an hour-15.
Our numbers are close enough it is no argument. This year we ran about a
270-car event on each course each day four days running. That time saving is
how we were able to get 1073 cars through in about the same time it took to
run 908 last year.
Consider the down time about the same as previous years (except coursewalk
was cut from 20 to 15 minutes between heats), then how lucky we were with
both great weather and no on-course incidents that caused long delays (even
what cars we did break were quickly cleared). And we were done about 4 pm
each day. Have a major oops, or a big rain, and that fudge factor is quickly
gone.
We are getting awfully good at this (some classes were shorted runs in the
first few years), but let's not tempt fate. We need that fudge factor for
when s*** happens. IMHO.
--Rocky
-----Original Message-----
From: Sam & Greg Scharnberg <samandgreg@uswest.net>
To: Rocky Entriken <rocky@tri.net>; Jay Mitchell <jemitchell@compuserve.com>
Cc: autox@autox.team.net <autox@autox.team.net>
Date: Wednesday, September 20, 2000 8:41 PM
Subject: Re: Rocky's Stats for 2000?
>At 08:04 PM 9/20/00 -0500, Rocky Entriken wrote:
><snip>
>>BTW, I figured out what saving five seconds per car meant over the entire
>>event. About eight hours! Or one hour per course per day.
>
>
>I also calculated the 5 seconds saved per vehicle for 300 cars/day/course
and
>it only came to 75 minutes/course/day for a total of 2 and a half hours per
>two
>days. Actually, at 20 seconds it takes 5 hrs to get in 900 runs and at 15
>seconds it takes 3 hrs and 45 minutes barring no re-runs, etc, etc.
Granted
>there is the down time between heats.
>
>So how about 4 runs instead of 3???
>
>Food for thought,
>Sam
>
|