<?xml version="1.0" encoding="UTF-8"?>

<!-- <!DOCTYPE sddlschema SYSTEM "sddlschema.xsd">-->

<sddl>

<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<!-- -->
<!--  SDDL Name:  MSC_EVENTS.SDDL -->
<!-- -->
<!--  Purpose:      This SDDL file defines the MSC_EVENTS relation.-->
<!-- -->
<!--  Modification History:-->
<!-- -->
<!--    Date       PR      Who                       Reason-->
<!--  - - - -    - - - -   - -    - - - - - - - - - - - - - - - - - - - - - -->
<!--  05/31/00   44862     Baum   Original implementation-->
<lm>  07/03/03   48821     CTB   Converted to XML format </lm> <!-- last mod -->
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
 

    <record name="MSC_EVENTS_TYPE"> 
 
 
        <description>This relation is used to contain the events of interest to
                   FGS processing that are extracted from the mission schedule,
                   the MSC file.</description>


            <field name="event_time">
                    <type>C20</type>
                    <description>YYYY.DDD.HH.MM.SS.CC the time within a hundreth of
                         a second for each event. </description>
            </field>

            <field name="event_type">
                    <type>C3</type>
                    <description>OPS for operational info; FGS for jitter; RTI for PCS 
                         events; RTO for offset slot data; TDR for TDRSS
                         COMCON events.</description>
                         

            </field>

            <field name="event_class">
                    <type>C5</type>
                    <description>      for OPR type classes
                               --------------------

                          BOM   begin mission schedule
                          EOM   end mission schedule

                               for FGS type classes
                               --------------------
                         
                          BOSn  begin slew of type n (n=1 to 4)
                          PCP   Pointing Control Processor
                          ORBIT related to HST orbit
                          BOA   begin GS acquisition or reacquisition
                          EOA   end GS acquisition or reacquisition

                                for RTI type classes
                                --------------------

                          EOS2  end slew of type 2
                          FHST3 fhst - start of 3-axis update
                         
                                for RTO type classes
                                --------------------
 
                          GEN   generate offset slot
                          REUSE reuse offset slot
                          SET   set offset slot
                          CLEAR clear offset slot

                                for TDR type classes
                                --------------------

                          BOC   begin COMCON
                          EOC   end COMCON
                          BRC   begin rejected COMCON
                          ERC   end rejected COMCON
                          BTC   begin trimmed COMCON
                          ETC   end trimmed COMCON </description>
            </field>

            <field name="event_name">
                    <type>C10</type>
                    <description>Format     Description
                         ---------- --------------------------------------
                         mmmmmmmmm  9-char MSC rootname for BOM and EOM
                         aaaaaaaaaa 10-char aperture name for BOSn,or EOS2
                         TERMINATE  PCP state
                         GYRO       PCP state
                         FGS_OCCULT PCP state
                         SAA        PCP state
                         ENTR_DAY   entering ORBIT day 
                         ENTR_NIGHT entering ORBIT night
                         GSACQ1     first acquisition for BOA and EOA
                         GSACQ2     second acquisition for BOA and EOA
                         REACQ      reacquisition for BOA and EOA
                         S_ss_pppoo RTO: ss is slot num, pppoo is obset
                         pppoo_ssss TDR: pppoo is obset, ssss is service </description>
            </field>

    </record>
 
  
 
    <relation name="msc_events">
 
        <type>MSC_EVENTS_TYPE</type>

        <description>Mission Schedule Events</description>

        <subsystem_using>OPUS</subsystem_using>

        <index name="msc_events_1">
            <type>unique clustered</type>
            <field name="event_time"/>
            <field name="event_type"/>
            <field name="event_class"/>
            <field name="event_name"/>
        </index>

    </relation>
</sddl>
