Independence Day 5K results and post-race corrections

[Brian]

Results are here very soon:

www.chicorunningclub.org/resultsMaster.html

And this thread will be used to explain any corrections to the results
as they trickle in post-race.

If you are missing from the results, have the wrong time, placing, or
worse--gender or age--email run...@saber.net. I will investigate and
try my best to correct the problem and update the results.

Before any corrections roll in, I'll answer a couple of timing-related
questions here:

CHIP TIMING
Q: Why no chip timing at today's race? (Or the HOT in October.)

A: Chip timing costs us several thousands of dollars each event, and
for a race this small it would raise the entry fee considerably. Once
a race grows to, say, 500 or more racers, it is less painful to price
that into the entry. That is why we only have chip timing for the
Bidwell Classic and somewhat less often, the Almond Bowl.

BIB TAG
Q: Who do I give my bib tag to after I cross the finish line?

A: Nobody. When we time our smaller races like today's 5K, our process
captures bib numbers without resorting to having the bib tags in
backup. This backup system is sometimes called a "stringer" system. We
had more problems with stringers than without, and it requires more
people, so we ditched it. And today, your bib tag was your ticket to
pancakes.

CORRECTING RESULTS AT RACE
Q: Why can't you correct my missing/incorrect result there at the
race?

A: Sometimes, on the fly, we can correct the results. But in most
cases when runners approach the timing desk while the race is still
going, the timer's attention is completely focused on the equipment
and the finish line. Even when nobody is coming down the finishing
stretch, I still have to keep an eye on the finish line clock, the
official clock on my desk, and the timing application running on the
computer. Attempting to fix results errors at that point is a lot like
trying to fix an oil leak while driving down the road. There's too
great a risk of missing subsequent finishers or worse, botching the
rest of the results already recorded.

[Brian]

Bib 144, time 29:43 mis-keyed as bib 12. Bib 12 keyed in once again at
actual time 38:41.

Duplicate bib 12 corrected to bib 144.