Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.stsci.edu/ftp/documents/archive-manual/11_dmfstructure.txt Дата изменения: Wed Mar 24 18:10:01 1993 Дата индексирования: Sat Dec 22 19:32:30 2007 Кодировка: Поисковые слова: star trail

CHAPTER 11:
DMF
Database Structure


This chapter describes the contents of some of the tables in the Data
Management Facility (DMF). The screens presented in the STARCAT
system are views on these various database tables. This chapter includes
descriptions of the contents and population source of the exp, obs, prop,
and pepsi science tables and the dsname and files archive accounting
tables..

EXP

The EXP table is filled by ingesting keywords from the science data file
headers. There is one record per exposure. The table contains both proposal
level (planned) and exposure level (executed) information about
observational parameters of exposures.

Field

dataset_name

date_obs

dec_targ

dec_v1

equinox

expend

expflag

expstart

exptime

fgslock

instrume

linenum

monangl

mtflag

npdectrg

npratrg

observtn

obset_id

pa_v3

pep_expo

pequinox

progrmid

proposid

ra_targ

ra_v1

seqline

seqname

short_pep_expo

sun_alt

sunangle

surfaltd

surflatd

surflong

targname

time_obs

tuple_id

Contents

Name of the dataset

UT date of the start of the observation (dd/mm/yy)

Declination of target (degrees)

Declination of telescope's V1 axis (degrees)

Equinox of the celestial coordinate system

Exposure end time (Modified Julian date)

Exposure interruption indicator

Exposure start time (Modified Julian date)

Exposure duration (seconds-calculated)

Commanded FGS lock (FINE, COARSE, GYROS,
UNDEFINED)

Instrument

PEP proposal line number

Angle between the moon and the V1 axis (degrees)

Moving target flag; T if target is moving

North pole declination of target (degrees)

North pole right ascension of target (degrees)

Observation number

Observation set identifier

Position angle of telescope's V3 axis (degrees)

PEP exposure identifier, including sequence

Proposed equinox of the celestial coordinates

Program identifier

PEP proposal identifier

Right ascension of the target (degrees)

Right ascension of telescope's V1 axis (degrees)

PEP line number of defined sequence

PEP define/use sequence name

PEP exposure identifier without sequence

Altitude of the sun above Earth's limb

Angle between the sun and the V1 axis (degrees)

Surface feature altitude (kilometers)

Surface feature latitude (degrees)

Surface feature longitude (degrees)

Proposer's target name

UT time of start of observation (hh:mm:ss)

Tuple ID

Table 11.1: Contents of the EXP Table

OBS

The OBS table is filled by ingesting the science data file headers. There
is one record per exposure. The table contains predominantly proposal
level (planned) information about observational parameters of exposures.


Field

alias1

alias2

ang_side

aper_1

aper_2

aper_3

aper_4

cmd_exp

col_b_v

col_u_b

col_v_r

config

dwell_ln

dwell_tm

e_b_v

extnct_v

mag_b

mag_r

mag_u

mag_v

mt_lv1_1, mt_lv1_2,
mt_lv1_3, mt_lv1_4,
mt_lv2_1, mt_lv2_2,
mt_lv2_3, mt_lv2_4,
mt_lv2_5, mt_lv3_1,
mt_lv3_2, mt_lv3_3,
mt_lv3_4, mt_lv3_5

mu_dec

mu_epoch

mu_ra

no_lines

observtn

obset_id

opmode

parallax

pep_expo

proc_typ

progrmid

proposid

rad_vel

redshift

rootname

scan_ang

scan_cor

scan_len

scan_rat

scan_typ

scan_wid

short_pep_expo

sp_type

spec_1

spec_2

spec_3

spec_4

surf_b

surf_r

surf_u

surf_v

tar_type

tardescr

tardesc2

targcat

targcat2

tarkey1, tarkey2,
tarkey3, tarkey4,
tarkey5, tarkey6,
tarkey7, tarkey8,
tarkey9, tarkey10

tuple_id

Contents

First target name alias

Second target name alias

Angle between sides of parallelogram (degrees)

First aperture value

Second aperture value

Third aperture value

Fourth aperture value

Commanded time per exposure

Expected B-V color

Expected U-B color

Expected V-R color

Proposed instrument configuration

Dwell points per line for scan pointing

Wait time (duration) at each dwell point

E(B-V)

Extinction in V

Expected B magnitude

Expected R magnitude

Expected U magnitude

Expected V magnitude

