!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! SDDL Name:	OBSET_EVENTS_TABLE.SDDL
!
! Purpose:      This SDDL file defines the OBSET_EVENTS_TABLE relation.
!
! Modification History:
!
!   Date       OPR      Who                       Reason
! --------   -------    ---   -------------------------------------------------
! 08/31/99    38202     KEN S.Original implementation
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
LANGUAGE        SQL

RECORD  OBSEVT_TYPE
 
!------------------------------------------------------------------------------
!
!   RECORD INFORMATION
!
!------------------------------------------------------------------------------
 
 
    DESCRIPTION       "This relation is used to provide OPUS with event
                       information found in the mission schedule for
		       particular obsets.  For all obsets found within 
		       a mission schedule it contains BOSLEW, BOACQ, 
		       and FHST times by obsets."

!------------------------------------------------------------------------------
!
!   FIELD INFORMATION
!
!------------------------------------------------------------------------------
 
    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.
                    Is 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 slew_start_time
        TYPE        C17
        DESCRIPTION "This time contains the event time of the first type 2 
		    slew + duration that pertains to the obset. "
    END_FIELD

    FIELD slew_next_time
        TYPE        C17
        DESCRIPTION "This time contains the event time of the next type 2 
		    slew that pertains to the obset. "
    END_FIELD


    FIELD boacq_start_time
        TYPE        C17
        DESCRIPTION "This time contains the event time of the first boacq
		     that pertains to the obset."
    END_FIELD

    FIELD reacq_start_time
        TYPE        C17
        DESCRIPTION "This time contains the event time of the first boacq or
		     the last reacq of one or/more reacq's that pertains to 
		     the obset."
    END_FIELD

    FIELD fhst_start_time
        TYPE        C17
        DESCRIPTION "This time contains the event time of the first FHST-3 AXIS
		     fixed head star-tracker update that pertains to the obset."
    END_FIELD


RELATION  obset_events_table
 
    TYPE             OBSEVT_TYPE
 
    DESCRIPTION      "Link obset events to RTI Relation"
 
    SUBSYSTEM_USING  "OPUS"
 
    INDEX  obset_events_1
        TYPE         unique, clustered
        FIELDS       program_id,obset_id
    END_INDEX

END_RELATION
END_RECORD