- Feb 12, 2025
-
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
- Feb 11, 2025
-
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
Repeating small tests many times was order of magnitude slower. The reason is the computation of Lagrange polynomials was both inefficient and performed every time an RegularInterpLagrange instance was created. This causes overhead which is not relevant for large problem sizes but makes running many small tests slow. The fix for now is to cache the creation of the polynomials. Now they are created only onnce for each interpolation order, but not once per instance.
-
- Feb 04, 2025
-
-
Wolfgang Kastaun authored
Change math markup from mkdocs to sphinx syntax
-
- Feb 03, 2025
-
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
- Feb 02, 2025
-
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
Made test stricter. The previous parameters used a maximum shift too small to increase the required margin size, thus not testing anything related to its size.
-
Wolfgang Kastaun authored
-Sample rate now specified when constructing operator -Tolerance now given in same units as shifts, instead of index space.
-
Wolfgang Kastaun authored
Limit for coordinate shift was given w.r.t absolute time instead index space. Bug had no impact because shift was below 1 sample in either case (TODO: larger shifts).
-
- Jan 30, 2025
-
-
Wolfgang Kastaun authored
Note results can change within the inversion tolerance. The reason is that each dask chunk is inverted separately, which may lead to fewer iterations on the faster converging chunks of data. The boundary conditions during the interpolation within the fixed point iteration are flat. All points are used in the convergence measure. In contrast, the old scheme excluded a hardcoded margin. TODO: the case where interpolation is set to None is currently not implemented. All unit tests are passing.
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
Convergence criterion was excluding margins even though those points were actually valid.
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
- Jan 27, 2025
-
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
Also, exclude invalid margin points from error measure. The iteration stop criterion differs from the original one, which used hardcoded margins for this.
-
- Jan 24, 2025
-
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
- Jan 16, 2025
-
-
Wolfgang Kastaun authored
-
- Jan 15, 2025
-
-
Wolfgang Kastaun authored
Added instrument parameter delay_clock_max giving largest shift allowed to occur during resampling to different timeframes. For now, this is just a float and not compared to or inferred from the parameters for the clock drifts / noise. The interpolation method used is the same as for the interspacecraft delays, but employing the above limits for the time shift (needed for the internal margin sizes) Note: the inversion routine for computing the shift between time frames was not touched and still uses the original interpolation
-
Wolfgang Kastaun authored
The electronic delays are assumed to be fixed. Therefore, no new parameters are needed for the limits. A separate interpolator for electro delays was added to instrument, using the fixed interpolation method also employed in the adaptive interpolator for the interspacecraft delays. A parameter check was added to prevent passing non-scalar electronic delays.
-
- Jan 14, 2025
-
-
Wolfgang Kastaun authored
Moved those limits out of the interpolation parameter tuple.
-
Wolfgang Kastaun authored
The logic instrument.apply_shift is now in fixed_shift_numpy.AdaptiveShiftNumpy
-
- Jan 13, 2025
-
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
-
Wolfgang Kastaun authored
This emulates the previous behavior during the refactoring but needs to be improved later. It allows invalid points in shifted data also near right boundary. The ranging unit test that was failing with stricter BC now passes again.
-
- Dec 21, 2024
-
-
Wolfgang Kastaun authored
This adds a new method apply_shift, which uses the daskified time-shifting. It also changes the interpolation config parameter, adding minimum and maximum delay to the tuple. This delay refers to inter-spacecraft delays. The new methods are not applied to other delays yet, which are still using the old interpolator code that is still in place. There are now two dask-able Lagrange interpolators to chose from, a new implementation (method "lagrange") and one using dsp.timeshift internally ("lagrange_dsp"). For both, there are now separate interpolator interfaces for fixed and dynamic delay. The code to chose fixed or dynamic interpolator based on argument type is now in the new instrument.apply_shift() method. There are new unit tests for the time shift, also testing old and new implementation against each other. All but one of the original integration tests pass. The fail occurs in test_ranging.py for test test_prn_ambiguity_with_esa_orbits. The cause is that the sampling rate is chosen so low that the interpolation stencil extends beyond the right boundary, triggering an error by the stricter checks of the new routines.
-
Wolfgang Kastaun authored
-
- Dec 20, 2024
-
-
Wolfgang Kastaun authored
-