Hi there - You can use: https://project-gc.com/Challenges/GCAK85D/85500 Test it out and let us know.by bmuzzin - ARCHIVE Checker requests (completed)
It looks like there are two checkers associated with this GC code: https://project-gc.com/Challenges/GC5Q66E/12930 https://project-gc.com/Challenges/GC5Q66E/18924 In your cache page, you've linked to this one (which is for some other GC code): https://project-gc.com/Challenges/GC42VXP/568 They *all* seem like they work to me - how exactly are they not working properly?by bmuzzin - ARCHIVE Checker requests (completed)
Hi there - You can use: https://project-gc.com/Challenges/GCAK9C4/85499 Test it out and let us know.by bmuzzin - ARCHIVE Checker requests (completed)
Hi there - you can use: https://project-gc.com/Challenges/GCAKAR9/85498 Note that, the script works in meters not feet - 15420m is approximately 50,000ft. Test it out and let us know.by bmuzzin - ARCHIVE Checker requests (completed)
Not sure what happened there - at the particular error line with the error, it somehow changed from "month" to "months"... this checker script changes frequently, so it's always possible there are some errors that will be introduced. But - should be fixed now though (ran the checker, and I pass! ... I guess this means I need to go to Newfoundland now? :))by bmuzzin - ARCHIVE Checker requests (completed)
Circling back here - is anything else required here? When I run: https://project-gc.com/Challenges//80561 With your user name, the results now look reasonable. I think there was an error in the 'oldest' function in that script that was fixed in an unrelated request. Also, it looks like with the recent database conversion, these queries are faster than they used to be.by bmuzzin - ARCHIVE Checker requests (completed)
TL;DR: Okay so good news! I had an idea of how to optimize the script... and I've added in negative attributes. Even with adding the negative attribute checks, your profile runs in 14 seconds... so, extrapolating, somebody would need ~120k finds to timeout... which, if you have 120k finds, you probably pass :). However, the HTML output problem still exists. I've left in skipping prinby bmuzzin - ARCHIVE Checker requests (completed)
https://project-gc.com/Challenges/GCAJ5CT/85444 Hi there - I worked on this a bit... it might still need more work. There are a few issues: 1. Outputting all the calendars for all the attributes takes too much output space. I've cut the attribute calendars off for now, otherwise it won't show the HTML at all. 2. The script takes a long time to execute, and that scales with the nuby bmuzzin - ARCHIVE Checker requests (completed)
This script is checking for the date the geocache was hidden, not the day it was found. ie. you *found* GC40XC2 on January 26th, but it was hidden on November 8th, which is why it doesn't qualify. So, I think the script is working as expected (I only need one day myself... ironically in December).by bmuzzin - ARCHIVE Checker requests (completed)
Not sure what happened there - but should be fixed now.by bmuzzin - ARCHIVE Checker requests (completed)
Hi there - You can use: https://project-gc.com/Challenges/GCAJY1H/85169 Test it out and let us know.by bmuzzin - ARCHIVE Checker requests (completed)
Well, I think a user would just paste the "x / y weeks" in their log anyhow, not the entire list. There are many checkers that have huge log outputs, and usually you just paste the "passed" line into your log. I think logs on geocaching.com have a 4kb limit anyhow, which even at 52 weeks might be exceeded with one per week. And I think this way is better, because then the uby bmuzzin - ARCHIVE Checker requests (completed)
Alright! I think we're close. - I have put it back to the histogram version. - If the histogram is just looking for groups of one, it doesn't print out the "with the sum of 1" part. - I've made it so the 'hidden_year_weekn' goes into a field called 'week', so that the output now will just say "User has 40 weeks (15 needed)" right at theby bmuzzin - ARCHIVE Checker requests (completed)
Alrighty... I've implemented the ISO8601 method of week-of-the-year... you still are missing 21, 22 and 40. I've changed the function... so the output is different. Not sure it's better - it now lists all the events you've got, with the weeks where you have the most events first. Making a "nice" graph like the other checker mentioned is difficult, because it'by bmuzzin - ARCHIVE Checker requests (completed)
The checker will only show the first cache that meets the requirements for a week. Once it's listed a cache for week N, then even if you've found multiple others for the same week, it won't print them out. If you required (say) 2 events per week, then it would print out 2. But, again I think we're losing something in translation. What do you mean by "calendar week&quoby bmuzzin - ARCHIVE Checker requests (completed)
Just like me - I screw up some mundane detail! I've transposed it now... after losing the whole tag and having to redo it :)by bmuzzin - ARCHIVE Checker requests (completed)
Unfortunately not even the hand of God can reset the challenge check count... ... and I really hope this one gets published after all that. Good luck :)by bmuzzin - ARCHIVE Checker requests (completed)
https://project-gc.com/Challenges/GCAH6T3/85065 I have also long thought that the bingo output and configuration is terrible... they're not that popular, and I suspect they'll be accepted less and less by reviewers... but here goes. I implemented a new one - which also does a bunch of error checking, and also has an ACTUAL bingo card (2D output). Each square has a pass or fail icon (by bmuzzin - ARCHIVE Checker requests (completed)
Upped it to 18 required. Yes, the system automatically pulls the name of the cache from geocaching.com, but obviously it can't do that until the cache is published.by bmuzzin - ARCHIVE Checker requests (completed)
Alright, I've updated again... I've embedded the national parks as 'predefined' filters within the script. So now, when it "prints the filter", the name of the national park comes out next to each one in the log. I've also made it so you can limit what gets printed out in the filter, because, the example log has very little output space as well. With just thby bmuzzin - ARCHIVE Checker requests (completed)
I think to support that, the script will need further modifications, or, it maybe be just easier to create a new one, with some of the national park information embedded it in, so it doesn't require additional tag space. I can do this, it'll just take a few days.by bmuzzin - ARCHIVE Checker requests (completed)
Here's the one for this one: https://project-gc.com/Challenges/GC55871/84968 Only one of the last 10 loggers fails, they only have 26 finds and obviously don't pass here. Same rules apply to this one as the other - if it starts with punctuation, that doesn't count. Again, might want to clarify the intent with the CO, and we can easily change it up. Test it out and let us knoby bmuzzin - ARCHIVE Checker requests (completed)
Hi there - I already had a script very similar to this one, so I've cloned it, and tagged the challenge here: https://project-gc.com/Challenges/GC5BF6N/84966 As with legacy challenges, there's always a concern to "get it correct". Of the last 10 loggers here, 8 of them the script verifies as passing. Another person fails, with their "C" cache in their stated lby bmuzzin - ARCHIVE Checker requests (completed)
Hi there - You can use: https://project-gc.com/Challenges/GCAJP7Q/84965 Test it out and let us know.by bmuzzin - ARCHIVE Checker requests (completed)
I don't think it's possible. There's (very) limited space for entering the tag information... I had to modify this script to make it such that it fits as it is (for example, abbreviating 'county' to 'c'), and there's very little room left as it stands. Meaning there's not really any way to enter the names of the parks.by bmuzzin - ARCHIVE Checker requests (completed)
Ah okay - I did respond, there were just two threads. I think this is resolved then also.by bmuzzin - ARCHIVE Checker requests (completed)
Again, there are multiple ways to determine which week of the year any day falls on. January 1st 2022 was a Saturday. The checker assumes that weeks start on Sunday, thus the first week of 2022 in the original checker (which is what is being used now), the only day in the first week of 2022 was Saturday January 1st. September 26th was the 268th day of the year. Since the first week of the yeaby bmuzzin - ARCHIVE Checker requests (completed)
I've updated the tag so it's now the original version.by bmuzzin - ARCHIVE Checker requests (completed)
Not sure if I fixed this, and just didn't respond - if I run NVTaps through the bronze checker, it prints out their North America caches, which is their only continent, but gives them a failure, since they only have one continent. Could you confirm that the issue here is fixed?by bmuzzin - ARCHIVE Checker requests (completed)
Apparently the county name is "City of Saint Louis (MO)". Sometimes the county names in PGC aren't exactly the same as the OSM ones... so I've updated that. wsck4wsck4 now passes the one test. I feel like we're getting closer :)by bmuzzin - ARCHIVE Checker requests (completed)