You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We only want historical attitude kernels delivery following each track (3/wk)
Make certain it does not start with imap_pred_ (only imap_)
Historical attitude naming convention is imap_yyyy_doy_yyyy_doy_##.ah.bc
Ephemeris
Reconstructed delivered 1/wk
nom is least ideal (after burn and pred)
Ephemeris naming convention is imap_nom_yyyymmdd_yyyymmdd_v##.bsp
Reprocessing (future requirements to keep in mind - not for this task)
We will need to reproduce our data product. The kernel names used in each data product will be recorded in the RDS. We will need to have a way to not use only the latest.
The start of the attitude and ephemeris kernels will be "cut out" after a period of time after it becomes too large. How will this affect reprocessing?
Related tickets
No response
The text was updated successfully, but these errors were encountered:
Summary
We are currently using an EFS mount. Details of how kernels are delivered may be found pg 17 of 7516-9163 MOC Data Products Guide:
https://confluence.lasp.colorado.edu/display/IMAP/IMAP+POC+External+Reference+Documents
Requirements
Attitude
Ephemeris
Reprocessing (future requirements to keep in mind - not for this task)
Related tickets
No response
The text was updated successfully, but these errors were encountered: