Latest Entries »

Updating Results

Volunteers are currently working on getting data that hasn’t been updated in a while up to date, either due to volunteers who weren’t able to assist any more (and I didn’t know about) or who had problems and need us to update for them (some lost everything).  It takes time to go through 8 full months of checking logs, especially since this year has been a rougher year for dipping.  My guess is an increased number of users using apps like C:Geo, which by default automatically log a “Visit” log for all trackables in your possession (which if you don’t carefully go through the settings, you can easily miss this option).

I will have an update this week, with ALL racers updated.  I am also checking on the few issues some of you have brought up about inaccurate scores AFTER we get them all updated.  I say after because a few appear to be related to the lack of updates on some bugs.

We’ll be back soon with the updates.

I will say that I am currently looking at NOT doing a fifth year.  This does take time to manage everything and I am increasingly finding my weekend time is filling up well in advance.  Despite having a number of volunteers who help me, it still takes time to do everything.  I’d be open to stepping down to a volunteer role if someone is really wanting to take over the race, but this could be my last year of doing this.  Heck, someone else might have some ideas for improving the race.



July Results and Happy News

First off, the July Results have been posted.  At least as much as I have.  Unfortunately, some results haven’t been seen in a while.  So I am taking matters into my own hands at this point since some other options have been exhausted (though, I should be fair and say that some of the results were a result of a volunteer’s computer crash and they have asked me to take over scoring them).  What this means is going through the complete travels of about 28 bugs.  Once I have the scoresheets up to date, updating them month to month will go quicker.  If it hadn’t been for a dipping problem, my own set of 9 bugs would have taken me about 20 minutes to update.

However, this will all have to wait at least until next week.  Not only am I starting the new school year this week (with students returning on Thursday), but my own wedding is this Saturday.  So I don’t have the time it will take to update the scoresheets for the 28 bugs until after this weekend (my job prevents a Honeymoon so I will have evenings free).
Some of you have contacted me about why your bugs aren’t updating.  The lack of several months data is likely the reason.  Todd, I have your name down as needing a look at your bug.  And I have a note from the owner of Gumby.  These are the two I saw when I checked in this week.  If there is anyone else that has a discrepancy with the score you have calculated versus what is shown on this site (don’t count August movements in your score yet since they aren’t figured into the online results yet), please post a comment on here with the name of your TB, it’s reference #, and the score YOU have calculated.  Once I update the 28 bugs previously mentioned, I will compare it to what you are reporting and get back in touch with each of you regarding the discrepancy.

This year has been a hard year for the race, and a seemingly busy one for me personally.   As much as I would love to say that this race has gone on for 5 years, there have been enough complications this year to make me reconsider doing this another year. I guess it will depend on how much people want another race.  I recall being contacted from someone who wanted to replicate the race.  Maybe they might be interested in helping manage this one next year.  Who knows.

Good night everyone,

With the June updates came some surprise changes in the top 5.  Flower Power has taken the top spot and become the first racer to cross the 400 point margin. Way to go Flower Power. Also, with Geowoodstock having taken place near the beginning of June, we saw several racers make their way to the MEGA event, earning a quick 40 points and likely some miles and border crossings to boot.

Some great stories are likely developing with some of the racers. Unfortunately, others have been struck with tragedy. Several racers have unfortunately ended up in caches that got muggled before they could be picked up again. Others have been placed in caches and forgotten. If your racer hasn’t moved in a few weeks, get online and check out it’s movements. Look at the cache page for it’s current location. Find the log for the person who dropped it into the cache and then read some logs. Did it get mentioned by anyone? Did anyone report a cache with no trackables? If it looks like it is being passed up, sometimes a polite note on the cache page asking for someone to help the racer continue in the race will do the trick.

Or maybe your racer was picked up by a cacher who has held onto it for several weeks. Consider a polite e-mail asking for an update on the TB and asking if there are any questions that you can answer about the race and the bug’s mission. It’s amazing how a well worded e-mail can sometimes get a bug moving.

We are now halfway through the year. There is no way for me to see every log entry out there. Does anyone have a bug that has had an interesting story from their travels? Feel free to share the story with a link to your bug.

It’s been a busy year for me, so I’m sure there are others out there just as busy. Hopefully, many of you are enjoying your summer. I have a nice week-long vacation at the lake starting this weekend. That will really help relieve some of the stress of planning a wedding and replacing a wrecked car.  I will have some stuff with me so if more points data comes in I will update the results.

Race On!!