Consider going back to 1 SD for visit radiuses during overlap testing about locokit HOT 2 CLOSED

Occasionally people request a setting in Arc App, for adjusting this sort of thing.

That's something I'm not ever going to do in Arc App itself, because it's an explicit statement of failure on the algorithm's part. If the algorithm can't get the right answer, that's the algorithm's fault, and that failure shouldn't be shunted onto the user.

But settings and options inside LocoKit itself are still fair game. There's already some semi related prefs for minimum / maximum allowed visit radiuses, and some other related things.

Although that would still need something to dynamically adjust those settings in Arc App's case, some sort of heuristics based engine, given that Arc App isn't going to expose those settings to the user. So it's still far more preferable to get this managed dynamically in LocoKit, in a way that matches what humans expect the end result data to look like.

from locokit.

Well, nothing clever came to mind. And something still needed to be done. So I went with the simple solution of just going back to 1sd. And it does indeed feel a lot better. The 2sd experiment didn't pan out.

If any of my cunning plans come back to mind, I'll file them separately.

from locokit.