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

Re: https://project-gc.com/Challenges/GC2HD75/49721

June 07, 2020 11:28AM
The above checker is a resus cache checker
When I ran it I found an additional cache on the list to one I have been collating
When I checked I found the additional 'candidate' and discovered that I had not counted it as a resus as there had been another find prior to ours on the same day and it had been logged prior to ours on GC too thus should not have been picked up as a resus.
I was under the impression that the checker looked for gaps between my logs and the next previous log - on this occasion the gap is the same day so should have recorded a '0' count but instead it has ignored that
I appreciate these circumstances are not common (such luck that you go and look for a resus cache and some one beat you to it on the same day) but it does skew the findings

Any ideas


Edited 1 time(s). Last edit at 06/22/2020 08:46PM by Deepdiggingmole. (view changes)
Re: https://project-gc.com/Challenges/GC2HD75/49721
June 08, 2020 09:31AM
This is a known problem but can not be avoided. A checker can not look in a logbook and if there are 2 cachers visiting a lonely cache on the same day there is no way of telling who was first. The cacher logging online does not have to be the cacher who found the cache first that day. Lonely caches are often at places which have no internet connection and the finder can be on a trek in the wilderness whereby the online log is not made on the same day.
Re: https://project-gc.com/Challenges/GC2HD75/49721
June 08, 2020 10:07AM
I did suspect that - but frustrating that it skews results - however it is not a very common occurrence thankfully :-)
Sorry, only registered users may post in this forum.

Click here to login