!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! ! SDDL Name: QOLINK_SMS.SDDL ! ! Purpose: This SDDL file defines the qolink_sms relation. ! ! Modification History: ! ! Date OPR Who Reason ! -------- ------- --- ------------------------------------------------- ! 05/09/96 31365 JJB Original implementation ! 03/10/97 33526 JJB Extend table to include products and add status ! 07/28/97 34813 JJB Extend table to add OPUS tracking fields ! 07/06/99 38210 KEN Extend table to add start/stop time fields ! 03/30/00 40279 JJB Add index for start time used by insert_ss_records ! 05/09/01 44524 JJB Add time_type field for FGS project ! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! LANGUAGE SQL RECORD QOLSMS_TYPE !------------------------------------------------------------------------------ ! ! RECORD INFORMATION ! !------------------------------------------------------------------------------ DESCRIPTION "This relation is used to provide DADS and OPUS with the SMS_ID for any observation in the support schedule. It can be used to list all observations and association products for a particular SMS_ID. It contains a status field to identify observation or product archive success or unavailability. It contains eight OPUS tracking fields not used by DADS." !------------------------------------------------------------------------------ ! ! 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 ob_number TYPE C3 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. The third character is only used for association products." END_FIELD FIELD sms_id TYPE C9 DESCRIPTION "The C&C list is a major data structure within SPSS that contains information on 'candidates' and the 'calendar'. The candidate data, often referred to as the candidate pool, are scheduling units and their associated observation set, alignment, and target data. The calendar is a timeline of activities that are laid down by the SPSS scheduling utilities. When a C&C List is saved in SPSS (via the CCLIST/SAVE comand) it receives an identifier. The identifier can be up to 9 characters long. Within operations, the C&C list naming convention is: yydddnxx where yy = last two digits of the year ddd = day of year of start of calendar n = length of calendar in days (usually 7) xx = unique identifier within above info. " END_FIELD FIELD status TYPE C1 DESCRIPTION "The condition or availability for archiving is indicated by a status code with the following definition: U - Unexecuted - the initial condition for exposures or products that will be archived independently of associations. M - Member - the initial condition for exposures that are only archived within an association product. N - Not available - set by operations to indicate exposures or products that cannot be generated. E - Executed and archived successfully." END_FIELD FIELD inst TYPE C1 DESCRIPTION "One character identifier for the instrument used for the science observation. The relation between this value and the names in qobservation.si_id are: 1 = 1 2 = 2 3 = 3 J = ACS N = NIC O = STIS U = WFII V = HSP W = WFPC X = FOC Y = FOS Z = HRS " END_FIELD FIELD taq TYPE C1 DESCRIPTION "Flags observation as a target acquisition. Y - The qobservation.target_acqmode field is 01 or 02. This observation is a target acquisition." END_FIELD FIELD ocx_expected TYPE C1 DESCRIPTION "Flags this observation as real time (mode 1) target acq. Y - The qobservation.target_acqmode field is 01. This observation is a mode 1 (real time) target acquisition image." END_FIELD FIELD pdq_created TYPE C1 DESCRIPTION "OPUS pipeline has created a PDQ file for this observation. The value of this column is an alphanumeric code that indicates the status, real or inferred, of the PDQ file for the observation." END_FIELD FIELD oms_archived TYPE C1 DESCRIPTION "OMS pipeline has successfully achived an observation log for this observation. X - The data assessment software has validated existence of the OMS observation log for this observation in DADS." END_FIELD FIELD rti_checked TYPE C1 DESCRIPTION "OPUS staff has checked for existence of real time information for this observation. X - The OPUS staff has run RTI_CHECK software for this observation." END_FIELD FIELD ocx_appended TYPE C1 DESCRIPTION "An OCX file has been appended to the PDQ file. The value of this column is an alphanumeric code that indicates that the data assessment software has located an OCX file (and the type of file) for this observation and has appended it to the PDQ file." END_FIELD FIELD assessed TYPE C1 DESCRIPTION "This observation has been assessed for procedural quality. The value of this column is an alphanumeric code that summarizes the essentials of the assessment process." END_FIELD FIELD dq_archived TYPE C1 DESCRIPTION "Archive status of the procedureal data quality file(s). The value of this column is an alphanumeric code that indicates the archive status of the PDQ (and optionally the OCX) file of this observation." END_FIELD FIELD start_time TYPE C17 DESCRIPTION "This field (format: yyyy.ddd:hh:mm:ss) contains either the planned or actual start time of the observation. The time_type field indicates the source of the time. " END_FIELD FIELD end_time TYPE C17 DESCRIPTION "This field (format: yyyy.ddd:hh:mm:ss) contains either the planned or actual end time of the observation. The time_type field indicates the source of the time. " END_FIELD FIELD time_type TYPE C1 DESCRIPTION "(P/A) When this field is P for planned, start_time and end_time are generated from SPSS planning data and the accuracy is questionable. When this field is A for actual, start_time and end_time have been updated by the OPUS pipeline using science data. " END_FIELD RELATION qolink_sms TYPE QOLSMS_TYPE DESCRIPTION "Link observations to CCL Relation" SUBSYSTEM_USING "OPUS" INDEX qolink_sms_1 TYPE unique, clustered FIELDS program_id,obset_id,ob_number END_INDEX INDEX qolink_sms_2 TYPE nonclustered FIELDS sms_id END_INDEX INDEX qolink_sms_3 TYPE nonclustered FIELDS start_time END_INDEX END_RELATION END_RECORD