-
Notifications
You must be signed in to change notification settings - Fork 35
MAG L1C: continue previous day's timeline across the day boundary #3323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sapols
wants to merge
7
commits into
IMAP-Science-Operations-Center:dev
Choose a base branch
from
sapols:mag-l1c-day-boundary-2925
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
485f56e
Adding MAG L1C day boundary tests
maxineofficial ac9fdb5
MAG L1C: continue previous day's timeline across the day boundary (#2…
sapols 9e5c39b
MAG L1C: harden previous-day handling per independent review
sapols 33faa5d
MAG L1C tests: compare timestamps at 1 us precision per MAG expectations
sapols e4fd2fb
MAG L1C: address day-boundary PR review feedback
sapols 8f49ade
MAG L1C: take the previous-day timeline from the previous day's L1C
sapols f4cff7e
MAG L1C tests: fix stale comment - previous-day file is the L1C
sapols File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find this method to be confusingly named and very verbosely commented to the point of confusion. Suggest you get your AI code writing companion to dial down the verbosity a bit.
I think this method is just getting the last vector timestamp from the previous day and the rate of vector generation?
So call it that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lol yeah fair, noted on the verbosity. Some comment verbosity is unavoidable because our numpydoc pre-commit hook requires full summary/Parameters/Returns scaffolding on every function. But it's still on me to avoid over-explaining inside that scaffolding. In this case, most of it existed to justify the confusing shifted return value which your simplification in the next thread eliminated. Renamed to your suggested
_get_last_timestamp_and_rate_from_previous_day_in_nsand cut the docstring down (e4fd2fb); it now does exactly what the name says. I'll keep the prose dialed down going forward.