JUNO SPICE Kernel Naming Scheme
===========================================================================
 
     CHA&BVS/NAIF, September 24, 2009.
 
 
CK
===========================================================================
 
     Naming scheme for all CKs:
 
           juno_INST_TYPE_YYMMDD_YYMMDD[_EXTRA]_vNN.bc
 
     where
 
           INST     structure identifier (required):
 
                       sc      for spacecraft
 
                       sa      for solar arrays
 
                       asc1    for ASC1
 
                       asc2    for ASC2
 
                       asc3    for ASC3
 
                       asc4    for ASC4
 
                       sc2asc  for spacecraft-to-ASC alignment
 
                       asc2mob for ASC-to-MOB alignment
 
                       uvs     for UVS
 
           TYPE     data type identifier (required):
 
                       nom     for nominal data based on planned
                               attitude profile
 
                       nom*    for nominal for a particular position
                               (e.g. nom0, nomp30, nomm30, etc.)
 
                       prl     for long-term prediction, made from
                               .drf delivered five weeks in advance
                               covering two orbits
 
                       prs     for short-term prediction, made from
                               .drf delivered eight days in advance
                               covering one orbit
 
                       raw     for telemetry-based (the need,
                               frequency, and coverage are TBD)
 
                       rec     for reconstruction, based on .drf
                               delivered up to seven days later
                               covering one orbit
 
                       tst     for test data
 
           YYMMDD   coverage start and stop UTC/SCET (required);
 
           EXTRA    additional information token (optional; e.g. _tcm1);
 
           NN       version number (required);
 
 
FK
===========================================================================
 
     Naming scheme for FKs:
 
           juno_vNN.tf
 
     where
 
           NN       version number (required);
 
 
IK
===========================================================================
 
     Naming scheme for IKs:
 
           juno_INST_vNN.ti
 
     where
 
           INST     instrument identifier (required):
 
                       jade    for JADE
                       jedi    for JEDI
                       jiram   for JIRAM
                       junocam for JUNOCAM
                       mag     for FGM, ASC
                       mwr     for MWR
                       struct  for SRU, SSSs, antennas, REMs
                       uvs     for UVS
                       waves   for WAVES
 
           NN       version number (required);
 
 
LSK
===========================================================================
 
     Naming scheme for generic LSKs:
 
           naifNNNN.tls
 
     where
 
           NNNN     version number (required)(e.g. 0009);
 
 
PCK
===========================================================================
 
     Naming scheme for generic PCKs:
 
           pckNNNNN.tpc
 
     where
 
           NNNNN    version number (required)(e.g. 00008);
 
     Naming scheme for JUNO-project PCKs:
 
           TBD
 
 
SCLK
===========================================================================
 
     Naming scheme for SCLKs:
 
           JNO_SCLKSCET.NNNNN.tsc
 
     where
 
           NNNNN    version number (required)(e.g. 00001);
 
     Note: The "JNO" here is uppercase and just three letters due to the
     LMCO SCLKvSCET source file name.
 
 
SPK
===========================================================================
 
 
Pre-launch Reference SPKs by MD
--------------------------------------------------------
 
     Naming scheme for nominal pre-launch SPKs produced by Mission Design:
 
           TBD
 
 
Ops SPKs by NAV
--------------------------------------------------------
 
     Naming scheme for operations SPKs produced by NAV:
 
           spk_TYP_YYMMDD_YYMMDD_yymmddV[_EXTRA].bsp
 
     where
 
           TYP      data type identifier (required):
 
                       ref     reference trajectory
 
                       pre     predict, with the upcoming maneuver
                               modeled
 
                       nob     predict, without the upcoming maneuver
                               modeled
 
                       rec     reconstruction
 
           YYMMDD   coverage start and STOP UTC/SCET (required);
 
           yymmdd   file release date (required);
 
           EXTRA    additional information token (optional; up to 8
                    characters including underscore; e.g. _tcm1);
 
     Note: file naming scheme is as specified by the NAV producers. They
     were willing to change an earlier hyphen to an underscore (the
     character between the START and STOP times).
 
 
Merged, Ever-growing SPKs by NAIF
--------------------------------------------------------
 
     Naming scheme for merged, ever-growing SPKs for orbital phase:
 
           juno_TYPE_orbit.bsp
 
     where
 
           TYPE     data type (required):
 
                       rec     for reconstructed
                       pred    for predicted
 
 
Planetary SPKs by NAIF
--------------------------------------------------------
 
     Naming scheme for planetary SPKs:
 
           deNNN.bsp
 
     where
 
           NNN      DE version (required; e.g. 421);
 
 
Satellite SPKs by NAIF
--------------------------------------------------------
 
     Naming scheme for satellite SPKs:
 
           jupNNN[_EXTRA].bsp
 
     where
 
           NNN      satellite ephemeris number (required; e.g. 230);
 
           EXTRA    additional information token (optional; e.g. _rocks);
 
 
Structure SPKs by NAIF
--------------------------------------------------------
 
     Naming scheme for structure locations SPKs:
 
           juno_struct_vNN.bsp
 
     where
 
           NN       version number (required);
 
 
ORBNUM
===========================================================================
 
 
ORBNUM for Nominal SPKs
--------------------------------------------------------
 
     Naming scheme for ORBNUM files based on nominal MD SPKs:
 
           SPKNAME.orb
 
     where
 
           SPKNAM   name of the ``parent'' SPK file;
 
 
ORBNUM for Merged, Ever-growing SPKs
--------------------------------------------------------
 
     Naming scheme for merged, ever-growing ORBNUM files for orbital phase:
 
           juno_TYPE_orbit.orb
 
     where
 
           TYPE     data type (required):
 
                       rec     for reconstructed
                       pred    for predicted
 
 
SFF
===========================================================================
 
     Naming scheme for reconstructed SFF files for science:
 
           juno.sff