Skip to content

Conversation

@laspsandoval
Copy link
Contributor

Change Summary

Overview

I've been asked to start to plan for overlapping stations and creating schedules for them.

Updated Files

  • generate_coverage.py
    • Handle stations so that they get priority. For example, we will always seek the most coverage from Kiel and inform other stations to not attempt to take data when Kiel is available.
    • Add capability for stations to fill in gaps if there is ever a DSN outage.

Testing

  • test_generate_coverage.py

@laspsandoval laspsandoval self-assigned this Jan 27, 2026
@laspsandoval laspsandoval added this to the January 2026 milestone Jan 27, 2026
Comment on lines +110 to +111
# This station now occupies these times and will block later stations
non_dsn_occupied_mask |= visible
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this actually what you want? This means that the way this loop is defined will dictate the order and amount of time that the stations will cover. If there is 1-hour of overlap but the first station has 4 hours and the second station has 8 hours, that would set this to 4-hours for the first station every time and only 7-hours for the second station, but you might want that second station to take precedence because it has the longer block of time.

In general, I think this is OK right now but it should get some more thought to how we want to approach it. One other idea is to not block based on ground-stations but rather indicate how many stations could cover a specific area, so DSN can block, but the others just add to the coverage time.

@laspsandoval laspsandoval marked this pull request as draft January 29, 2026 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants