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

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

<sddl>

<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<!-- -->
<!--  SDDL Name:  AST_JITTER_KW.SDDL -->
<!-- -->
<!--  Purpose:      This SDDL file defines the AST_JITTER_KW relation.-->
<!-- -->
<!--  Modification History:-->
<!-- -->
<!--    Date       PR      Who                       Reason -->
<!--  - - - -    - - - -   - -    - - - - - - - - - - - - - - - - - - - - - -->
<!--  03/12/01   44862     Baum   Original implementation-->
<lm>  07/03/03   48821     CTB   Converted to XML format </lm> <!-- last mod -->
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
 
    <record name="AST_JITTER_KW_TYPE"> 

 
        <description>"This relation is used to provide data calculted by the
                   JITTER process to the AST pipeline. The data is in the form
                   of named keyword values. For flexibility, this table allows
                   an arbitrary number of keywords to be accessed by the
                   programmattic IDs of the astrometry dataset. "</description>


            <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 or pmdb -load.
                    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="ob_number">
                    <type>C2</type>
                    <units>BASE_36</units>
                    <description>"Observations are numbered sequentially throughout
                    an observation set and are assigned by SMS/Gen.
                    An ob_number is _NOT_ the same as an obset_ID. "</description>
            </field>

            <field name="keyword_name">
                    <type>C8</type>
                    <description>"The name of the keyword for has the keyword_value."</description>
            </field>

            <field name="keyword_value">
                    <type>C68</type>
                    <description>"The value of the keyword_name. The longest string 
                    allowed by FITS is 68 characters. Most keywords have values
                    that are less than 20 characters. "</description>
            </field>

    </record>
 
 
 
    <relation name="ast_jitter_kw">
 
        <type>AST_JITTER_KW_TYPE</type>

        <description>AST keywords supplied by JITTER calculations.</description>

        <subsystem_using>OPUS</subsystem_using>

        <index name="ast_jitter_kw_1">
            <type>unique clustered</type>
            <field name="program_id"/>
            <field name="obset_id"/>
            <field name="ob_number"/>
            <field name="keyword_name"/>
        </index>

    </relation>
</sddl>
