!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! SDDL Name:	JITTER_EVT_MAP.SDDL
!
! Purpose:      This SDDL file defines the JITTER_EVT_MAP relation.
!
! Modification History:
!
!   Date       OPR      Who                       Reason
! --------   -------    ----   ------------------------------------------------
! 11/30/00    44862     Baum   Original implementation
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
!
 
LANGUAGE	SQL

RECORD  JITTER_EVT_MAP_TYPE
 
!------------------------------------------------------------------------------
!
!   RECORD INFORMATION
!
!------------------------------------------------------------------------------
 
 
DESCRIPTION       "This relation is used to identify the all the jitter
                   datasets that follow either the SMS start event or the GS
                   acquisition event, identified by event time. The event_type
                   specifies whether the event_start_time is for an SMS or a GS
                   acquisition. If the event is an acquisition, then the 
                   evt_start_time will exactly match the acq_start_time in the
                   gsa_data table. This table is also used to identify internal
                   exposures that do not need engineering telemetry for its 
                   defaulted jitter files. The table was designed to be easily 
                   joined to qolink_sms to get exposure status so that jitter
                   files are not generated for exposures have a status of N. "

!------------------------------------------------------------------------------
!
!   FIELD INFORMATION
!
!------------------------------------------------------------------------------

    FIELD  event_start_time
        TYPE        C17
        DESCRIPTION "YYYY.DDD:HH:MM:SS, Start time of event. If event_type is
                    G for GSACQ then this time must match the acq_start_time
                    in the gsa_data table and it can be used to join to that
                    table. " 

    END_FIELD


    FIELD  event_type
        TYPE        C3
        DESCRIPTION "(SMS or GSA)  SMS start or GS acquisition start. "
    END_FIELD

    FIELD program_id
        TYPE        C3
        UNITS	    "BASE_36"
        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. "
    END_FIELD

    FIELD obset_id
        TYPE        C2
        UNITS	    "BASE_36"
        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. "
    END_FIELD

    FIELD ob_number
        TYPE        C2
        UNITS	    "BASE_36"
        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. "
    END_FIELD

    FIELD internal_flag
        TYPE        C1
        DESCRIPTION "(Y or N) Y indicates this is a internal observation. "
    END_FIELD

END_RECORD
 
 
!------------------------------------------------------------------------------
!
!   RELATION DECLARATION
!
!------------------------------------------------------------------------------
 
 
RELATION  jitter_evt_map
 
    TYPE             JITTER_EVT_MAP_TYPE
 
    DESCRIPTION      "FGS-jitter-dataset to MSC-event Mapping Relation"
 
    SUBSYSTEM_USING  "OPUS"

    INDEX  jitter_evt_map_1
        TYPE         unique, clustered
        FIELDS       event_start_time, event_type, program_id, obset_id, 
                     ob_number
    END_INDEX

    INDEX  jitter_evt_map_2
        TYPE         nonclustered
        FIELDS       program_id, obset_id, ob_number
    END_INDEX

END_RELATION