 
 
SDU Spacecraft Sequence EK file
==============================================================================
 
   This file was made using SPICE utility program PEF2EK by converting
   complete integrated SDU Spacecraft Sequence Predicted Events File
   (PEF file) created by SDU Spacecraft team at LMA, in to SPICE EK
   sequence format.
 
 
File Contents
------------------------------------------------------------------------------
 
   This SDU Spacecraft Sequence EK file contains complete set of
   command and, optionally, spacecraft subsystem status information
   along with notes found in the original PEF file from which it was
   generated. See Appendix 1 for complete SDFU and config record of the
   original PEF file.
 
 
Usage
------------------------------------------------------------------------------
 
   The data in the file may accessed via SPICE Toolkit EK subroutines
   or examined using SPICE utility program INSPEKT.
 
 
Associated SDU SPICE kernels
------------------------------------------------------------------------------
 
   The information contained in the command data table of this file
   maybe used together with the corresponding descriptions contained in
   the SDU command dictionary EK file when accessed through the EK
   subroutines or INSPEKT.
 
   SPICE EK subsystem requires a leapsecond kernel file (LSK file) to
   be loaded into a program in order to support queries on the EK files
   containing tables that include columns of type TIME.
 
 
SDU Sequence EK Data Tables Structure
------------------------------------------------------------------------------
 
   This file contains five data tables having the following structure:
 
     Command data table -- SDU_CMD:
     ------------------------------
 
           TIME              TIME
 
           COMMAND           CHARACTER*(*)
 
           PARAMETER_NAME    CHARACTER*(*)
 
           CHR_VALUE         CHARACTER*(*)
 
           DP_VALUE          DOUBLE PRECISION
 
           INT_VALUE         INTEGER
 
           VALUE_FLAG        CHARACTER*(*)
 
           ENTRY_ID          CHARACTER*(*)
 
           PARAMETER_INDEX   INTEGER
 
           LONG_VALUE        CHARACTER*(*)(VSA)
 
     Notes data table -- SDU_NOTE:
     -----------------------------
 
           TIME              TIME
 
           ATTRIBUTE_NAME    CHARACTER*(*)
 
           CHR_VALUE         CHARACTER*(*)
 
           ENTRY_ID          CHARACTER*(*)
 
           ATTRIBUTE_INDEX   INTEGER
 
     Status information data table -- SDU_STATUS (this table is optional):
     ---------------------------------------------------------------------
 
           TIME              TIME
 
           SUBSYSTEM         CHARACTER*(*)
 
           PARAMETER_NAME    CHARACTER*(*)
 
           CHR_VALUE         CHARACTER*(*)
 
           DP_VALUE          DOUBLE PRECISION
 
           INT_VALUE         INTEGER
 
           VALUE_FLAG        CHARACTER*(*)
 
           ENTRY_ID          CHARACTER*(*)
 
           PARAMETER_INDEX   INTEGER
 
   column definitions are as follows:
 
           TIME              time of the entry from PEF file.
 
           COMMAND           command name. Command names are taken from a
                             command dictionary.
 
           SUBSYSTEM         subsystem name. Subsystem names are taken from
                             corresponding record of PEF file.
 
           PARAMETER_NAME    parameter name. Parameter names are taken from
                             the command dictionary for commands and from
                             corresponding PEF record for statuses.
 
           CHR_VALUE         value of the parameter or attribute in a
                             character string.
 
           DP_VALUE          value of the parameter or attribute in a DP
                             number (if character string could be parsed as
                             a DP number)
 
           INT_VALUE         value of the parameter or attribute in a INT
                             number (if character string could be parsed as
                             an INT number).
 
           VALUE_FLAG        single character flag showing which values are
                             present for current parameter or attribute. It
                             can be set to 'C', 'D', 'I' or 'A' for
                             commands. These values stand for: 'C' --
                             only character value is available. 'D' --
                             character and DP values are available. 'I'
                             -- character, DP and INT values are
                             available. 'A' -- only "long value" is
                             available.
 
           ENTRY_ID          character string which has the same value for
                             all EK table records representing a single
                             command, subsystem status or note record
                             from PEF file. Constructed as <PEF SEQ
                             ID>:<CMD line number in PEF file>. If <PEF
                             SEQ ID> string wasn't available from PEF
                             file header, it's replaced with some
                             random string that will be the same for
                             all records from a single PEF file.
 
           PARAMETER_INDEX   index of the parameter in a command or status
                             record from PEF file. For commands this index
                             is the same as the index stored in the command
                             dictionary.
 
           LONG_VALUE        character string array containing a
                             "80-characters" wrapped long character value
                             that couldn't fit into CHR_VALUE. To get real
                             parameter value from this array all array
                             elements must be concatenated together.
 
 
   An original PEF record of a particular type is represented by a few
   records in the corresponding data table in this EK file. Value of the
   ENTRY_ID column the same for all records which were generated from a
   single PEF record and, therefore, it can be used to group them together.
 
   The values in COMMAND, PARAMETER_NAME, and PARAMETER_INDEX columns
   in this file are consistent with the values in the same columns in
   the corresponding SDU dictionary EK files and therefore sequence and
   dictionary tables can be joined in EK queries using these columns as
   a keys.
 
 
