summaryrefslogtreecommitdiff
path: root/crates/gipfel-cli/Cargo.toml
diff options
context:
space:
mode:
authorJohannes Hofmann <Johannes.Hofmann@gmx.de>2026-11-16 22:34:35 +0100
committerJohannes Hofmann <Johannes.Hofmann@gmx.de>2026-11-16 22:34:35 +0100
commitac72f8e2d88cb10315abac3d1ceaa5252bc36ff5 (patch)
treea8cbb5b621c3dd8f14bdbe9e95784e5c6816a814 /crates/gipfel-cli/Cargo.toml
parentf2f2798e60acdb995924eed66864a106735bd3d3 (diff)
core: validity-filter the multi-start, don't guard after the fact
The real cause of the placement-dependent 'fit failed': the exactly- determined two-marker system has SEVERAL EXACT solutions - cost ties. Degenerate ones (scale ~30 px, center at a marker azimuth +/- 90 deg, where the tangent saturates) match both markers perfectly, won the lowest-cost race arbitrarily, and were then rejected by the post-hoc guards. A good solution existed but lost the tie -> random failures that flipped when a marker moved a few pixels. Fix: validity (scale >= 50, every known marker inside the projection domain) now filters candidates INSIDE the seed loop, before the cost comparison. First near-exact valid result (cost < 1 px^2) ends the search early, which also makes the typical fit ~75x faster. If no seed yields a valid fit, a plain run follows so the guards still produce the most informative error. Measured on a simulated Thaneller flow (Zugspitze fixed, Saeuling dragged over a 41x21 grid around its true spot): failures dropped from 163/861 to 0/861. On a deliberately absurd 61x17 grid (markers up to 3000 px off): domain rejections 103 -> 0, remaining failures are honest 'cannot determine scale' cases (marker in the other peak's x-column).
Diffstat (limited to 'crates/gipfel-cli/Cargo.toml')
0 files changed, 0 insertions, 0 deletions