Re: Checker for find-counts at certain elevations/altitude intervals

Hi,

I would like to request a checker similar to https://project-gc.com/Challenges/GC7FTNP/36789

for the following (new) challenge regarding finds at certain altitude rungs as follows:

You must have found
10 caches at altitudes up to sea level (0 meters included),
10 caches at altitudes between 1 and 5 meters above sea level,
10 caches at altitudes between 6 and 10 meters above sea level,
...
10 caches at altitudes between 566 and 570 meters above sea level,
(115 rungs of 5 meters with 10 finds each)

10 caches at altitudes between 571 and 585 meters above sea level,
10 caches at altitudes between 586 and 600 meters above sea level,
...
10 caches at altitudes between 736 and 750 meters above sea level,
(12 rungs of 15 meters with 10 finds each)

3 caches at altitudes between 751 and 775 meters above sea level,
3 caches at altitudes between 776 and 800 meters above sea level,
...
3 caches at altitudes between 1226 and 1250 meters above sea level,
(20 rungs of 25 meters with 3 finds each)

5 caches at altitudes between 1251 and 1500 meters above sea level,
5 caches at altitudes between 1501 and 1750 meters above sea level,
...
5 caches at altitudes between 2751 and 3000 meters above sea level.
(7 rungs of 250 meters with 5 finds each)

The challenge should be published as GCAMWBR

Looking forward to your comments.
Kind regards
Mi(chael)

Your request for a similar checker is not possible because I am running out of config space.

I can only use a macros setup for which I made two type
One with just the totals and one with just the GCcodes

But you do not fulfill your own challenge yet

https://project-gc.com/Challenges/GCAMWBR/87140
https://project-gc.com/Challenges/GCAMWBR/87141

Please test and reply

Hi vogelbird,

thank you very much for quickly implementing those two checkers. I did some testing.

Reading the tag configuration I noticed that you put "meters<%3" which excludes the upper bound. I guess the correct condition should be "meters<=%3" to cover the entire interval. (Alternatively the upper bounds in each interval could be increased by 1 meter to get to the lower bound of the following interval, right?) This would also explain most of the rungs I missed in the test run on my own statistics.

Nevertheless there is one interval (1076-1100) where my find counts indeed fail the given condition by one cache. Hence I would like to request the 20 rungs of 25 meters with 3 finds to be replaced by 10 rungs of 50 meters with 5 finds each as follows:

5 caches at altitudes between 751 and 800 meters above sea level,
5 caches at altitudes between 801 and 850 meters above sea level,
...
5 caches at altitudes between 1201 and 1250 meters above sea level,

Looking forward to the modified checker.
Best Mi(chael)

P.S.: Once I have logged the caches I found last week, the modified checkers should accept. Of course I will check this before sending in the cache page for review.

"meters<%3" changed into "meters<=%3"
and
5 caches at altitudes between 751 and 800 meters above sea level,
5 caches at altitudes between 801 and 850 meters above sea level,
...
5 caches at altitudes between 1201 and 1250 meters above sea level,

altitudes rings changed

Please test

Modified in no time and now everything looks perfect!

Thanks a lot, much appreciated!

Best Mi(chael)