2MAPPS Software Interface Specification DBM05 3.0 97/05/28 Interface Name: DBMAN/DB Subtracted Source 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 data on sources subtracted from each galaxy candidate. 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. There will actually be two sets of DB tables containing subtracted src information: one set containing subtracted srcs from the point src list, and the other set containing subtracted srcs from the extended src list. The two DB tables containing this data from survey scans are named "sub_pt_src" and "sub_ext_src". The tables containing this data from calibration scans are named "sub_pt_src_c" and "sub_ext_src_c". All are in the "tmass" DB. Each ext. src data record (see SIS DBM02) provides the number of subtracted and blanked sources within its image. Each subtracted source found in these tables can be linked back to its own point/extended src data through the hemis + date + scan (+ coadd) + sub_id "key", and can be linked to the image from which it was removed through the hemis + date + scan + coadd + img_id "key". If a field is not applicable or contains a "bad or N/A measurement value" (see previous 2MAPPS SISs for details) for a certain source, the field will contain "NULL" values as defined by the DB. The descriptions below contain the following information: 1. "Name" is the name 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 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, especially for the position fields. 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 8d 01 y y hemis hemisphere (N/S) of observation - char(1) n 21 1s 01 n y date observation date - date n 22 yymmdd 01 n y scan scan number (unique within date) - smallint n 23 3hd 01 n y coadd 3-digit coadd number - smallint n 24 03hd 01 n y img_id processed image source ID number - integer n 25 6d 01 n y sub_id subtracted source ID number - integer n 1 6d 01 n y x_coadd x (cross-scan) position (coadd coord.) of subtracted source arcsec decimal(4,1) n 0 6.1f 01 n n y_coadd y (in-scan) position (coadd coord.) of subtracted source arcsec decimal(5,1) n 0 6.1f 01 n n _f_sub flux of subtracted source DN integer n 0 6d 01 y y _r_sub radius of subtracted source arcsec integer n 0 6d 01 y y ext_key (1) key to extended source's DB record - integer n 0 7d 01 n n sub_key (2) key to subtracted source's DB record - integer n 0 9d 01 n n ----------------------------------------------------------------------------------------------------------------------------------------- total # columns = 17, # bytes/row = 61 ----------------------------------------------------------------------------------------------------------------------------------------- NOTES: (1)Extended source data key: no default (non-null) The ext_key field will be set to the key of the record in the extended source DB containing the ext. src data for the src image being processed. The ext. src data will also have the same date, hemisphere, scan, coadd, id keys. (2)Subtracted src record key: no default (non-null) The sub_key field will be set to the key of the record containing the subtracted source's point or extended src data (see SISs DBM01 and DBM02). The src data will also have the same date, hemisphere, scan, (coadd,) id keys. The only difference between the two tables "sub_pt_src" and "sub_ext_src" is that the sub_key field refers to the point src DB for the first table and the ext. src DB for the second table.