Re: New checker w/ optimized algorithm for https://coord.info/GCA0BD7

Hi,

background: I created challenge https://coord.info/GCA0BD7 and tagged Multiple Test Checker v2 for it https://project-gc.com/Challenges/GCA0BD7/74593 only to learn later that the execution of this checker times out with some geocaching nicks.

As the solution to this kind of problem is complex, I've learned now that this type of solution would likely need its own script, with an algorithm designed for this kind of problem directly.

Since I'm afraid this exceeds my current skills, I'm kindly asking if there is anyone who would have time & interest into looking how to solve this problem more efficiently (by writing a new script).

I will implement this.

Can you provide an example username that times out?

Thanks. I only personally know of "essiva" however just a moment ago when I tested, it did not time out anymore. One Finnish reviewer let me know there were more so I've passed question to him/her to provide impacted usernames. Will get back once I hear from them.

Update: got answer - additional impacted nicks "mipoded" and "satuja".

Thank you. I think the reason it is slow is because they don't qualify. The checker spends time trying to find the "best" solution (which will never terminate because of a large number of possibilities.)

Update: I propose the following.

https://project-gc.com/Challenges//75350

Please test. This runs in <1 second for mipoded and satuja, and also for mondou2 (#1 most finds in the world) and RetiredGuy (American w/ #1 most countries visited) and merdian (German w/ #1 most countries visited).

(Please do not link on the cache page just quite yet. I want to make a couple more changes.)



Edited 2 time(s). Last edit at 02/20/2023 11:49PM by Hügh. (view changes)

Hi, this looks very good. However, I tested this one with a few random nicks other than those known problematic ones and found at least one that now times out ("georapo"). Will continue testing later.

georapo now runs without trouble.

@Hügh you should exclude "Locationless (Reverse) Cache" types because cachers will have false positives

Disclaimer: as CO, I'm fine in including locationless as part of accepted criteria.

Looks very good, indeed. Executed this against nicks I know that have travelled 'more or less' and could not find any more issues. Are you still going to perform additional tweaks or do you consider this ready for publishing/replacing the original?

I made a couple final tweaks. You can now link to it if you wish.

https://project-gc.com/Challenges/GCA0BD7/75350

Perfect. Thank you very much Hügh for your quick response and for good solution!