Skip to content
Snippets Groups Projects
  1. Feb 12, 2025
  2. Feb 11, 2025
  3. Feb 04, 2025
  4. Feb 03, 2025
  5. Feb 02, 2025
  6. Jan 30, 2025
  7. Jan 27, 2025
  8. Jan 24, 2025
  9. Jan 16, 2025
  10. Jan 15, 2025
    • Wolfgang Kastaun's avatar
      Use daskified interpolators to resample between different time frames · d0ef3dac
      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
      d0ef3dac
    • Wolfgang Kastaun's avatar
      Use new dask-based interpolation also for electro delays. · 81af4338
      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.
      81af4338
  11. Jan 14, 2025
  12. Jan 13, 2025
  13. Dec 21, 2024
    • Wolfgang Kastaun's avatar
      Use daskified time shifting operators for inter-spacecraft delays. · d452cbfd
      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.
      d452cbfd
    • Wolfgang Kastaun's avatar
      38920a6f
Loading