During the operation of the assign code the user may choose a number of ``sky fiber'' positions which were not originally in the catalog. These sky positions are converted from their plate coordinates or refracted coordinates back to catalog positions and added to this table. This FITS table should serve as both an input and output file format for the fiber assignment code. OBJ_PKEY serves as the primary key for this table.
This table should contain only information about the objects. For the sake of convenience the column PIVOTID is included. This denotes the pivot (and thus fiber) assigned to an object; however, inclusion of PIVOTID denormalizes the schema of the tables as a database.
Keywords for coordinate systems are derived from the proposed WCS conventions and resolution R3 of the OGIP recommendations.
Detailed definitions of the FITS keywords used in this HDU are available in a data dictionary.
XTENSION= 'TABLE ' / ASCII table extension BITPIX = 8 / number of bits per data pixel NAXIS = 2 / always 2 for a FITS table NAXIS1 = xxx / number of chars needed to describe members NAXIS2 = xxx / number of objects in the catalogs PCOUNT = 0 / required FITS extension keyword GCOUNT = 1 / required FITS extension keyword TFIELDS = 16 / Number of columns in the table EXTNAME = 'MOS_Input_Catalog' / This table describes MOS input catalogs EXTVER = 1 / Unique index of this Config table in file GRPID1 = 1 / member of group with EXTVER=1 in same file COMMENT Because GRPID1 is positive we need no GRPLC1 card DATE = 'yyyy-mm-ddThh:mm:ss.sssZ' / Date of construction of catalog table COMMENT Various keywords specifying the desired field center RA_PNT = xxx.xxxxxxx / Right Ascension of field center [degree] DEC_PNT = xxx.xxxxxxx / Declination of field center [degree] RADECPNT= 'FKx ' / Coordinate system for RA_PNT and DEC_PNT EQUINPNT= xxxxxx.xxxxxx / Equinox for RA_PNT and DEC_PNT [annum] MJD_PNT = 24xxxxx.xxxxxxxxx / needed if RADECPNT is FK4 [diem] DATE_PNT= 'yyyy-mm-ddThh:mm:ss.sssZ' / Time of planned observation TPRIMKEY= 'OBJ_PKEY' / Database Primary Key COMMENT In a relational sense this key should not be placed here. COMMENT Its presence permits the possibility of data that disagree. NFORKY = 1 / Number of foreign key joins described TFORKY1 = 'PIVOTID' / Foreign key TFOREF1 = 'MOS_Hardware' / some kind of reference to the other table TBCOL1 = 1 / First character in column TFORM1 = 'A32 ' / Fortran 77 format of column TTYPE1 = 'UNAME ' / TBCOL2 = 33 / First character in column TFORM2 = 'F11.7 ' / Fortran 77 format of column TTYPE2 = 'RA_OBJ ' / TUNIT2 = 'degree ' / Unit of measure of column TBCOL3 = xx / First character in column TFORM3 = 'F11.7 ' / Fortran 77 format of column TTYPE3 = 'DEC_OBJ ' / TUNIT3 = 'degree ' / Unit of measure of column TBCOL4 = xx / First character in column TFORM4 = 'I4 ' / Fortran 77 format of column TTYPE4 = 'PRIO ' / TBCOL5 = xx / First character in column TFORM5 = 'F7.3 ' / Fortran 77 format of column TTYPE5 = 'MAG ' / TNULL5 = '-99.999 ' / Indicates data not provides in input TBCOL6 = xx / First character in column TFORM6 = 'A128 ' / Fortran 77 format of column TTYPE6 = 'NAME ' / TBCOL7 = xx / First character in column TFORM7 = 'F13.6 ' / Fortran 77 format of column TTYPE7 = 'EQUINOX ' / TUNIT7 = 'annum ' / Unit of measure of column TBCOL8 = xx / First character in column TFORM8 = 'A128 ' / Fortran 77 format of column TTYPE8 = 'CAT_FILE' / TBCOL9 = xx / First character in column TFORM9 = 'I6 ' / Fortran 77 format of column TTYPE9 = 'OBJ_PKEY' / Primary key for table of objects TBCOL10 = xx / First character in column TFORM10 = 'I3 ' / Fortran 77 format of column TTYPE10 = 'PIVOTID ' / Key pointing into fiber table TNULL10 = ' -1 ' / Indicates no fiber is assigned to object TBCOL11 = xx / First character in column TFORM11 = 'A8 ' / Fortran 77 format of column TTYPE11 = 'RADECSYS' / TNULL11 = 'NULL ' / Indicates data not provided in input TBCOL12 = xx / First character in column TFORM12 = 'F9.4 ' / Fortran 77 format of column TTYPE12 = 'PM_RA ' / TUNIT12 = 'arcsec/(Julian annum)' / Unit of measure of column TNULL12 = '-999.9000' / Indicates data not provided in input TBCOL13 = xx / First character in column TFORM13 = 'F9.4 ' / Fortran 77 format of column TTYPE13 = 'PM_DEC ' / TUNIT13 = 'arcsec/(Julian annum)' / Unit of measure of column TNULL13 = '-999.9000' / Indicates data not provided in input TBCOL14 = xx / First character in column TFORM14 = 'F17.9 ' / Fortran 77 format of column TTYPE14 = 'MJD_WCS ' / TUNIT14 = 'diem ' / Unit of measure of column TNULL14 = '-999999.000000000' / Indicates data not provided in input TBCOL15 = xx / First character in column TFORM15 = 'F7.4 ' / Fortran 77 format of column TTYPE15 = 'PARALLAX' / TUNIT15 = 'arcsec ' / Unit of measure of column TNULL15 = '-9.9999 ' / Indicates data not provided in input TBCOL16 = xx / First character in column TFORM16 = 'F13.3 ' / Fortran 77 format of column TTYPE16 = 'RAD_VEL ' / TUNIT16 = 'm/s ' / Unit of measure of column TNULL16 = '300000000.000' / Indicates data not provided in input ENDThe header is padded with ASCII blanks such that it consists of a positive integer multiple of 2880 bytes (36 card images of 80 characters).
The value of the keyword EXTNAME deserves further scrutiny.
Other kinds of FITS groups for MOS data may become desirable; e.g.,
groups which relate calibration exposures to sky exposures. It may
also be desirable to insert other kinds of documentary data using
additional standard and/or MOS-specific keywords. The DATE
keywords present an obvious problem as we enter a new century, but
the FITS community has not yet developed an alternative scheme.
There are two different input formats for user catalogs. The first does not require catalog-style astrometric accuracy. For objects read from such a file the table will indicate the lack of information by the use of the FITS ASCII Table TNULL conventions. The other format does require the space motion and parallax components.