Skip to content
Snippets Groups Projects
  1. Aug 16, 2024
  2. Aug 09, 2024
  3. Aug 08, 2024
  4. Aug 07, 2024
  5. Aug 02, 2024
  6. Jul 30, 2024
  7. Jul 29, 2024
  8. Jul 23, 2024
  9. Jul 19, 2024
  10. Jul 03, 2024
  11. May 31, 2024
  12. May 30, 2024
  13. May 29, 2024
  14. May 28, 2024
    • Erin (Josh) Rigler's avatar
      Add can_produce_data() method to SqDistAlgorithm · 2bd15768
      Erin (Josh) Rigler authored
      This simply returns True from can_produce_data(), which is appropriate
      because 1) a stateful algorithm should be able to procude data as long
      as it starts from a valid state, adn 2) SqDistAlgorithm itself checks
      this state. If we ever implement a different stateful algorithm, it
      should do something similar.
      2bd15768
    • Erin (Josh) Rigler's avatar
      Pull inputs in run(), not run_as_update() · dd71bde9
      Erin (Josh) Rigler authored
      For years, when invoking geomag-algorithms' update mechanism, inputs
      were pulled and checked from the run_as_update() method inside the
      Controller class. I never understood this. It seemed to break the
      logic of the update mechanism if no inputs were available for the
      current inteval/gap. This might even be the source of noted issues
      where running back-filling scripts didn't behave as expected, and
      those scripts needed to be run multiple times.
      
      What's more, the run_as_update() method logically seems like the
      most appropriate place to read *outputs* and check for gaps. Whereas
      the run() method seems like the most appropriate place to read
      inputs, apply algorithms, and write out outputs.
      
      In any case, this change should not break any existing code. It
      should only allow the update mechanism to complete, every time, and
      as originally intended, rather than be short-circuited when input
      data are missing for the current interval (but might be available
      for previous intervals)..
      dd71bde9
  15. May 16, 2024
Loading