Contact Information
------------------------------------------------------------------------------
 
   If you have any questions regarding information or use of this file
   contact
 
   Boris V. Semenov, NAIF/JPL
   at:      JPL MS 301-125L
            (818)-354-8136
            Boris.Semenov@jpl.nasa.gov
 
 
Appendix 1: SDFU and Config Record of the Original PEF File.
==============================================================================
 
 
CCSD3ZF0000100000001NJPL3KS0L015$$MARK$$;
MISSION_NAME = STARDUST;
SPACECRAFT_NAME = STARDUST;
DATA_SET_ID = SEQ_PREDICTED_EVENTS;
FILE_NAME = sc089b.pef;
APPLICABLE_START_TIME = 2005-333T16:00:00.000;
APPLICABLE_STOP_TIME = 2005-360T00:30:00.000;
PRODUCT_CREATION_TIME = 2005-318T21:28:18;
PRODUCER_ID = SEQ;
SEQ_ID = sc089b;
SOURCE_FILE_NAME = sc089b.seqgen.sasf;
HOST_ID = sdseq1d;
CCSD3RE00000$$MARK$$NJPL3IF0M01200000001;
$$SDU       PREDICTED EVENTS FILE
************************************************************
*PROJECT    SDU
*SPACECRAFT 29
*OPERATOR   SDU SEQ Team Account
*DATE       Mon Nov 14 21:28:18 2005
*SEQ_GEN    V27.3 Thu May 6 07:38:56 PDT 2004
*BEGIN      2005-333T16:00:00.000
*CUTOFF     2005-360T00:30:00.000
*TITLE      sc089b
*Input files used:
*File Type  Last modified             File name
*SC_MODEL   Thu Jul 28 22:47:01 2005  /export/MSOP/J2.0-MMO/seq/smf/Stardust.4.0.3.5.smf
*CATALOG    Wed May 12 16:42:36 2004  /export/MSOP/J2.0-MMO/seq/satf/Stardust.4.0.3.2.satf
*RULES      Wed May 31 00:02:53 2000  /export/MSOP/J2.0-MMO/seq/fmrf/Stardust.A6.fmrf
*LEGENDS    Mon Mar 10 23:27:25 1997  /export/MSOP/J2.0-MMO/seq/legend/Stardust.A0.legend
*CONTEXT    Wed Jul 21 23:37:09 2004  /export/MSOP/J2.0-MMO/seq/cvf/msop.gvs.cvf
*CONTEXT    Tue Mar  1 23:25:49 2005  /export/MSOP/J2.0-MMO/seq/cvf/Stardust.A23.cvf
*CONTEXT    Thu Feb 13 14:16:56 2003  /home/acheuvro/SEQUENCES/seq_data/msop.soe.cvf
*CONTEXT    Mon Apr 21 19:28:05 2003  /export/MSOP/J2.0-MMO/seq_rw/seq_config/dsn_config/msop.dsn.cvf
*CONTEXT    Wed Nov  2 15:25:42 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_data/cruise/sdu/c89/soe_defaults_29.cvf
*CONTEXT    Fri Nov 11 16:50:38 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_config/dsn_config/dsn_config.cvf
*CLOCK      Mon Nov  7 21:24:52 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_input/sclk/SD_SCLKSCET.00139
*LIGHTTIME  Tue Sep 27 22:06:45 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_input/ltf/SDU_050511_060115_V01.ltf
*ALLOCATION Wed Nov  2 15:17:15 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_input/alloc/SDU_05333_05359.SAF
*VIEW_FD    Wed Dec 19 15:50:42 2001  /export/MSOP/J2.0-MMO/seq_rw/seq_input/vue/view10.fd
*VIEWPERIOD Wed Apr 20 22:27:30 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_input/vue/SDU_05052_06090.VP
*SEQUENCE   Mon Nov 14 21:28:19 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_data/cruise/sdu/c89/sc089b.seqgen.sasf
*CONDITIONS Wed Nov  2 19:24:13 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_data/cruise/sdu/c89/sc088b.fincon
*BG_SEQUENCEFri Nov 11 21:22:43 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_data/cruise/sdu/c89/sc089b_cond.sasf
*BG_SEQUENCEWed Nov  2 19:16:35 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_data/cruise/sdu/c89/fsw_diag_monthly_blk.sasf
*BG_SEQUENCEWed Nov  2 19:16:19 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_data/cruise/sdu/c89/fsw_diag_dir_dumps_blk.sasf
*BG_SEQUENCEWed Nov  2 23:36:13 2005  /export/MSOP/J2.0-MMO/seq_rw/seq_data/cruise/sdu/c89/set_non_std_dl_rate.sasf
*CAT_NO_VML
*DEFINITION
*DEP_CONTEXT
*EVENTS
*MASK
*OPTG_FD
*GEOMETRY
*REDUNDANT
*REQUESTS
*RESOLUTION
*SCRIPT
*TELEMETRY
*TYPEDEF
************************************************************
$$EOH
 
 
