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

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

<sddl>

<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<!-- -->
<!--  SDDL Name:  MSC_SLEW_SLOT.SDDL -->
<!-- -->
<!--  Purpose:      This SDDL file defines the MSC_SLEW_SLOT relation.-->
<!-- -->
<!--  Modification History:-->
<!-- -->
<!--    Date       OPR      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_SLEW_SLOT_TYPE"> 
 
        <description>This relation is used to contain the details of msc_events
                   of type RTO and class GEN taken from the MSC GEN-SLEW 
                   block. </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 obset. </description>
            </field>

            <field name="program_id">
                    <type>C3</type>
                    <units>BASE_36</units>
                    <description>When a proposal is accepted into the PMDB by SPSS it must
		    be assigned a unique 3 character base 36 program identifier.
		    This is done by the PMDB/ACCEPT_PROP command.
                    It is used for identification of proposals by spacecraft 
                    and OPUS software. It is also used in the OPUS and DADS 
                    rootname for all archived science data files. 
                    Because of flight design software, program_id must be
                    three characters. </description>
            </field>

            <field name="obset_id">
                    <type>C2</type>
                    <units>BASE_36</units>
                    <description>An observation set is a collection of one or more 
		    alignments that are grouped together based on FGS pointing 
		    requirements.  That is, if multiple alignments can all be 
		    executed using the same guide star pair, they are grouped
		    into the same observation set. </description>
            </field>

            <field name="slot">
                    <type>C3</type>
                    <description>Slot number</description>
            </field>

            <field name="load_by">
                    <type>C17</type>
                    <description>YYYY.DDD:HH;MM:SS - load by date</description>
            </field>

            <field name="max_slew">
                    <type>C3</type>
                    <description>formatted as integer arcsec - maximum slew angle</description>
            </field>

            <field name="offset_id">
                    <type>C13</type>
                    <description>An identified used in the SPSS database</description>
            </field>
    </record>
 
 
 
    <relation name="msc_slew_slot">
 
        <type>MSC_SLEW_SLOT_TYPE</type>

        <description>RTO GEN data from MSC file</description>

        <subsystem_using>OPUS</subsystem_using>

        <index name="msc_slew_slot_1">
                <type>unique clustered</type>
                <field name="event_time"/>
            <field name="program_id"/>
            <field name="obset_id"/>
            <field name="slot"/>
        </index>

        <index name="msc_slew_slot_2">
                <type>nonclustered</type>
                <field name="program_id"/>
            <field name="obset_id"/>
            <field name="slot"/>
        </index>

    </relation>
</sddl>
