I-ALiRT - add extension#297
Merged
laspsandoval merged 2 commits intoIMAP-Science-Operations-Center:mainfrom Mar 11, 2026
Merged
I-ALiRT - add extension#297laspsandoval merged 2 commits intoIMAP-Science-Operations-Center:mainfrom
laspsandoval merged 2 commits intoIMAP-Science-Operations-Center:mainfrom
Conversation
Contributor
Author
|
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
Contributor
|
Would it be reasonable to import/export it as a CSV? |
Contributor
Author
I thought of that, but it would require a code change for imap_processing and sds-data-manager. I had already assumed .xlsx |
maxinelasp
approved these changes
Mar 11, 2026
laspsandoval
merged commit e3ff5db
into
IMAP-Science-Operations-Center:main
16 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change Summary
Overview
Goonhilly (UKSA) sent us a schedule. I would like to keep it in the same place that I keep the DSN schedules in sds-data-acct # bucket. I will give it an appropriate naming convention and then download it when I creating the ground station coverage schedule.