Question

Can we have a checker for GC5PPPR please. Thanks

Comments

I'm not PM, could you paste the requirements in here?

---

To qualify to log this cache, you must accumulate a quarter of a million Church Micro points within 2 CONSECUTIVE calendar days. Church micro points are the number alocated to each church micro, i.e;

Church Micro 5699... Pleasley is worth 5699 church micro points.  Church Micro 6717... Rainworth Methodist is worth 6717 church micro points.  Just add up the church micro numbers of CM's found in two consecutive calendar days to see if you have 250'000 points or more. If you have the required amount of CM points in 1 calendar day, you still qualify... but may feel extra smug about your achievement.

---

Thanks, that should be quickly do-able.

---

Actually, the script I was going to use doesn't appear to support this. It'll be a bit longer than I'd expected.

---

Now tagged: http://project-gc.com/Challenges/GC5PPPR/16117

I'm also progressing with tagging other similar Church Micro Points challenges, there's about 6 others that'll soon all have checkers (as soon as I fix a bug in the code for longer time-spans)...

---

Thank you. I have managed to use this checker.

Answer 1

Now tagged: http://project-gc.com/Challenges/GC5PPPR/16117

I'm also progressing with tagging other similar Church Micro Points challenges, there's about 6 others that'll soon all have checkers (as soon as I fix a bug in the code for longer time-spans)...

Comments

I looked at creating a church micro checker before and there was a small problem that all caches did not follow the naming rule
There are many that your pattern misses
for example
1093 - CHURCH MICRO 1093 SR PETERS CRANSFORD
1102 - CM 1102 Holy Trinity Church Bradwell
456 - St Bartholomews Wickham Bishops - Church Micro 456 (maby i dont know how eol pattern matching works)
1190 - Church Micro - Elmstead Market BONUS

You could expand the pattern but i would guess there will be false positive with the 1102 match.
I think using the bookmark list at http://www.15ddv.me.uk/geo/cm/ is necessary.
There has to be manual adding of new bookmarklist bur you can use the and the pattern

---

Thanks for noting this I had also been informed of this by mole125, with the lovely example of:
6165 Church Micro Heighington

I'd also spotted a few other annoying cases such as:
Church Micro Rotherham 6428 (Holy Trinity Ulley)

I think that 1093 and 456 will be matched at present, because I'm not pinning the pattern to the start of the cache name, the space matching pattern at the beginning is superfluous though.
I'm not sure whether the bonus caches are counted towards challenges, but they appear on the bookmark lists so it's going to be the case.

I'm going to edit the script again this evening to make use of the bookmark lists and to adjust how the "Points" are retrieved, there's a few issues with caches that have multiple numbers in the name (especially where the CMID is 2nd):
 WPP #1 - Church Micro 7267...Winterley

And CM#1000 is also a special case due to the embedded comma:
Church Micro 1,000...Wherigo to Church

As a first approximation, it's mostly there, just a bit of fine-tuning required :)

---

1093 will fail depending of it the pattern are case sensitive
456 will fail it EOL etc (I don't think it is is not included because [^%a%d] will require a character if I am not mistaken. Is it really  necessary  to require a non number,letter after the number?
The number match will never happen if the %d+ before it is gready as I suspect it is

But just create a tag without the window and test on someone that have found those caches and test it

---

(My) patterns are case insensitive.
Ah, yes, EOL. I was needing to filter out Church Micro challenge caches, eg
Church Micro 100k Challenge
I was finding that just [^%a] would still match "Church Micro 100" as the 0 was matching against [^%a]. It's annoying the patterns aren't powerful enough to support ([^%a%d]|$)

Anyway, that won't matter once I move to bookmark lists.

---

Urgh, GC5EZ0X: Church Micro #6599 Horsley uses a UTF8 non-breaking space, which is lua treats as the raw bytes c2 a0... How fun.

---

Now updated to handle all Church Micro caches correctly.
Still have a bug in calculating find streaks > 2 days long., to fix tonight.

---

Finally fixed all the remaining known bugs. Checker now supports indefinite find windows, find windows of any length, and prints out your current 'best' find period to date if you don't fulfil the challenge.