Advanced

Re: GC6ZV2P - 365 Days Found, 366 Days Hidden

[Resolved] GC6ZV2P - 365 Days Found, 366 Days Hidden
January 31, 2017 02:58PM
I need the cloned tag removed cache GC6ZV2P. The current checker requires 366 days found including leap day which is not allowed under the current challenge guidelines. I will need a checker that requires finds for each of the 365 days of the calendar (excludes leap day) AND at least one find for each of 366 days based on placed date (includes leap day).

Thank you for your help with this.
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
January 31, 2017 03:23PM
For the hidden days 366 days is accepted by the reviewers because a cacher can fulfill the challenge any day of the year.
The only difficulty is finding a cache which is hidden on the 29th of february
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
January 31, 2017 09:05PM
The existing checker that I cloned GC5HQKC requires leap day for both parts of the requirement. I need leap day excluded from the requirement to find a cache on all 365 days of the year. You are correct they allow the requirement to include leap day for those that must be found based on the placed date.

Can you please remove the cloned tag and update the checker or create a new one to work for this cache.
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
January 31, 2017 09:23PM
Here is the link to the new checker http://project-gc.com/Challenges/GC6ZV2P/24576
I will arrange that the old one will be removed

additional note: Cloned tag is removed
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 12:18AM
Thank you so much.
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 04:17AM
It appears that the checker is still requiring 366 days for the found portion of the challenge.
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 07:25AM
The output is not clear, but it does not require the 29th of February to be filled.
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 09:42AM
I was going to say that I just tweaked the output of my calendar checker to handle leap day differently but see now that this is a different checker. But still, the regular calendar checker output will now show leap day as optional (if indeed the challenge criteria allow it to be, which isn't always the case).

(It's not possible to tag that checker for this particular challenge due to multiple requirements.)
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 11:13AM
I need the output clarified as the cache was rejected once due to requiring leap day on my first submission. It would be nice if the calendars and notes indicated which was found and which was hidden as well.
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 11:19AM
This is a matter for the scipt writer in this case "Target." because he is the only one who can change the output of the checker

I did not think about another script before which shows the heading and has leapday as option

Here is the link http://project-gc.com/Challenges/GC6ZV2P/24586

Just tell me if you like this one and then I remove the other checker



Edited 1 time(s). Last edit at 02/01/2017 11:35AM by vogelbird. (view changes)
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 11:52AM
I like the output much better but does it exclude leap day? I can't tell from just running the checker. Is this script writer one we can contact to indicate that in the output?



Edited 1 time(s). Last edit at 02/01/2017 11:59AM by lil2busy. (view changes)
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 12:25PM
The checker will give green if there is no visit on leapday .

And you can contact the scrpt writer by pressing the little envolop behind {Script name: Charts challenges (by Jakuje)}

The script is a copy of "pinkunicorn" old script and if he updates it to the current script the leapday result should be clearer
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 01:53PM
I am not seeing a green check on leap day for the found caches for 2 cache IDs that I know do not have finds on 02/29. I show that it is still requiring a find for leap day. The totals also imply that they need a cache find on 02/29. The caching ids that I tested are EBFolks and ebgirl.

I still think that leap day needs to be excluded from the checker based on the results for these 2 cachers. Am I missing something?
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 02:05PM
The code in that checker is taken from an old version of my calendar script so the checker will show holes in the display grid for 29/2 even if the checker reports OK. This happens for challenges that don't require leap day.

Unfortunately, my updated version of the checker doesn't handle multiple requirements so that can't be used either. Thus, either Target or I need to change code to make this work as desired. I'll think about what needs to be done to handle this. If the requirements are the same for both placed and found (366 or 365 if leap day is missing) it should be pretty easy, I think.
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 02:45PM
Maybe Jakuje can update his script
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 03:05PM
I have reached out to Jakuje but haven't heard back.

Pinkunicorn if you can build one for 365 I will modify the cache for both 365 found and hidden.
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 10:55PM
I've updated my enhancement of Target.'s Multiple test checker script to incorporate the updated calendar checker code. So multiple test checkers using my script will have the updated output.
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 10:18PM
I updated the script from the original one by pinkunicorn. Thanks for letting me know.

Let me know if it does what you wanted now.

http://project-gc.com/Challenges/GC6ZV2P/24586
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 10:26PM
It would be *very* nice if there was a way for one script to call methods from another script so we could avoid this kind of unneccessary duplication of code...
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 10:37PM
I clearly agree with that, but there is still no such possibility and it was the main reason why the discussed script was created.

If I remember, there was some discussion about this topic years ago (can't find it now), but it was never put together.

Feel free to bring this topic up again in the general checkers discussion. Unfortunately I am not much active in checkers so I will not be able to drive it much, but proof of concept is already there for years.
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 10:52PM
There is proof of concept?
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 01, 2017 11:01PM
The "Charts challenges" checker basically uses the checkers as they were made by other authors and returns `ok` as conjunction of `ok` results of all the other used ones (and merges logs and output).

If every checker will have some unique name, all of that can be somehow put together and even use them directly from the config and without any need to create a new "superset" checkers.

But in any way, the problem would be stability of the results, because the author would not have complete control of his script behaviour, if it would call functions from different scripts, which is something we want to avoid in "official challenge checkers".
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 02, 2017 08:33AM
With this "solution" we will instead get an ever-increasing number of special checkers where people have just copied various bits from other checkers to make some change, and then never get the benefit of updates to the original checker, instead of trying to suggest updates to existing checkers.
Re: GC6ZV2P - 365 Days Found, 366 Days Hidden
February 02, 2017 04:06AM
Thank you everyone. I have submitted the cache. I appreciate all your efforts.

Lisa aka lil2busy
Sorry, only registered users may post in this forum.

Click here to login