07/03/03 48821 CTB Converted to XML format 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. C17 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. C3 (SMS or GSA) SMS start or GS acquisition start. C3 BASE_36 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 or pmdb -load 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. C2 BASE_36 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. C2 BASE_36 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. C1 (Y or N) Y indicates this is a internal observation. JITTER_EVT_MAP_TYPE FGS-jitter-dataset to MSC-event Mapping Relation OPUS unique clustered nonclustered