Moving target information

Expected DEC proper motion

Epoch of the proper motion

Expected RA of proper motion

Number of lines per scan (1-99)

Observation number

Observation set identifier

Proposed operation mode

Expected parallax of target

PEP exposure identifier including sequence

Reprocessing flag:
normal - has not been reprocessed
minor - reprocessed & original release data retained
major - major reprocessing; release date reset to 1
year from reprocessing date

Program identifier

PEP proposal identifier

Radial velocity (kilometers/second)

Expected redshift of target

Rootname of the observation set

Position angle of scan line (degrees)

Scan coordinate frame of reference (celestial, )

Scan length (arcseconds)

Commanded rate of the line scan

"C" for bostrophidon, "D" for C with dwell, "N" for
unknown

Scan width (arcseconds)

PEP exposure identifier without sequence

First spectral element

Second spectral element

Third spectral element

Fourth spectral element

Expected B surface brightness

Expected R surface brightness

Expected U surface brightness

Expected V surface brightness

Target type

Target description

Target description (continued)

Target category

Target category 2

Target key description

Tuple ID from the OBS table

Table 11.2: Contents of the OBS Table

PROP

The PROP table is filled directly from the PEPSI database. PROP
contains information about entire proposals (not about individual
exposures.) The PEPSI database is maintained by the User Support Branch
at STScI.

Field

Make_spike_prop

RPSS_cur_dsn

RPPS_org_dsn

pi_address

pi_country

pi_fname

pi_inst

pi_lname

pi_mi

pi_phone

pi_title

priority

proposal_id

proposal_title

sci_category

semester

tac_panel

tuple_id

Contents

Spike file name of the current version

RPSS file name of the current version

RPSS file name of the original version

Address of the principle investigator

Country of the principle investigator

First name of the principle investigator

Principle investigator's home institution

Last name of the principal investigator

Middle initial of principle investigator

Principle investigator's phone number

Principle investigator's title, e.g., Dr. or Prof.

Priority of proposal as set by TAC

Proposal ID from PEPSI database

Title of the proposal

Scientific category for the proposal

Semester in which proposal was considered

Time Allocation Committee panel that reviewed proposal

Tuple ID from PROP

Table 11.3: Contents of the PROP Table

PEPSI

The PEPSI table contains one entry per planned exposure; it describes
the planned observational parameters for that exposure. Note that one
planned exposure can result in several executed exposures.

Field

alias_1

alias_2

aperture_1

aperture_2

aperture_3

aperture_4

config

exptime_not_spe

exposure_id

maxwave

minwave

num_exposures

opmode

proposal_id

proposed_exptime

seqline

seqname

spectral_elemen

tardescr

tardescr2

targcategory

targname

tuple_id

Descriptor

First taget name alias

Second target name alias

First aperture value

Second aperture value

Third aperture value

Fourth aperture value

Proposed instrument configuration

Flag indicating that exposure time was not specified

Exposure identifier

Maximum wavelength

Minimum wavelength

Number of exposures

Proposed operation mode

Proposal identifier (from PEPSI)

Proposed exposure time

PEP line number of define sequence

PEP define/use sequence name

First through fourth spectral elements (four fields)

Target description

Continuation of target description

Target category

Proposer's target name

Tuple counter

Table 11.4: Contents of the PEPSI Database Relation

DSNAME

The DSNAME table is populated as the data is written to the archive's
optical disk. It contains a record, by archive class (see Chapter 10), of each
complete archived dataset. The release_date is maintained as a field
in the DSNAME table.

Field

archive_class

archive_date

archive_dist

creation_date

propr_exception

release_date

reproc_count

tuple_id

version

Description

Dataset archive class

DMF archive date for the dataset

Archive distribution value

SOGS creation date for dataset

Proprietary exception flag (0 - not set)

Proprietary release date

Reprocessing count

Tuple ID

Dataset version number

Table 11.5: Contents of the DSNAME Database Relation

FILES

The FILES table is populated as data is archived. It contains a
record-by filename, extension, and version number-of each file written
to the optical disk.

Field

archive_class

dataset_name

dir_sec

diskname

extension

fits

fn_version

owner

size

tuple_id

version

Description

File archive class

Dataset name of file

Optical disk directory sector offset

Name of the optical disk containing file

File name extension

Flag indicating FITS format

File name version

Owner of file

Maximum size of dataset, in bytes

Tuple ID of files record

Version of file

Table 11.6: Contents of the FILES Database Relation
193