 
 
MGS Spacecraft Sequence EK file
==============================================================================
 
   This file was made using SPICE utility program PEF2EK by converting
   complete integrated and updated with real time commands MGS Spacecraft
   Sequence Predicted Events File (PEF file) created by MSOP SEQ team at
   JPL, in to SPICE EK sequence format.
 
 
File Contents
------------------------------------------------------------------------------
 
   This MGS Spacecraft Sequence EK file contains complete set of command,
   spacecraft activity, ground event and 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 MGS SPICE kernels
------------------------------------------------------------------------------
 
   The information contained in the data tables of this file maybe used
   together with the corresponding descriptions contained in the MGS command,
   spacecraft activity and ground event dictionary EK files 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.
 
 
MGS Sequence EK Data Tables Structure
------------------------------------------------------------------------------
 
   This file contains five data tables having the following structure:
 
     Command data table -- MGS_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)
 
     Activity data table -- MGS_ACT:
     -------------------------------
 
           TIME              TIME
 
           ACTIVITY          CHARACTER*(*)
 
           ATTRIBUTE_NAME    CHARACTER*(*)
 
           CHR_VALUE         CHARACTER*(*)
 
           DP_VALUE          DOUBLE PRECISION
 
           INT_VALUE         INTEGER
 
           VALUE_FLAG        CHARACTER*(*)
 
           ENTRY_ID          CHARACTER*(*)
 
           ATTRIBUTE_INDEX   INTEGER
 
     Ground events data table -- MGS_GEV:
     ------------------------------------
 
           TIME              TIME
 
           GROUND_EVENT      CHARACTER*(*)
 
           ATTRIBUTE_NAME    CHARACTER*(*)
 
           CHR_VALUE         CHARACTER*(*)
 
           DP_VALUE          DOUBLE PRECISION
 
           INT_VALUE         INTEGER
 
           VALUE_FLAG        CHARACTER*(*)
 
           ENTRY_ID          CHARACTER*(*)
 
           ATTRIBUTE_INDEX   INTEGER
 
     Status information data table -- MGS_STATUS:
     --------------------------------------------
 
           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
 
     Notes data table -- MGS_NOTE:
     -----------------------------
 
           TIME              TIME
 
           ATTRIBUTE_NAME    CHARACTER*(*)
 
           CHR_VALUE         CHARACTER*(*)
 
           ENTRY_ID          CHARACTER*(*)
 
           ATTRIBUTE_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.
 
           ACTIVITY          activity name. Activity names are taken from
                             an activity dictionary.
 
           GROUND_EVENT      ground event name. Ground event names are
                             taken from a ground event 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.
 
           ATTRIBUTE_NAME    attribute name. Attribute names are taken from
                             the activity and ground event dictionaries for
                             activities and ground events and are set to
                             some fixed values defined by PEF specification
                             for notes.
 
           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' or 'I' for activities,
                             ground events and statuses and 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, activity, ground event, 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.
 
           ATTRIBUTE_INDEX   index of the attribute in an activity, ground
                             event or note record from PEF file. For
                             commands activities and ground events this
                             index is the same as the index stored in the
                             corresponding 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, ACTIVITY, GROUND_EVENT, PARAMETER_NAME,
   PARAMETER_INDEX, ATTRIBUTE_NAME and ATTRIBUTE_INDEX columns in this file
   are consistent with the values in the same columns in the corresponding
   MGS 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 = MARS_GLOBAL_SURVEYOR;
SPACECRAFT_NAME = MARS_GLOBAL_SURVEYOR;
DATA_SET_ID = SEQ_PREDICTED_EVENTS;
FILE_NAME = c1102.u2.pef;
APPLICABLE_START_TIME = 1997-237T14:00:00.000;
APPLICABLE_STOP_TIME = 1997-245T14:00:00.000;
PRODUCT_CREATION_TIME = 1997-245T18:05:56;
PRODUCER_ID = SEQ;
SEQ_ID = c1102;
SOURCE_FILE_NAME = c1102.u2.sasf;
HOST_ID = mgseq2;
CCSD3RE00000$$MARK$$NJPL3IF0M01200000001;
$$MGS       PREDICTED EVENTS FILE
************************************************************
*PROJECT    MGS
*SPACECRAFT 94
*OPERATOR   mgs nipcec process,264-535,x37856
*DATE       Tue Sep  2 18:05:56 1997
*SEQ_GEN    V22.3 Tue Jun 10 14:08:44 PDT 1997
*BEGIN      1997-237T14:00:00.000
*CUTOFF     1997-245T14:00:00.000
*TITLE      c11 - TCM4
*Input files used:
*File Type  Last modified             File name
*SC_MODEL   Wed Aug 20 22:01:21 1997  /msop/seq/smf/mgs.L1.43.smf
*CATALOG    Wed Aug 20 22:01:35 1997  /msop/seq/satf/mgs.L1.33.satf
*RULES      Mon Jul  7 16:17:07 1997  /msop/seq/fmrf/mgs.L1.10.fmrf
*CONTEXT    Mon Jun 16 15:55:57 1997  /msop/seq/cvf/mgs.L1.19.cvf
*CONTEXT    Tue Sep  2 15:18:40 1997  /data1/mission/tcm4.cvf
*CONTEXT    Thu Aug 21 19:48:36 1997  /data1/dsn_config/soe_defaults.cvf
*CONTEXT    Thu Apr 24 14:50:56 1997  /data1/dsn_config/dsn_config.cvf
*CONTEXT    Mon Mar 10 17:42:15 1997  /msop/seq/cvf/DefaultUplinkBitRate_94.cvf
*LEGENDS    Mon Mar  3 19:02:36 1997  /msop/seq/legend/mgs.L1.1.legend
*CLOCK      Thu Aug 21 20:39:30 1997  /data1/sclk/MGS_SCLKSCET.00013
*LIGHTTIME  Thu Apr  3 20:43:19 1997  /data1/ltf/ltm_c_970129-970912_geo
*ALLOCATION Thu Aug 21 20:39:22 1997  /data1/alloc/c11upd.v1
*VIEW_FD    Thu Aug 21 19:48:53 1997  /data1/vue/view10.fd
*VIEWPERIOD Thu Aug 21 20:20:42 1997  /data1/vue/DSN_97210-97280_VP
*SEQUENCE   Tue Sep  2 18:05:56 1997  /data1/mission/c1102.u2.sasf
*CONDITIONS Tue Sep  2 15:09:27 1997  /data1/mission/c1003.u2.fincon
*EVENTS
*BG_SEQUENCE
*DEP_CONTEXT
*DEFINITION
*MASK
*GEOMETRY
*OPTG_FD
*TELEMETRY
*REQUESTS
*RESOLUTION
*SCRIPT
*REDUNDANT
************************************************************
$$
 
