You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The initial dem_align.py planar fit to remove post-co-registration residuals worked well. The current n-order polynomial fit functionality is largely untested. User reports in Dec 2019 indicated this functionality is not working correctly, something that I was able to reproduce with quick tests, but didn't have the time to document and fix.
Change from geolib.ma_fitplane to geolib.ma_fitpoly:
Notes suggest we should consider numpy.polynomial.polynomial here. I need to revisit local branches - I thought I started this, but did not merge in master.
May be an issue of when/how the resulting "tiltcorr" correction is applied. I wanted another iteration of the main Nuth and Kaab optimization after the residual correction was removed, as it's possible that the final translation would be different after removing systematic residuals.
Should also rename command line option from -tiltcorr to -remove_residuals or something along those lines.
The text was updated successfully, but these errors were encountered:
The initial
dem_align.py
planar fit to remove post-co-registration residuals worked well. The current n-order polynomial fit functionality is largely untested. User reports in Dec 2019 indicated this functionality is not working correctly, something that I was able to reproduce with quick tests, but didn't have the time to document and fix.Change from
geolib.ma_fitplane
togeolib.ma_fitpoly
:demcoreg/demcoreg/dem_align.py
Line 374 in abd6be7
This
pygeotools/geolib
commit updated underlying fitting routines to support arbitrary higher-order polynomials:dshean/pygeotools@fbd7b97#diff-0c9ae3a15902d51d1f8374a5976f4d79
Notes suggest we should consider
numpy.polynomial.polynomial
here. I need to revisit local branches - I thought I started this, but did not merge in master.May be an issue of when/how the resulting "tiltcorr" correction is applied. I wanted another iteration of the main Nuth and Kaab optimization after the residual correction was removed, as it's possible that the final translation would be different after removing systematic residuals.
Should also rename command line option from
-tiltcorr
to-remove_residuals
or something along those lines.The text was updated successfully, but these errors were encountered: