CHAPTER 9: HST Catalog Screens In This Chapter... Pre-Obs Screens / 114 Post-Obs Screens / 130 Instruments Screens / 138 Targets Screens / 152 Engineering Screens / 158 Archive Screens / 175 This chapter comprises complete descriptions of all data screens in the HST catalog. The screens are shown in the order in which they appear in their respective menus, except that the GENERAL screen, which appears in the top-level menu appears in the POST-OBS section since it can also be accessed through the POST-OBS menu. Following each screen is a table that explains what information is found in each field. The table also lists the source DMF table, which you will need to know if you are writing readfiles to automate your catalog searches, and data types. The data types that may appear in these tables are: o A - Alphanumeric text field (corresponds to type C in ICD-19) o I - Integer o L - Boolean logical (true or false, yes or no) o R - Real Figure 9.1 shows the organization of the HST Catalog, with the screen names placed under their appropriate menus. Figure 9.1: Organization of the HST Catalog Pre-Obs Screens The PRE-OBS menu comprises the following data screens: o ABSTRACTS-SHORT (page 115) o ABSTRACTS-LONG (page 116) o EXP-CAT (page 117) o GO-GTO (page 121) o OPPARM (page 123) o PROP (page 124) o PROP-OBS (page 126) o USERS-EXP-INFO (page 128) ABSTRACTS_SHORT This screen provides a direct view on the abstract table in the DMF database. The abstract table contains the title, keywords, and abstract for each accepted HST proposal. The field proposal_id uniquely identifies each proposal. This screen provides access to information about the proposal abstracts. Figure 9.2: ABSTRACTS_SHORT Screen Field abstract keywords pi_name prop_id sci_category title Source abstract abstract prop prop prop prop Type A A A I A A Contents Abstract of proposal Proposal keywords Last name of the principal investigator Proposal identification number Type of proposal, as indicated on proposal cover page Title of the proposal Table 9.1: Fields in the ABSTRACTS_SHORT Screen ABSTRACTS_LONG The ABSTRACTS_LONG screen contains essentially the same information as the ABSTRACTS_SHORT screen, although it allows for a longer abstract description. This screen can only be viewed using a long window (see page 12). Figure 9.3: ABSTRACTS_LONG Screen Field abstract keywords pi_name prop_id sci_category title Source abstract abstract prop prop prop prop Type A A A I A A Contents Abstract of proposal Proposal keywords Last name of the principal investigator Proposal identification number Type of proposal, as indicated on proposal cover page Title of the proposal Table 9.2: Fields in the ABSTRACTS_LONG Screen EXP_CAT The EXP_CAT screen (also called the "Official GTO and GO catalog" screen) provides a view on the exposure catalog (see page 82). The EC contains all HST targets approved for observation by guest observers (GOs) or guaranteed time observers (GTOs). Figure 9.4: EXP_CAT Screen Field prop_id pi_name cycle sci_category config opmode aperture spect_elem centwave spec_req exptime num_exp targname ra dec Type I A I A A A A A I A D I A D D Contents Proposal identification number Name of principal investigator Cycle in which proposal was considered Can be CAL, OV, SV, GTO, or GO Requested instrument configuration Requested operating mode Requested instrument aperture Spectral element (filter name) Central wavelength (angstroms) Special requirements Proposed exposure time in hh mm ss Requested number of exposures for current observation Target name as entered by observer Planned right ascension (equinox 2000) Planned declination (equinox 2000) Table 9.3: Fields in the EXP_CAT Screen OBS The OBS screen provides a direct view on the the OBS table in the DMF database (see Chapter 11). The OBS screen displays the planned observational parameters for each exposure. Example 9.5: OBS Screen Field aper_1 aper_2 aper_3 aper_4 config linenum_id maxwave minwave num_exposures opmode pep_expo prop_exptime proposid seqline seqname sp_el_1 sp_el_2 sp_el_3 sp_el_4 targ_descr target_category targname Contents Aperture 1 Aperture 2 Aperture 3 Aperture 4 Requested instrument (e.g., WFC or PC) Number of lines per scan Maximum wavelength Minimum wavelength Number of exposures Requested operating mode PEPSI exposure number (Format is NNN.NNNMMMM where NNN.NNN is line number in exposure logsheet and MMMM is expansion number if exposure is repeated) Proposed exposure time Proposal ID from PEPSI Line number in sequence Sequence name Spectral element 1 Spectral element 2 Spectral element 3 Spectral element 4 Target description Target category Name of target Table 9.4: Fields in the HST Planned Observations Screen GTO-GO The GTO-GO screen provides a view of the proposal-level information for all executed GO and GTO observations. The keyword information provided for each observation is similar to that provided by the EXP-CAT screen view of the exposure catalog (the official GO-GTO catalog), but only executed observations are shown. Figure 9.6: GO/GTO Screen Field dec exp_id mag minwave num_exp opmode pi_fname pi_lname priority prop_exptime prop_id proposal_title ra sci_category sp_el_1 tac_panel targ_categ targ_descr targname Contents Declination of target Exposure ID Magnitude/flux of target (if known) Minimum wavelength of spectral observation Number of exposures Requested instrument and operating mode First name of principal investigator Last name of principal investigator Priority; "H" for high, "S" for supplemental Proposed exposure time Proposal ID Title of proposal Right ascension of target (equinox 2000) Science category (CAL, OV, SV, GO, or GTO) Spectral element number 1 Time Allocation Committee approving proposal Target category (not guaranteed) Description of target Name of target, as entered by GO Table 9.5: Fields in the GO/GTO Screen OPPARM The OPPARM screen contains operational parameter information about a given exposure. Figure 9.7: OPPARM Screen Field exposure_id opparm proposal_id tuple_id value Source opparm opparm opparm opparm opparm Type A A I I A Contents Exposure ID Name of the operational parameter Proposal ID Tuple ID; this is a counter that is incremented for each new tuple in a relation Value of the operational parameter (character) Table 9.6: Fields in the Operational Parameter Screen PROP The PROP screen provides a direct view on the prop table of the DMF database (see Chapter 11). The PROP screen contains information about an entire proposal; all information displayed comes directly from the Proposal Entry Processing System Interface (PEPSI) database. The proposal_id field uniquely identifies each proposal. Figure 9.8: PROP Screen Field pi_address pi_country pi_fname pi_inst pi_lname pi_phone proposal_id proposal_title sci_category semester tac_panel tuple_id Source prop prop prop prop prop prop prop prop prop prop prop prop Type A A A A A A I A A A A I Contents Address of principal investigator Home country of principal investigator First name of principal investigator Institution with which PI is associated Last name of principal investigator Phone number of principal investigator PEPSI proposal identification number Proposal title Science category (CAL, OV, SV, GO, or GTO) Semester in which proposal was considered Time Allocation Committee reviewing proposal Incremental counter Table 9.7: Fields in the PROP Screen PROP-OBS The PROP-OBS screen is a view on the prop and obs tables of the HST catalog. It provides general information about planned parameters of executed HST observations. Data accessed from this screen are similar to that provided by the GO or GTO catalogs, but with more extensive information provided. Figure 9.9: PROP-OBS Screen Field config flux opmode pep_expo pi_fname pi_lname priority proposal_title proposal_id release_date sci_category tac_panel tardescr tardesc2 targcat targname Contents Requested instrument (e.g., WFC or PC) Requested operating mode PEPSI exposure number Principal investigator's first name PI's last name Priority; "H" for high, "S" for supplemental Title of proposal Proposal ID from PEPSI Date on which data becomes public Science category (CAL, OV, SV, GO, or GTO) Time allocation committee approving proposal Target description Continuation of target description Target category Name of target Table 9.8: Fields in the PROP-OBS Screen USERS-EXP-INFO The USERS-EXP-INFO screen provides a direct view on the PEPSI table in the DMF database (see Chapter 11). This screen describes exposures at the observation level. Figure 9.10: USERS-EXP-INFO Screen Field aperture_1 through aperture_4 config exposure_id linenum_id maxwave minwave num_exposures opmode proposal_id seqline seqname spec_1 through spec_4 tardescr and tardescr2 target_category targname Source pepsi pepsi pepsi pepsi pepsi pepsi pepsi pepsi pepsi pepsi pepsi pepsi pepsi pepsi pepsi Type A A A A R R I A I A A A A A A Contents Apertures 1 through 4 Instrument (configuration) PEP exposure identifier, distinct from line number. Form is NNN.NNNMMMM where NNN.NNN is the line number in the exposure logsheet and MMMM is the expansion number if the exposure is found in a repeat (do for target or user seq expansion) PEP proposal line number Maximum wavelength Minimum wavelength Number of exposures Operating mode of the instrument PEPSI proposal ID PEP line number of defined sequence PEP define/use sequence name Spectral elements 1 through 4 Target description Target category Proposer's target name Table 9.9: Fields in the USERS-EXP-INFO Screen Post-Obs Screens The POST-OBS menu provides access to the following screens: o EPHEMERIS - Ephemeris Information o EXP - The Exposures Screen (page 131) o GENERAL - General Purpose Search Screen, this is also accessible directly from the top-level menu (page 133) o PDQ - PODPS Data Quality Screen (page 135) o PLANNED_VS_DONE - Planned Versus Executed Screens (page 136) EPHEMERIS The ephemeris data file describes the spacecraft's position during its observations. This data can be critical during the analysis process, for example, in determining the Doppler effects of wavelength measurements. Figure 9.11: EPHEMERIS Screen Field archive_date creation_date dataset_name extension tuple_id Source ephemeris ephemeris ephemeris ephemeris ephemeris Type A A A A I Contents Date that file was archived Date that file was created Name of data set .ORX Tuple counter Table 9.10: Fields in the EPHEMERIS Screen EXP The EXP screen is a direct view on the EXP table of the DMF database. The EXPosure table contains keywords which describe-at the SOGS level-exposures taken by the telescope. All data are taken from the SOGS science header files. The dataset field refers to the DSNAME relation, used to find the archived files. Figure 9.12: EXP Screen Field dataset dec (N.P.) dec (obs) dec (v1) Exp len exposure linenum moon ang proposal ra (N.P.) ra (obs) ra (v1) seqline start stop sun ang surf alt surf lat surf long target tuple_id v3 angle Type A A D D I I A D I D D D A I I D D D D A I D Contents Data set name Declination of north pole of target Declination of target Declination of telescope's V1 axis Duration of exposure Exposure ID Exposure ID assigned by PEPSI within proposal Angle between the moon and the target Proposal number Right ascension of north pole of target Right ascension of target Right ascension of telescope's V1 axis Line number in DEFINE SEQUENCE line Start time of exposure Stop time of exposure Angle between the sun and the target Surface feature altitude Surface feature latitude Surface feature longitude Name of target Tuple counter Position of telescope's V3 axis Table 9.11: Fields in the EXP Screen GENERAL The GENERAL screen provides a view on several tables in the HST catalog. It provides general information about completed observations, and is typically the best screen to start with when doing archival searches. More precise information about a particular observation can be found in the INSTRUMENT screens. Note that observations taken with the FGS are not displayed by this screen. Example 9.13: The GENERAL Screen Field aper 1 through aper 4 category config dataset DEC descrpt 1 descrpt 2 expflag expstart exptime fgslock instrmnt opmode qualcom quality PI proposal_id release_date sci_cat spec 1 through spec 4 target RA target name Source obs obs obs exp exp obs obs exp exp exp exp exp obs pdq pdq prop exp dsname prop obs exp exp Type A A A A A A A I I D A A A A A A I I A A I A Contents Requested apertures Target category (not guaranteed) Requested instrument Dataset name (reference to the archive files) Declination of target (degrees) Description of target (first 68 characters) Description of target (last 68 characters) Exposure interrupt indicator Exposure start date Exposure length (minutes and seconds) FGS lock status (FINE, COARSE, GYRO, NO) Instrument in use Requested operating mode PODPS assessment comments Parameterized PODPS data quality assessment Last name of principal investigator Proposal identification Date data will become public Science category Requested spectral elements Right ascension of target (degrees) Target name (as entered by GO) Table 9.12: Fields in the GENERAL Screen PDQ The PDQ screen displays the PODPS data quality comments and parameters for each dataset. (See page 78 for a description of PDQ values.) Example 9.14: PODPS Data Quality Screen Field dataset qualcom1 and qualcom2 qualdate quality tuple_id Contents Name of dataset (reference to files in archives) PODPS data quality comments Date when quality assessment was assigned Parameterized PODPS data quality assessment Tuple counter Table 9.13: Fields in the PODPS Data Quality Screen Planned-vs-Done This screen allows you to compare the proposed observational parameters (indicated as prop) with executed observational paramers (indicated by obs). Figure 9.15: PLANNED-VS-DONE Screen Field categ config dec 2000 descr exp id exp start exp time instr mag maxwave minwave pi proposal ra 2000 sci_cat stop targ Source pepsi obs pepsi/exp obs obs exp pepsi/exp obs targflux pepsi pepsi prop prop pepsi/exp prop exp fixtarg Type A A A A R A D A R R R A I A A I A Contents Target category (not guaranteed) Requested instrument Declination; first field is proposed, second is observed Description of target Exposure ID Exposure start time Exposure length (minutes, seconds); first field is proposed, second field is observed Instrument in use Flux of object (can be magnitude) Maximum wavelength Minimum wavelength Last name of principal investigator Proposal identification number Right ascension; first field is proposed, 2nd is observed Science category (CAL, OV, SV, GTO, GO) Stop date and time of exposure Target name (from proposal) Table 9.14: Fields in the PLANNED-VS-DONE Screen Instruments Screens The screens accessible from the INSTRUMENTS menu provide instrument-specific information for completed HST observations. The following screens are available from this menu: o FGS - Fine Guidance Sensors o FOC - Faint Object Camera (page 141) o FOS - Faint Object Spectrograph (page 143) o FOS2 - Instrument Scientist Screen for FOS (page 145) o HRS - High Resolution Spectrograph (page 146) o HSP - High Speed Photometer (page 148) o WFPC - Wide Field/Planetary Camera (page 150) FGS The FGS/Astrometry screen provides instrument-specific information about completed HST observations taken with the FGS. Information is drawn from the EXPosure and calibration database (CDBS) tables. Figure 9.16: FGS Screen Field Proposal Id Dataset Release Date Target RA Target Dec fgslock V1axis RA V1axis Dec V3 Angle Target Name calibrat exptime expstart expflag targetid fgsid aastmode tgt_mag aast_flt tmfmt Source exp exp dsname exp exp exp exp exp exp c0shp exp exp exp cfmast cfmast cfmast cfmast cfmast cfmast Contents Original proposal ID number Dateset name (reference to archive files) Release date Right ascension of target (degrees) Declination of target (degrees) FGS lock status (FINE COARSE GYRO NO) Right ascension of telescope's V1 axis (degrees) Declination of telescope's V1 axis Position angle of telescope's V3 axis Target name Calibration flag (T or F) Exposure duration (seconds-calculated) Exposure start time (modified Julian date) Exposure interrupt indicator Target ID (from TARGETID keyword) Astrometry FGS ID Actual astrometry processing mode Target magnitude AST FGS filter position (actual) Telemetry format (af, an, ff, fn) Table 9.15: Fields in the FGS Screen FOC The FOC screen provides instrument specific information about completed HST observations taken with the FOC. Information is drawn from the EXPosure and calibration database (CDBS) tables. Figure 9.17: FOC Screen Field calibrat cammode Dataset expflag expstart exptime fgslock Field of View filter ledcolor ledmode lineoff mtflag optcrly optelt1 through optelt4 Proposal ID pxformt Release Date sampoff shtmode smmmode Target Dec Target Name Target RA V1axis Dec V1axis RA V3 angle Source c0shp cxmast exp exp exp exp exp cxmast focwheel1 through focwheel4 cxmast cxmast cxmast exp cxmast cxmast exp cxmast dsname cxmast cxmast cxmast exp exp exp exp exp exp Type A A A A I D A IxI A A I R A A A I A I R A A T A T T T T Contents Calibration flag (T or F) Coronographic apodizer mask (INBEAM, NOTUSED) Dataset name (reference to archive files) Exposure interrupt indicator Exposure start time (Modified Julian date) Exposure duration (seconds-calculated) FGS lock status (FINE, COARSE, GYRO, or NO) Samples per line (64, 128, 256, 512) and lines per frame (64, 128, 256, 512, or 1024) Filter LED color (a color, blank, NONE or ERROR) LED calibration status (ACTIVE or NOTUSED) Line offset (0.0 to 1023.75) Moving target flag (T or F) Optical relay (f48, f96, or f288) Optical element of each filter wheel Identification of original proposal Format of the image (NORMAL or ZOOM) Release date of dataset Sample offset (0.0 to 1023.75) Shutter mode (INBEAM or NOTUSED) Spectrographic mirror mechanism (INBEAM, NOTUSED) Declination of target (degrees) Target name Right ascension of target (degrees) Declination of telescope's V1 axis (degrees) Right ascension of telescope's V1 axis (degrees) Position of telescope's V3 axis Table 9.16: Contents of the FOC Screen FOS The FOS screen provides instrument specific information about completed HST observations taken with the FOS. Information is drawn from the EXPosure and calibration database (CDBS) tables. Figure 9.18: FOS Screen Field aper_id calibrat dataset detector expflag expstart exptime fgslock fgwa_id grndmode noiselm pa_aper polar_id porposal Id release date slices Target RA Target Dec Target Name V1axis Dec V1axis RA V3 Angle yaqmd yspace Source cymast c0shp exp cymast exp exp exp exp cymast cymast cymast cymast cymast exp dsname cymast exp exp exp exp exp exp cymast cymast Type A A A A A I D A A A I I A I I I T T A T T T I R Contents Aperture ID Calibration flag (T or F) Dataset name (reference to archive files) Detector in use (AMBER or BLUE) Exposure interrupt indicator Exposure start time (Modified Julian date) Exposure duration (seconds-calculated) FGS lock status (FINE, COARSE, GYRO, NO) FGWA ID Ground software mode Burst noise rejection limit Position angle of aperture used with target Polarizer ID (A, B, or C (clear)) Identification of the original proposal Release date Number of time slices Right ascension of observed target Declination of target (degrees) Target name Declination of telescope's V1 axis Right ascension of telescope's V1 axis (degrees) Position of telescope's V3 axis Acquisition mode yspace = yrange * 32 / ysteps Table 9.17: Contents of FOS Screen Fields FOS2 The FOS2 screen provides more detailed instrument parameters of the HST observations taken with the FOS. Figure 9.19: FOS2 Screen GHRS The GHRS screen provides instrument specific information about completed HST observations taken with the High Resolution Spectrograph (HRS). Information is drawn from the EXPosure and calibration database (CDBS) tables. Figure 9.20: The GHRS Screen Field aperobj calibrat Dataset detector expflag expstart exptime fgslock grating nbins obsmode Proposal Id Release Date Target Dec Target Name Target RA V1axis RA V1axis Dec V3 Angle Source czmast c0shp exp czmast exp exp exp exp czmast czmast czmast exp dsname exp exp exp exp exp exp Type A A A I A I D A A I A I I T A T T T T Contents Science instrument object aperture ID Calibration flag (T or F) Dataset name (reference to archive files) Detector in use (1 or 2) Exposure interrupt indicator Exposure start time (Modified Julian date) Exposure duration (seconds-calculated) FGS lock status (FINE, COARSE, GYRO, NO) Grating name Number of substep bins in this pattern (1 to 16) Observation mode Proposal ID Release date Declination of target (degrees) Target name Target right ascension (degrees) Right ascension of telescope's V1 axis (degrees) Declination of telescope's V1 axis (degrees) Position angle of telescope's V3 axis Table 9.18: Fields in the GHRS Screen HSP The HSP screen provides instrument specific information about completed HST observations taken with the HSP. Information is drawn from the EXPosure and calibration database (CDBS) tables. Figure 9.21: HSP Screen Field aperoffx aperoffy apertobj calibrat data_fmt data_src data_type Dataset detectob eplongpm expflag expstart exptime fgslock longpmer mode mtflag Proposal ID Release Date samptime Target Dec Target Name Target RA V1axis Dec V1axis RA V3 Angle Source cvmast cvmast cvmast c0shp cvmast cvmast cvmast exp cvmast cvmast exp exp exp exp cvmast cvmast exp exp dsname cvmast exp exp exp exp exp exp Type R R A A A A A A I R A I D A R A A I I R T A T T T T Contents X component of offset of object in aperture Y component of offset of object in aperture Aperture in use-object date Calibration flag (T or F) Data format (BYTE, WORD, LWRD, ALOG, ALL) Data source (star, sky, area scan) Data type (digital or analog) Dataset name (reference to archive files) Detector in use (0-5); object data Epoch of longitude of prime meridian Exposure interrupt indicator Exposure start time (Modified Julian date) Exposure duration (seconds-calculated) FGS lock status (FINE, COARSE, GYRO, NO) Longitude of prime meridian Instrument mode (SCP, SSP, or ARS) Moving target flag (T or F) Identification of original proposal Release date Integration time (in seconds) Declination of target (degrees) Name of target Right ascension of target (degrees) Declination of telescope's V1 axis (degrees) Right ascension of telescope's V1 axis (degrees) Position angle of telescope's V3 axis Table 9.19: Fields in the HSP Screen WFPC The WFPC screen provides instrument specific information about completed HST observations taken with the WF/PC. Data are extracted from the EXPosure, OBServation, and WF/PC calibration-related master tables. Figure 9.22: WFPC Screen Field Bay 3A1 T CDBSfile calibrat Camera Dataset expflag expstart exptime fgslock filt. 1 filt. 2 im. type mode preflash Proposal ID Release Date Targ aq mode Target Dec Target Name Target RA V1axis Dec V1axis RA V3 Angle Source cwmast cwmast c0shp cwmast exp exp exp exp exp cwmast cwmast cwmast cwmast cwmast exp dsname c0shp exp exp exp exp exp expp Type R A A A A A I D A A A A A T I I A T A T T T T Contents Bay 3 A1 temperature CDBS file (GENERIC, BIAS, DARK, PREF, FLAT, MASK, AT) Calibration flag (T or F) Camera in use (WF or PC) Dataset name (reference to the archive files) Exposure interrupt indicator Exposure start time (Modified Julian date) Exposure duration (seconds-calculated) FGS lock status (FINE, COARSE, GYRO, NO) First filter name Second filter name Image type (SCIENCE, BIAS, DARK, PREF, FLAT, SPECIAL) Instrument mode (FULL or AREA) FULL is full resolution, AREA is area integration Preflash time (seconds) Identification of original proposal Release date Target acquision mode used for the observation (00-03) Declination of target (degrees) Target name Right ascension of target (degrees) Declination of telescope's V1 axis (degrees) Right ascension of telescope's V1 axis (degrees) Position angle of telescope's V3 axis Table 9.20: Fields in the WFPC Screen Targets Screens There are four screens under the TARGETS menu: o FIXTARG - Fixed Target Screen o SS_TARG - Solar System Target Screen (page 154) o TARGSEARCH - Target Description and Alias Screen (page 156) o TARGFLUX - Target Flux Screen (page 155) FIXTARG The FIXTARG screen describes fixed target information and is only populated for fixed targets. Figure 9.23: Fixed Target Screen Field dec_proposed plate_id proposal_id ra_proposed redshift _rv targname tuple_id Type D A I D D D A I Contents Declination of proposed target (arc degrees) Plate ID Proposal ID Right ascension of proposed target (degrees) Value of the redshift Value of radial velocity (computed) Target name Tuple counter; incremented for each tuple in a relation Table 9.21: Fields in the Fixed Target Screen SS_TARG The SS_TARG screen describes information for observations of solar system targets. This screen can be viewed using a long window (see page 12). Figure 9.24: Solar System Target Screen Field comments position_1 position_2 position_3 proposal_ targname tid windows Type I A I Contents Comments Radius, latitude, observation type, etc. Radius, latitude, observation type, etc. Radius, latitude, observation type, etc. Proposal ID Target name Tuple counter Observation window Table 9.22: Fields in the SS_TARG Screen TARGFLUX This screen displayes the observer-entered information about the flux (magnitude) of the target. Figure 9.25: Target Data Screen Field band1 band2 character_value flux flux_type flux_uncertainty proposal_id targname tuple_id wavelength Type A A A A F I A I F Contents First band (V or B) Second band (V or B) For flux_type of value "TYP" Value of the flux (can be the magnitude) Type of flux (e.g., BB "blackbody", CEX "color", FLX "flux") Flux uncertainty of the target Proposal ID Target name Tuple counter Wavelength of FLX-type flux (angstroms) Table 9.23: Fields in the TARGFLUX Screen TARGSEARCH TARGSEARCH is useful for searching for HST observations of specific targets based on target name, alias, or target RA and Dec, and is also useful for finding observations of sources in a given astronomical class (based on target categories, descriptions, and the proposal title). Figure 9.26: Target Description and Alias Search Screen Field dataset descrpt 1 descrpt 2 instrmnt prop id prop title target alias target category target DEC target RA target name Type A A A A I A A A I I A Source exp obs obs exp exp prop obs obs exp exp obs Contents Dataset name First 68 characters of target description Last 68 characters of target description Instrument Proposal identifier (PEP) Proposal title Target alias 1 and 2 Target category 1 and 2 Declination of target (degrees) Right ascension of target (degrees) Target name, as entered by observer Table 9.24: Fields in the Target Alias Screen Engineering Screens The ENGINEERING menu provides access to the following data screens: o RTA - Real-Time Acquisition o REC_ENG - Rec Engineering o ENG_SUB - Engineering Subsystem o OPPARM - Operational Parameters o SMS - Science Mission Schedule o MS - Mission Schedule and Timelines o MAN_VER_DATA - Maneuver Verification Data o GS_DATA - Guide Star Data o OBC_DUMP - On-Board Computer Dumps o DUMP_EXT - Dumps Extension Codes RTA The RTA screen accesses the real-time activity log, described in ICD-19 and ICD-46. These files have a file name of the form Zymdhhmmn.POD, where: o Z - Identifies the file as a real-time activity log file o y - Year (1-Z), where 1981 is 1 o m - Month (1-C), where January is 1 o d - Day (1-V) o hh - Hour (00-23) o mm - Minute (00-59) o n - Site, 1 is scif, 2 is ssc o POD - All RTA files end in the extension .POD Figure 9.27: RTA Screen Field dataset_name date extension tuple_id Contents Name of the data set Date, taken from the file name .POD Tuple counter Table 9.25: Fields in the RTA Screen REC_ENG REC_ENG files all have an extension of .DAT. Indexes are available for the fields stop_time and start_time. File names have the format EymdhhmmM.DAT, where: o E - The letter E identifies the file as an engineering file o y - Year (1-Z), 1 is 1981 o m - Month (1-C), 1 is January o d - Day of month (1-V) o hh - Hour (00-23) o mm - Minute (00-59) Figure 9.28: REC_ENG Screen Field data_size dateaset_name extension format start_time stop_time tuple_id Type I A A A Contents Size of the data file Name of the data set .DAT Data format Starting time, format is dd Mmm yyyy hh:mm:ss, e.g., 12 Nov 1991 07:56:51) Stop time, format is dd Mmm yyyy hh:mm:ss Tuple counter Table 9.26: Fields in the REC_ENG Screen ENG_SUB REC_ENG data files all have an extension of .DAT. Indexes are available on the fields stop_time and start_time. The file name format is EymdhhmmM.DAT, where: o E - Identifies the file as an engineering file o y - Year (1-Z), 1 is 1981 o m - Month (1-C), 1 is January o d - Day of month (1-31) o hh - Hour (00-23) o mm - Minute (00-59) Figure 9.29: ENG_SUB Screen Field compress data_size dataset_name def_name def_orig extension format generated raw_convert start_time stop_time tuple_id Type A I A A A A A A A Contents Flag indicating compressed data Size of the data file Data set name (Xymdhhpxx, described above) Subset definition name Subset definition origin .abc Data format Time generated, format is yyyy-mm-dd hh:mm:ss Flag identifying raw or converted data Starting time, format is yyyy-mm-dd hh:mm:ss Stop time, format is yyyy-mm-dd hh:mm:ss Tuple counter Table 9.27: Fields in the ENG_SUB Data Screen OPPARM The OPPARM screen contains operational parameter information about a given exposure. Figure 9.30: OPPARM Screen Field exposure_id opparm proposal_id tuple_id value Source opparm opparm opparm opparm opparm Type A A I I A Contents Exposure ID Name of the operational parameter Proposal ID Tuple ID; this is a counter that is incremented for each new tuple in a relation Value of the operational parameter (character) Table 9.28: Fields in the Operational Parameter Screen SMS The SMS screen is the science mission schedule produced by SPSS. It includes all mission parameters. SMS is passed to PASS where spacecraft parameters are added, producing mission schedules (final and re-plans) and mission timelines (final and re-plans). File names have the form Sadddnpr.ext. The extension can be either .SMS for science mission schedules, .MS for mission schedules, or .MTL for mission time lines. The root name consists of: o S - Identifies the files as an SMS file o a - Identifier o ddd - Day of year (1-366) o n - Times covering exact period that day o p - Patch revision o r - Version Example 9.31: SMS Screen Field calendar_name cc_list dataset_name date extension Type A A A A A Contents SPSS name File name (without extension) Date of the science mission schedule file File name extension Table 9.29: Fields in the Science Mission Schedule Screen MS This screen provides information from the Mission Schedule. File names take the form Sadddnpr.ext, where: S - Identifies the file as a MS file a - Identifier ddd - Day of year (1-366) n - Times covering exact period that day p - Patch revision r - Version ext - Extension Figure 9.32: MS Screen Field date filename extension tuple_id Type A A A Description Date of the science mission schedule file File name without the extension File extension Tuple counter Figure 9.33: Fields in the MS Screen MAN_VER_DATA The MAN_VER_DATA screen displays information from the maneuver verification files, which have names of the form Tymdhmmss where: o T - Identifies the file as a maneuver verification file o y - Year (1-Z, 1981 is 1) o m - Month (1-C, 1 is January) o d - Day (1-V) o h - Hour (0-N) o mm - Minute (00-59) o ss - Second (00-59) Figure 9.34: MAN_VER_DATA Screen Field dataset_name filesize generated num_records start_time stop_time tuple_id A I A I A A Contents Name of the data set Size of the file Time generated, format is dd Mmm yyyy hh:mm:ss Number of records Starting time, format is dd Mmm yyyy hh:mm:ss, e.g., 01 Nov 1990 04:40:47 Stop time, format is dd Mmm yyyy hh:mm:ss Tuple counter Table 9.30: Fields in the Maneuver Verification Data Screen GS_DATA The GS_DATA screen is made up of guide star data file names. File names have the form Tymdhmmss.GSD, where: o T - All guide star files begin with the letter T o y - Year (1-Z), 1981 is 1 o m - Month (1-C), January is 1 o d - Day (1-V) o h - Hour (0-N) o mm - Minute (00-59) o ss - Second (00-59) All file names end with the .GSD extension. Figure 9.35: GS_DATA Screen Field dataset_name extension filesize generated num_records start_time stop_time tuple_id Type A A I A I A A Contents Name of the data set File name extension, .GSD File size Time generated, format is dd Mmm yyyy hh:mm:ss Number of records Start time, format is dd Mmm yyyy hh:mm:ss Stop time, format is dd Mmm yyyy hh:mm:ss Tuple counter Table 9.31: Fields in the Guide Star Data Screen OBC_DUMP The OBC_DUMP screen describes the archived NNC-I computer dumps. There are six types of dumps: executive status buffer dumps, NSSC-I memory dumps, HSP microprocessor memory dumps, FOC microprocessor dumps, FOS microprocessor dumps, and unknown dumps. File names have the format Gqymdhhzz.DMP, where: o G - Identifies the file as a dump file o q - Dump type; T is executive status dump, U is NNSC-I memory dump, V is HSP dump, X is FOC dump, Y is FOS dump, and A is unkown dump o y - Year of first minor frame (1-Z), 1981 is 1 o m - Month of first minor frame (1-C) o d - Day of first minor frame (1-V) o hh - Hour of first minor frame (00-23) o zz - Minute (00-59) Figure 9.36: OBC_DUMP Screen Field dataset_name date extension tuple_id type Type A A A A Contents Name of the data set Date of the first minor frame Extension (ATX, BDX, E1X, etc.) Tuple counter Type of dump file; determined from dump type character in the file name, using the table DUMP_EXT Table 9.32: Fields in the Onboard Computer Dump Screen DUMP_EXT The DUMP_EXT screen describes the computer dump extensions. Tye types used are: T for executive status buffer, U for NSSC-I memory, V for HSP, X for FOC, Y for FOS, and A for unknown dump. Figure 9.37: DUMP_EXT Screen Field dump_char type Contents Character value in the file name representing the dump type (see description above) Six character value of the type Table 9.33: Fields in the Dump Extension Screen Archive Screens These screens provide direct views of the DSNAME and FILES tables in the DMF catalog. The tables provide indexes to the files and datasets on the optical disks that constitute the HST archive. (See also Chapter 11). DSNAME Figure 9.38: DSNAME Screen Field archive_class archive_date archive_dist creation_date dataset_name propr_exception release_date tuple_id version Contents Archive class of the data set. This describes the general character of the dataset. Several classes are defined by SOGS and more classes are defined for data from other sources-such as SMS, ephemeris data, etc. Date the dataset was archived (see Chapter 11) Bit indicating that data center that received the archive data set Date the data set was created Name of the data set in the archive Proprietary exception flag; a value of 1 indicates a pro- proprietary release period other than 1 year Date that data will become public (non-proprietary) Tuple counter Version of the dataset and archive class; when data are rearchived, the version number is incremented Table 9.34: Fields in the DSNAME Screen FILES Figure 9.39: FILES Screen Field archive_class dataset_name dir_sec diskname extension size tuple_id Contents Archive class of data set Name of the data set in the archive Optical disk directory sector offset Name of optical disk containing file File extension Maximum size, in bytes, of data set Tuple counter Table 9.35: Fields in the FILES Screen 113