-
Notifications
You must be signed in to change notification settings - Fork 16
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
CoDICE: Calculate epoch values from acq_start_seconds instead of shcoarse #1262
base: dev
Are you sure you want to change the base?
CoDICE: Calculate epoch values from acq_start_seconds instead of shcoarse #1262
Conversation
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 just have the one double check comment. Otherwise this is good to go!
imap_processing/codice/codice_l1a.py
Outdated
epoch : NDArray[int] | ||
List of epoch values. | ||
""" | ||
epoch = met_to_j2000ns(self.dataset.acq_start_seconds) |
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.
Just to double check... acq_start_seconds
records the spacecraft clock coarse ticks (seconds) at acquisition start time and there is no sub-seconds field? If both of those things are true, this looks like the correct implementation to me.
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.
After discussing with Joey, there is indeed a sub-seconds field that I will have to implement, so I will update that. acq_start_seconds
does indeed record the S/C clock coarse ticks at acquisition time.
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.
@subagonsouth Could you give this another look any make sure I am thinking about this correctly? It is a bit tricky since acq_start_seconds
is in units of seconds and acq_start_subseconds
is in units of microseconds, so I think I need to do a small conversion before calculating epoch
.
Change Summary
Overview
This PR adds a function to calculate epoch values from
acq_start_seconds
field instead of the defaultshcoarse
field, as per request from CoDICE instrument team. The function may also be expanded in the future to support other time keys if needed.Updated Files
imap_processing/codice/codice_l1a.py