PLEASE READ: This is the bonus cache for the A set of caches in KCSearcher's Feb29 2016 Experiment series to test First To Find (FTF) sharing. Cache is a preform. Parking is within 25 feet. Log FTF ASAP using mobile device, if available, to prevent others from wasting time and gas on a futile FTF attempt.
FTF prize is a $60 gift certificate to be used for shopping at Geocaching.com. To claim your FTF prize, remove the post-it that covers the FTF signature area. Send me the code from the post-it and your email address to my contact info at geocaching.com. If there are multiple cachers in the FTF party, send me each cacher’s email address (limit 6).
Read on for hypothesis and experiment details.
I have placed 2 sets of 29 caches plus 3 bonus caches for publication on 2/29/2016. This is to help cachers can fill in their caching calendar by getting a find on 2/29. In addition, there are some cachers that need an FTF on 2/29 to help complete their FTF blackout bingo. Remember, leap day only comes around once every 1,461 days.
My working hypothesis is that cachers are generally sharing people. For at least 58 cachers to have a chance at getting a First To Find on 2/29, they will need to share and only get one cache in these series as the First Finder on 2/29. Will the FTF hounds be able to control their passion and eagerness to pile up FTF’s, or will they be greedy and go after them all? If they are sharing, there will be at least 58 different cacher names to sign the FTF spot. I say “at least” because it is possible to share an FTF if the cache was found when more than one cacher was searching and one of them makes the actual find.
Travel (that’s why it’s a D4.0):
The A set of caches are located in the following counties:
- 5 in Alameda
- 9 in Contra Costa
- 3 in Sacramento
- 3 in San Joaquin
- 3 in Solano
- 3 in Stanislaus
- 3 in Yolo
Prerequisite:
To find this cache, you must have found at least 12 of the A set of caches and collect the number associated with the coordinate code letters from each cache you have found. Once you have found the all of the letters to derive the cache location, you will find the cache at N3a bc.def W12g hj.klm. To derive the final coordinates for your search, do the following math (the large letters correspond to the value you recorded when you found the caches):
- a = A - 1 (there are 4 caches with this code)
- b = B - 8 (there are 2 caches with this code)
- c = 6 - 6 (the 1 cache with the C code has been archived)
- d = 5 + 4 (the 1 cache with the D code has been archived)
- e = E + 3 (there are 2 caches with this code)
- f = F + 6 (there are 4 caches with this code)
- g = G + 2 (there are 5 caches with this code)
- h = H - 9 (there are 2 caches with this code)
- j = J - 0 (there is 1 cache with this code)
- k = K + 5 (there is 1 cache with this code)
- l = L + 1 (there are 2 caches with this code)
- m = M + 0 (there are 4 caches with this code)
You can validate your puzzle solution with certitude.
If you can't get the coordinates to come out right, recheck your work and try again. If you are still having problems, send me a message with the coordinates you derived and the data values you used for the coordinate code letters.
RESULTS to be displayed at the FTF on Feb 29. How did this year's experiment do? event on March 5th!!!
See KCSearcher's Feb29 2016 #AXX Experiment and KCSearcher's Feb29 2016 #BXX Experiment cache pages for details.
Please consider visiting all caches in KCSearcher's Feb29 2016 Experiment series. This link will take you to a list of those caches.