diff options
| author | Johannes Hofmann <Johannes.Hofmann@gmx.de> | 2026-11-16 23:01:33 +0100 |
|---|---|---|
| committer | Johannes Hofmann <Johannes.Hofmann@gmx.de> | 2026-11-16 23:01:33 +0100 |
| commit | 45f4d6b2ebcd52857f9ecc480a6fdcb11cb6e24d (patch) | |
| tree | 72793a509abab96190e523a8411ab4bdde1fb0b6 /crates/gipfel-desktop/icons/android/mipmap-xxxhdpi/ic_launcher.png | |
| parent | 335adadb70762410790a47ed1af1e49660dbbfcc (diff) | |
core: a fit must actually fit - reject huge residual RMS
User session log (browser console) showed the failure mode precisely:
a panorama (Saeuling az 11.2 at px 150, Zugspitze az 91.7 at px 3398,
linear pixel spacing) switched to rectilinear mode. Every seed landed
at cost ~12900 (RMS ~80 px) and the fitter committed the garbage
(pitch -81 deg, scale 91) because it merely passed the sanity filters.
Rectilinear geometry cannot represent linear pixel spacing over wide
spans: for an azimuth pair d apart, the x-ratio has a hard minimum
(~5 for d = 40.9 deg, and it grows with d), so such marker sets have
provably NO exact solution - the old 'always solvable' assumption held
only for tan-consistent spacings.
comp_params now computes rms = sqrt(cost/n) from the final cost and
rejects rms > 30 px with:
Fit cannot match the markers (RMS 80 px) - this projection cannot
represent the marked geometry. Is this a panorama? Switch to
cylindrical mode.
Regression test uses the user's exact captured marker data. Also fixed
a synthetic test placement (800/300 px for a 40.9 deg pair) that was
itself rectilinearly impossible - the guard caught it, which is a nice
independent confirmation.
Diffstat (limited to 'crates/gipfel-desktop/icons/android/mipmap-xxxhdpi/ic_launcher.png')
0 files changed, 0 insertions, 0 deletions
