PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT INTERCHANGE_FORMAT = ASCII PUBLICATION_DATE = 2010-08-30 NOTE = "LRO E-Kernel Information" END_OBJECT = TEXT END General Information About SPICE E-Kernels ========================================= The purpose of the Events (E) -kernel is to store different kinds of the spacecraft and science instrument events related information such as spacecraft and instrument commands, status parameters, records of spacecraft activities, ground events, and so on, and to systematize and provide access to this data in relational data base -like fashion. The means of an access to the EK data are provided via SPICE Toolkit APIs, calls to which can be integrated into user application programs. The information regarding how to obtain the SPICE system toolkit for a number of languages and computer platforms is located in the ``/software'' subdirectory of the main directory of this data set. To use E-kernels with INSPEKT program, a Leapseconds (LSK) is required. Refer to the ``ek.req'' and ``inspekt.ug'' documents provided with the toolkit to get more information on how to access E-kernel data. LRO E-kernels Provided in This Data Set ======================================= The Events Kernel is a Binary-formatted file that consists of the complete set of event sequences (in sequential time-order) when any instrument is not collecting science data, such as during spacecraft station keeping maneuvers. The LRO Event kernel is intended to provide current and future users of LRO science data information on events and activities that affected science data collection and that can assist in extracting the full value of the science data returned from the LRO mission. The events documented by the event kernel can be planned or unplanned. Some examples of planned events might be: - halting data collection for slews or calibrations; - delta-v maneuvers; - loading a FSW patch; - recovery from non-nominal modes such as safe mode. Some examples of unplanned events might be: - an anomaly resulting in the orbiter transitioning to safe mode or powering down instruments; - instrument anomaly. The information for the event kernel will come primarily from one source: - The LRO telemetry and command (T&C) system event message log; The event kernel is generated by an automated process within the LRO Mission Operations Center (MOC). The LRO Event Kernel Utility runs once per week at 0000Z on Monday. The Utility scans the T&C logs for appropriate information to be included in the event kernel. The LRO mission operations team has the responsibility for determining which information is appropriate and configuring the LRO Event Kernel Utility accordingly. File Name Convention ==================== The LRO EKs are named as follows: ___. where File Designator = [7 characters] token identifying the file; is "lroevnt" to indicate this is the Events Kernel; followed by the underscore (_) character. Start Date = [7 characters], YYYYDOY; represented in UTC format and followed by underscore(_); where YYYY => 4 ASCII digits of year ("2008"-"2013") DOY => 3 ASCII digits for day of year ("001"-"366") identifies the start date for the data contained within the file. Stop Date = [7 characters], YYYYDOY; represented in UTC format and followed by underscore(_); where YYYY => 4 ASCII digits of year ("2008"-"2013") DOY => 3 ASCII digits for day of year ("001"-"366"); identifies the stop date for the data contained within the file. version number = [3 characters] v, followed by a two-digit version number. The initial version is 00, next is 01 ... up to 99. file extension = [3characters] Standard file extension for the binary sequence LRO Event Kernel file "bes". Contact Information =================== Regarding Lunar Reconnaissance Orbiter project specific information provided in this data set contact: Rick Saylor (301)-614-1354 Richard.S.Saylor@nasa.gov address: NASA Goddard Space Flight Center (GSFC) Mail Stop 451.0 Building 12 Room N233 Greenbelt MD 20771