This relation documents STIS Guest Observer WAVECAL exposures that were originally unassociated in TRANS, but that were later deemed capable of being parts of associations by the STIS team. To determine which associations a wavecal is part of these fields can be joined with similar fields in the asn_members table. The work is fully described in OPUS OPR 55219. C3 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. This program identifier is tagged as 'program_id' in most PMDB relations. 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. C2 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. An observation set is identified by a 2 character base 36 string. This field, typically called 'obset_id', will often contribute to the index on relation together with a proposal_id, version_num, and possibly other fields. OBSET is an abbreviation for observation set. C3 BASE_36 For exposures, observations are numbered sequentially throughout an observation set and are assigned by SMS/Gen. For exposures the name is two characters and it is the same as the observation ob_number. For products it is the association number (two characters) plus the product_id. STIS_GO_WAVE_TYPE STIS Guest Observer WAVECAL Relation OPUS unique clustered ignore_dup_key