2MAPPS Software Interface Specification DBM10 3.1 98/02/19 Interface Name: DBMAN/DB Coadd 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 tile 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 "coadd_dat", and the table containing this data from calibration scans is named "coadd_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. 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 7d 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 coadd 3-digit coadd number - smallint n 24u 03hd 01 y y band band identifier (j, h, or k) - char(1) n 25u 1s 01 y y n_x number of columns (x) in coadd image - smallint n 0 4hd 01 n n n_y number of lines (y) in coadd image - smallint n 0 4hd 01 n n x_co_<#> (1) x U-scan position of coadd corner <#> pix decimal(7,3) n 0 9.3f 01 n n y_co_<#> y U-scan position of coadd corner <#> pix decimal(8,3) n 0 10.3f 01 n n ra_ctr right ascension (J2000 decimal deg) of coadd center deg decimal(9,6) n 1 10.6f 01 y y dec_ctr declination (J2000 decimal deg) of coadd center deg decimal(8,6) n 1 10.6f 01 y y twist_ang twist angle of coadd image (degrees E of N) deg decimal(9,6) n 0 10.6f 01 n y x_ctr unit sphere x value of coadd center - decimal(9,9) n 0 12.9f 01 n n y_ctr unit sphere y value of coadd center - decimal(9,9) n 0 12.9f 01 n n z_ctr unit sphere z value of coadd center - decimal(9,9) n 0 12.9f 01 n n sky background sky value of coadd DN decimal(6,2) n 1 7.2f 01 y y noise background sky noise of coadd DN decimal(5,2) n 1 6.2f 01 y y fwhm FWHM used for source detection - decimal(5,2) n 0 6.2f 01 n y n_det number of detections from coadd - integer n 1 6d 01 y y n_solo number of solo detections blanked in frames - integer n 0 6d 01 n y shape_avg average "shape" value for coadd - decimal(6,3) n 1 7.3f 01 y y shape_sig one-sigma uncertainty in shape average - decimal(5,3) n 1 6.3f 01 y y n_src_sh number of sources in shape distribution - smallint n 1 5d 01 n y psf_id ID number of PSF used for coadd - smallint y 1 5d 01 y y ap_cor aperture correction used for coadd mag decimal(5,4) y 0 7.4f 01 y y ap_cor_rms rms of aperture correction used for coadd mag decimal(5,4) y 0 7.4f 01 y y psf_norm PSF mag normalization used for coadd mag decimal(5,4) y 0 7.4f 01 y y psf_norm_rms rms of PSF mag normalization used for coadd mag decimal(5,4) y 0 7.4f 01 y y m_thr GALWORKS limiting mag used mag decimal(4,2) y 0 6.2f 01 n n m_thr_lcsb GALWORKS limiting mag used for LCSBs mag decimal(4,2) y 0 6.2f 01 n n sh_thr GALWORKS sh score threshold used - decimal(3,1) y 0 4.1f 01 n n wsh_thr GALWORKS wsh score threshold used - decimal(3,1) y 0 4.1f 01 n n v_thr GALWORKS vmean & vint score threshold used - decimal(3,1) y 0 4.1f 01 n n r23_thr GALWORKS r23 score threshold used - decimal(3,1) y 0 4.1f 01 n n bkgnd_sig GALWORKS background uncertainty for coadd - decimal(5,2) y 0 6.2f 01 n n tile_id key to tile data record - integer n 0 5d 01 n n night_key (2) key to night data record - integer n 0 4d 01 n n scan_key key to scan data record - integer n 0 6d 01 n n ----------------------------------------------------------------------------------------------------------------------------------------- total # columns = 47, # bytes/row = 172 ----------------------------------------------------------------------------------------------------------------------------------------- NOTES: (1)Corner positions: The four x_co_<#> and y_co_<#> fields, where "#" ranges from 1 to 4, contain the U-scan coordinate positions of the four corners of the coadd. Corner #1 is at the 0,0 pixel of the coadd. (2)night_key, scan_key The night_key and scan_key fields will be set to the keys of the records containing the corresponding night and scan data in the "scan DB".