2MAPPS Software Interface Specification DBM09 3.1 98/02/19 Interface Name: DBMAN/DB Scan Data Interface Type of Interface: Database (Informix) Field Data Specification Written By: DBMAN _______________________________ T. Evans Read By: Informix DB Description: DBMAN loads 2MASS data into the Informix 2MASS database. This SIS describes the DB fields (AKA "table columns") for the survey scan data. Note also that data for calibration scans will be kept in a separate calibration DB, designed for storing data for numerous scans of the same areas of sky. Descriptions of other DB data are found in the other DBMxx SISs. Also, information from each DBMAN run will also be written to a UNIX summary file. The DB table containing this data from survey scans is named "scan_dat", and the table containing this data from calibration scans is named "scan_dat_c". Both are in the "tmass" DB. This data belongs to a group of data labelled the "scan DB" for convenience, to separate it from the extracted source list data labelled the "source DB". There are 4 different "scopes" of the data in the "scan DB": tile, night/ hemisphere, scan, and coadd. Except for tile and night/hemisphere (hereafter called simply "night"), each scope is a subset of the one preceeding it; for example, there are up to 999 scans per night, with x coadds for each scan, etc. Additionally, much of the night data, mainly calibration data, have duplicate fields for each band. The entire sky is covered by overlapping strips called "tiles", which define the strips to be scanned in the survey. Thus each scan belongs to exactly one tile, but each tile may be scanned more than once, usually on different nights, until data having acceptable quality is taken. If a field is not applicable or contains a "bad or N/A measurement value" (see previous 2MAPPS SISs for details) for a certain entry, the field will contain "NULL" values as defined by the DB. The descriptions below contain the following information: 1. "Name" contains the names of the DB fields or table columns. Note that they are all in lower case, because the DB doesn't distinguish between upper and lower case names. If there is a number in parentheses after the name, please refer to the numbered notes at the end of the descriptions for more information. Some fields are repeated 4 times, once for each corner, but are found only once in the description below; these fields contain "<#>" in the name, where "#" ranges from 1 to 4. In addition, some fields are repeated 3 times, once for each band, but are found only once in the description below; these fields contain "" in the name, where "b" is understood to mean "j", "h", and "k". NOTE: The "cntr" column MUST be the first column in each table. 2. "Description" contains short descriptions of the field contents. 3. "Units" contains the units of the values in the fields. 4. "DBType" contains the DB data storage types for the fields. Note that some data types are further defined by values in parentheses following the type name. Also, these types are NOT cast in stone and could change. 5. "Null" indicates (y/n) whether the DB fields accept NULL values. 6. "Idx" contains a code indicating whether fields are indexed and what type of indexes they have. If the code is "0", the field is not indexed. If it is "1", the field has a simple index. If there is a "u" after the digit(s), the index is a "unique" one. If the code has a 2-digit number, the first digit indicates to which composite index the field belongs, and the second digit indicates the ordering of the fields within the composite index. 7. "Fmt" contains a C-like description of the best formats for displaying the field contents, *excluding* a leading space for field separation. 8. "Tbl" contains the (sub-)table ID to which the fields belong. NOTE: The "cntr" field will be the first field in each sub-table, and is used as a join index. The 1st sub-table ("01") is the "main" sub-table, and must contain one entry per table cntr number; any other sub-table will not contain an entry for a cntr number if its fields would all be NULL. 9. "Min" and "Std" indicate (y/n) whether the DB fields are found in the "mini" and "standard" table output views. NOTE: A line beginning with "-------" can only be used herein to delineate the section of field/data dictionary lines seen below. Name Description Units DBType Null Idx Fmt Tbl Min Std ----------------------------------------------------------------------------------------------------------------------------------------- cntr entry counter (key) number (unique within table) - integer n 1u 6d 01 y y hemis hemisphere (N/S) of observation - char(1) n 21u 1s 01 y y date observation date - date n 22u yymmdd 01 y y scan scan number (unique within date) - smallint n 23u 3hd 01 y y tile_id tile ID number - integer n 1 5d 01 n y ra_ctr right ascension (J2000 decimal deg) of scan center deg decimal(9,6) n 1 10.6f 01 y y dec_ctr declination (J2000 decimal deg) of scan center deg decimal(8,6) n 1 10.6f 01 y y glon_ctr galactic longitude (decimal deg) of scan center deg decimal(9,6) n 1 10.6f 01 n y glat_ctr galactic latitude (decimal deg) of scan center deg decimal(9,6) n 1 10.6f 01 n y x_ctr unit sphere x value of scan center - decimal(9,9) n 0 12.9f 01 n n y_ctr unit sphere y value of scan center - decimal(9,9) n 0 12.9f 01 n n z_ctr unit sphere z value of scan center - decimal(9,9) n 0 12.9f 01 n n ra_<#> (1) right ascension (J2000 decimal deg) of scan corner <#> deg decimal(9,6) n 1 10.6f 01 n y dec_<#> declination (J2000 decimal deg) of corner <#> deg decimal(8,6) n 1 10.6f 01 n y direc direction of scan -- north/south-bound (n/s) - char(1) n 0 1s 01 n y quality quality flag for scan (0-10) - smallint n 1 2hd 01 y y phot_flg scan photometric flag (y/n) - char(1) n 0 1s 01 y y ut_beg beginning UT of scan data time datetime(h-s) n 0 %H:%M:%S 01 n n ut_end ending UT of scan data time datetime(h-s) n 0 %H:%M:%S 01 n n tel_temp telescope temperature (deg C) at beginning of scan degC decimal(3,1) n 0 5.1f 01 n n air_temp air temperature (deg C) at beginning of scan degC decimal(3,1) n 0 5.1f 01 n n rel_humid relative humidity (%) at beginning of scan % smallint n 0 2hd 01 n n baro_p barometric pressure (mmHg) at beginning of scan mmHg decimal(3,1) n 0 4.1f 01 n n airm_beg beginning airmass of scan - decimal(5,4) n 0 6.4f 01 n y airm_end ending airmass of scan - decimal(5,4) n 0 6.4f 01 n y airm_avg average scan airmass - decimal(5,4) n 1 6.4f 01 y y sstd_file name of secondary photometric standards file used - char(8) y 0 10s 01 n y _zp photometric zero-point for scan mag decimal(4,3) n 1 6.3f 01 y y _zperr rms error from zero-point mag decimal(4,3) n 1 6.3f 01 y y _alg (2) algorithm used for determining zero-point - char(2) n 0 2s 01 n n _n_det number of point sources detected in - integer n 1 6d 01 y y j_n_snr10 number of J point sources with SNR>10 (instrumental m<=15.8) - integer n 0 6d 01 n n h_n_snr10 number of H point sources with SNR>10 (instrumental m<=15.1) - integer n 0 6d 01 n n k_n_snr10 number of K point sources with SNR>10 (instrumental m<=14.3) - integer n 0 6d 01 n n n_ext number of regular extended sources detected in scan - integer n 1 6d 01 y y n_ext_snr07 number of regular extended sources detected with 0<=SNR<7 - integer n 0 6d 01 n n n_ext_snr720 number of regular extended sources detected with 7<=SNR<20 - integer n 0 6d 01 n n n_ext_snr20 number of regular extended sources detected with 20<=SNR - integer n 0 6d 01 n n n_lcsb number of LCSB sources detected in scan - integer n 1 6d 01 y y n_lcsb_snr07 number of LCSB sources detected with 0<=SNR<7 - integer n 0 6d 01 n n n_lcsb_snr720 number of LCSB sources detected with 7<=SNR<20 - integer n 0 6d 01 n n n_lcsb_snr20 number of LCSB sources detected with 20<=SNR - integer n 0 6d 01 n n _r1_norm Read1 mag normalization value mag decimal(5,4) n 1 7.4f 01 n y _r1_norm_rms rms of Read1 mag normalization value mag decimal(5,4) y 1 7.4f 01 n y _fbg_avg average frame background for scan DN decimal(7,2) n 1 8.2f 01 n y _fbg_rms rms of avg frame background for scan DN decimal(7,3) n 0 8.3f 01 n y _fbg_min minimum frame background for scan DN decimal(7,2) n 0 8.2f 01 n n _fbg_max maximum frame background for scan DN decimal(7,2) n 0 8.2f 01 n n _shape_avg average seeing shape for scan - decimal(6,3) n 1 7.3f 01 y y _shape_rms rms of avg seeing shape for scan - decimal(6,3) n 0 7.3f 01 y y _2mrat average 2nd image moment ratio for scan - decimal(6,3) n 0 7.3f 01 y y bmg_ntot total number of bandmerged sources - integer n 1 6d 01 n y bmg_j_fr fraction of all bandmerged sources that are J-only - decimal(5,4) n 0 6.4f 01 n n bmg_h_fr fraction of all bandmerged sources that are H-only - decimal(5,4) n 0 6.4f 01 n n bmg_k_fr fraction of all bandmerged sources that are K-only - decimal(5,4) n 0 6.4f 01 n n bmg_jh_fr fraction of all bandmerged sources that are JH - decimal(5,4) n 0 6.4f 01 n n bmg_jk_fr fraction of all bandmerged sources that are JK - decimal(5,4) n 0 6.4f 01 n n bmg_hk_fr fraction of all bandmerged sources that are HK - decimal(5,4) n 0 6.4f 01 n n bmg_jhk_fr fraction of all bandmerged sources that are JHK - decimal(5,4) n 1 6.4f 01 y n bmg_nsnr10 number of SNR>10 (j<=15.8, h<=15.1, k<=14.3) bandmerged srcs - integer n 1 6d 01 n y bmg_j_fr10 J-only frac.of SNR>10 (j<=15.8, h<=15.1, k<=14.3) bmrgd srcs - decimal(5,4) n 0 6.4f 01 n y bmg_h_fr10 H-only frac.of SNR>10 (j<=15.8, h<=15.1, k<=14.3) bmrgd srcs - decimal(5,4) n 0 6.4f 01 n y bmg_k_fr10 K-only frac.of SNR>10 (j<=15.8, h<=15.1, k<=14.3) bmrgd srcs - decimal(5,4) n 0 6.4f 01 n y bmg_jh_fr10 JH frac.of SNR>10 (j<=15.8, h<=15.1, k<=14.3) bmrgd srcs - decimal(5,4) n 0 6.4f 01 n y bmg_jk_fr10 JK frac.of SNR>10 (j<=15.8, h<=15.1, k<=14.3) bmrgd srcs - decimal(5,4) n 0 6.4f 01 n y bmg_hk_fr10 HK frac.of SNR>10 (j<=15.8, h<=15.1, k<=14.3) bmrgd srcs - decimal(5,4) n 0 6.4f 01 n y bmg_jhk_fr10 JHK frac.of SNR>10 (j<=15.8, h<=15.1, k<=14.3) bmrgd srcs - decimal(5,4) n 1 6.4f 01 y y n_tycho number of Tycho stars used in position reconstruction - integer y 0 6d 01 y y ra_tycho_sig sigma of source RAs with respect to Tycho RAs arcsec decimal(6,4) n 0 7.4f 01 n n dec_tycho_sig sigma of source Decs with respect to Tycho Decs arcsec decimal(6,4) n 0 7.4f 01 n n pct_spanned percent of scan length spanned by reference stars % decimal(5,2) n 1 6.4f 01 n n n_usnoa number of USNOA stars associated with sources - integer n 0 6d 01 y y pct_usn_assoc percent of USNOA stars in scan associated with sources % decimal(5,2) n 1 6.4f 01 n n pct_bmg_assoc percent of clean bandmerged sources associated with USNOA % decimal(5,2) n 1 6.4f 01 n n dx_jh cross-scan array J-H translation arcsec decimal(7,3) n 0 8.3f 01 n n dy_jh in-scan array J-H translation arcsec decimal(7,3) n 0 8.3f 01 n n dx_jk cross-scan array J-K translation arcsec decimal(7,3) n 0 8.3f 01 n n dy_jk in-scan array J-K translation arcsec decimal(7,3) n 0 8.3f 01 n n _rotat chip rotation with respect to scan direction deg decimal(8,6) n 0 9.6f 01 n n _dxstep_avg average in-scan frame-to-frame step size cpix decimal(8,4) n 0 9.4f 01 n n _dystep_avg average cross-scan frame-to-frame step size cpix decimal(8,4) n 0 9.4f 01 n n db_date date-time stamp of scan data entry into DB - datetime(y-s) n 0 %Y/%m/%d %H:%M:%S 01 n n night_key (3) key to night data record - integer n 0 4d 01 n n ----------------------------------------------------------------------------------------------------------------------------------------- total # columns = 55, # bytes/row = 236 ----------------------------------------------------------------------------------------------------------------------------------------- NOTES: (1)Corner positions: The four ra_<#> and dec_<#> fields, where "#" ranges from 1 to 4, contain the RA and Dec. positions of the four corners of the fully-covered area of the scan (i.e. the area covered by all three bands). The corners are numbered as follows: 1: eastern corner at scan start 2: western corner at scan start 3: eastern corner at scan end 4: western corner at scan end (2)_alg: flag that identifies the algorithm used to determine scan zero-point na = nightly average lf = linear fit 4h = 4-hour linear fit (3)night_key The night_key field will be set to the key of the record containing the corresponding night data in the "scan DB".