Go to the bottom.

!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! SDDL Name:    WGBO_WAIVER.SDDL
!
! Purpose:      This SDDL file defines the wgbo_waiver relation.
!
! Modification History:
!
!   Date       OPR      Who                       Reason
! --------   -------    ---   -------------------------------------------------
! 03/29/96   31192      BAO   Original implementation
! 04/19/99   35645      MMD   Added C and Fortran languages
! 05/25/99   35645.2    MMD   Changed date_rcvd to INT_TIME_STAMP_TYPE from I*4
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
!
 
LANGUAGE    C, FORTRAN, SQL

INCLUDE     ZSPSS_USER_TYPES.SDDL 
 
RECORD  WGBOWVR_TYPE
 
!------------------------------------------------------------------------------
!
!   RECORD INFORMATION
!
!------------------------------------------------------------------------------

    DESCRIPTION    "The wgbo_waiver relation is used by Operations to determine  
                    if Bright Object alerts have been waived for a particular 
                    observation set. 

                    The Bright Object alerts come from NGSS and the Contact
                    Scientist and are stored in the wgbrit_obj relation.  The 
                    Contact Scientist supplies the alerts for Moving Target
                    SUs that use a detector which is more sensitive than the
                    Guide Star Catalog.  These Contact Scientist supplied
                    alerts will always have corresponding wgbo_waiver records
                    in which the waiver_from field is set to REJECTED as they
                    have been determined to be unwaiverable.

                    For the NGSS supplied alerts, an operations member 
                    investigates Bright Object alerts received for an 
                    observation set during long range planning. If there are 
                    no health and safety issues for the Bright Object/macro 
                    aperture combinations, a Bright Object waiver file is 
                    generated.  Data from this file is loaded into the 
                    wgbo_waiver relation.
            
                    During calendar building, this relation is checked by the
                    bo_check tool to determine if a waiver has been received for 
                    each Bright Object alert whose time and angle ranges 
                    overlap those of a scheduled obset and which uses the same 
                    macro aperture as the scheduled obset.  The concern is that 
                    a Bright Object impacts a macro aperture being used at the 
                    scheduled V3 position angle for 
                    the obset. If a waiver is not found for a Bright Object/
                    macro aperture combination, an inquiry is made as to 
                    whether the alert can be ignored. In addition, a record is 
                    inserted into this relation in which the fields waiver_from 
                    is set to 'REQUESTED' and date_rcvd is set to the date of 
                    the inquiry. If the alert is found to be of no consequence, 
                    a waiver is sent, and the waiver_from and date_rcvd fields 
                    are appropriately updated with the name of the person who 
                    sent the waiver and the date when the waiver was received. 
                    If a Bright Object alert can not be waived, the waiver_from 
                    field is set to 'REJECTED' and the obset is removed from 
                    the calendar."
            
!------------------------------------------------------------------------------
!
!   FIELD INFORMATION
!
!------------------------------------------------------------------------------
 

    FIELD  proposal_id
        TYPE PROPOSAL_ID_TYPE   
    END_FIELD


    FIELD  obset_id    
        TYPE OBSET_ID_TYPE
    END_FIELD
 

    FIELD  version_num
        TYPE VERSION_NUM_TYPE
    END_FIELD
 

    FIELD  alert_obj_id
        TYPE TARGET_ID_TYPE 
        DESCRIPTION    "This field contains the unique identifier of the 
                        Bright Object."
        RELATED_FIELDS  "qtargets.target_id" "wgbrit_obj.alert_obj_id"

    END_FIELD


    FIELD  aper_id
        TYPE            C*4
        DESCRIPTION     "The macro aperture that the Bright Object falls in is
                         found in this field. It includes a number of real 
                         apertures and is strictly used for defining Bright 
                         Object avoidance areas."
        RELATED_FIELDS  "qaapertures.macro_apr_id" "wgbrit_obj.macro_apr_id"

    END_FIELD


    FIELD  waiver_from
        TYPE            C*10
        DESCRIPTION     "This field contains the name of the person issuing the 
                         Bright Object waiver. It is set to 'REQUESTED', if no 
                         record is initially found by SPST for a Bright Object/
                         macro aperture/V3 position angle combination.  It is 
                         set to 'REJECTED' if the Bright Object has been 
                         determined to be unwaiverable."
    END_FIELD


    FIELD  date_rcvd
        TYPE INT_TIME_STAMP_TYPE
        DESCRIPTION     "The date on which the Bright Object waiver is received
                         or requested by SPST is included here."
    END_FIELD

END_RECORD

!------------------------------------------------------------------------------
!
!   RELATION DECLARATION
!
!------------------------------------------------------------------------------
 
RELATION  wgbo_waiver 
 
    TYPE             WGBOWVR_TYPE
 
    DESCRIPTION      "Bright Object Waiver Relation"
 
    SUBSYSTEM_USING  "SPSS"

    INDEX  wgbo_waiver_1
        TYPE         clustered
        FIELDS       proposal_id, obset_id, version_num 
    ATTRIBUTES   ignore_dup_row
    END_INDEX
 
END_RELATION
 

Go to the top.