JUICE SPK files ============================================================================== This ``aareadme.txt'' file describes the contents of the kernels/spk directory of the JUICE SPICE data server. It was last modified on February 9, 2024 by Rafael Andres Blasco, ESAC/ESA. Contact Information ----------------------------------------------------------------------------- If you have any questions regarding this file contact the ESA SPICE Service (ESS) at ESAC: Alfredo Escalante Lopez (+34) 91-8131-429 spice@sciops.esa.int or the JUICE Science Operations Center at ESAC: Marc Costa Sitja (+34) 646-746-711 Marc.Costa@ext.esa.int References and required readings ----------------------------------------------------------------------------- 1. ``SPK Required Reading'', NAIF Document 2. ``Juice Flight Dynamics ICD (PLID Annex A)'', JUI-ESOC-MOC-ICD-500, Issue 1, Revision 5, September 30, 2022. 3. ``JUICE SPICE Interface Control Document'', SPICE-JUICE-ICD-002, Issue 2, Revision 2, October 24, 2022. Brief Summary ----------------------------------------------------------------------------- This directory contains the SPICE SP-Kernel files for the JUICE mission, including mission analysis, nominal and operational spacecraft trajectory SPKs, generic planetary and satellite ephemerides SPKs, and JUICE structure and sensors' locations SPKs. File naming conventions ----------------------------------------------------------------------------- Naming Scheme for JUICE spacecraft SPKs: The naming scheme for the JUICE spacecraft SPKs is: juice_TYPE[_DESC][_ID][_YYMMDD_YYMMDD]_vNN.bsp where TYPE Data type, where a reference to the originator of the data, the type of data and the and the reference period is provided. The different types are: orbc S/C reconstructed and predicted cruise orbit from Flight Dynamics. orbm S/C reconstructed and predicted cruise orbit to which ATTM CKs are consistent to, from Flight Dynamics. crema Full mission test reference trajectory based on a crema document issue from Mission Analysis. crema_plan Full mission test reference trajectory based on a crema document issue from Mission Analysis trim for start date matching with orbc Flight Dynamics trajectory. mat_crema Full mission test reference trajectory based on a crema document issue from Mission Analysis (old reference); DESC description of the original reference file (optional); ID Mapping to the original file product IDs as defined per an ICD document ([2] and [3]) (optional); YYMMDD coverage start and stop times in TDB (optional); NN version number, starting from 01 (required; e.g. 01); Naming Scheme for Generic Planetary Ephemeris SPKs The naming scheme for generic planetary SPKs is: deNNN.bsp where NNN DE version (required; e.g. 421); Naming Scheme for Generic Satellite Ephemeris SPKs The naming scheme for generic satellite SPKs is: jupNNN[_EXTRA].bsp where NNN satellite ephemeris number (required; e.g. 230); EXTRA additional information token (optional; e.g. _minor); Naming Scheme for JUICE Structure Locations SPKs The naming scheme for JUICE structure locations SPKs is: juice_struct_vNN.bsp where NN version number (required); If multiple versions of a JUICE structures SPK file are provided, always use the latest version (unless an earlier version is needed for some special reasons.) Naming Scheme for JUICE Structure Internal Locations SPKs The naming scheme for JUICE structure internal locations SPKs is: juice_struct_internal_vNN.bsp where NN version number (required); If multiple versions of a JUICE structures SPK file are provided, always use the latest version (unless an earlier version is needed for some special reasons.) Other directory contents ----------------------------------------------------------------------------- aareadme.txt This file. Particulars ----------------------------------------------------------------------------- Nothing to report. Kernel File Details ----------------------------------------------------------------------------- The most detailed description of the data in a binary SPK file is provided in metadata included inside the comment area of the file. This information can be viewed using the utility programs COMMNT and SPACIT included in the NAIF Toolkit. End of aareadme file.