×

To be able to write in the forum you need to authenticate. Meanwhile it's read-only.

Re: Checker request for: Oldest 100 caches out of 200 in Minnesota

[Resolved] Checker request for: Oldest 100 caches out of 200 in Minnesota
April 05, 2017 02:27AM
Vogelbird previously made a me a checker for finding oldest 50 caches out of 100 in Minnesota. The checker work great.
http://project-gc.com/forum/read?11,6086,7683#msg-7683
http://project-gc.com/Challenges/GC6WFA4/24134

I would now like to have a checker for the oldest 100 caches out of 200 in Minnesota.

Thank you,
Ranger Rog
Re: Checker request for: Oldest 100 caches out of 200 in Minnesota
April 05, 2017 04:15AM
Please provide your new GC code
Re: Checker request for: Oldest 100 caches out of 200 in Minnesota
April 05, 2017 02:09PM
Oops, sorry. The new GC code is GC73B98
Thanks,
Ranger Rog
Re: Checker request for: Oldest 100 caches out of 200 in Minnesota
April 05, 2017 02:37PM
Here is the link to the checker http://project-gc.com/Challenges/GC73B98/25770

You do not fulfill the challenge yet but please check it out
Re: Checker request for: Oldest 100 caches out of 200 in Minnesota
April 05, 2017 09:35PM
Boy, you are fast with the checker, Vogelbird. My previous checker took a month to get so I thought I had some time to get the 100 but your speed caught me off-guard. I found some today so I am only one short which I should be able to get in a few days. The link for the checker comes up "This checker script is disabled" so I can't check it out.

Thanks,
Ranger Rog
Re: Checker request for: Oldest 100 caches out of 200 in Minnesota
April 05, 2017 09:42PM
I forgot to enable the checker, but it's corrected
Re: Checker request for: Oldest 100 caches out of 200 in Minnesota
April 05, 2017 10:43PM
Thank you for enabling the checker.

I tried the checker and there appears to be some discrepancy in the output:
Ranger Rog
You have found 74 of the top 100
Missing cacheches are in red

The checkers can only check the current toplist.
If you were fulfilled it when you logged it in the past you might get a does not today.
Your log may have been correct but it cant be checked by this checker
On some challenges you when you accept it make a list and compare to that list. If you have done it you might fulfill the logging requirements right now but the checker can´t know that.
It is like if you make a new list right now. That is accepted on most challenges.
Please check the cache listing for the rules.
Script executed in 20 seconds. Peak memory usage: 14,336 kB

I should have found 92 of the top 200

I tried some people who should qualify and:
Boreal Walker
You have found all the top 115 caches
The list is the status as of 2017-04-06 00:18 servertime (CET)
I believe he should have found more than 115 of the 200

jonsom
You have found all the top 169 caches
Re: Checker request for: Oldest 100 caches out of 200 in Minnesota
April 06, 2017 08:20PM
Looking into the problem I found that the script only allows for 100 active caches so the caches 101 to 200 are not counted. I am not the script writer so I don't know if this could be easily increased.

However by investigating I also noticed the next problem,. The GetOldest is ({limit: 1000} which means for Minnesota a limitation date of 05-07-2003. At the moment there are till that date still 223 caches active.

As soon as there are 23 caches archived an altered checker will not work for your challenge either.
Re: Checker request for: Oldest 100 caches out of 200 in Minnesota
April 07, 2017 12:05AM
Thank you, Vogelbird, for looking into this problem. I don't have clue how the program works but I have a suspicion the 1000 cache limit will be a real deal breaker. Do you think it would be best to cancel this checker request and move on or should I leave it open for a while and see if a programmer has way around it?

Thank you for your time and effort on this,
Ranger Rog
Re: Checker request for: Oldest 100 caches out of 200 in Minnesota
April 07, 2017 12:19AM
Checking the API spec for the GetOldestCaches function, it looks like the defaults are that archived caches don't count toward the limit, but disabled ones do. So it should still be a viable function call even if several more get archived. Still need to get the limit increased, but that should be a fairly simple change to the script.
Re: Checker request for: Oldest 100 caches out of 200 in Minnesota
April 07, 2017 12:37AM
Howdy,

Vogelbird requested the script be changed. The limit is now 1000 not 100 so 200 should be fine for a while.

http://project-gc.com/Challenges/GC73B98/25797

Here is a new link.
Re: Checker request for: Oldest 100 caches out of 200 in Minnesota
April 07, 2017 02:25AM
Great work, guys...this looks fantastic. It even shows a cache in bold that I had found and then later adopted.
I'll test a few people and then turn it in for review.
Thanks,
Ranger Rog
Sorry, only registered users may post in this forum.

Click here to login