2MAPPS Software Interface Specification DBM08 3.1 98/02/11 Interface Name: DBMAN/DB Night 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 night/ hemisphere data (hereafter called simply "night 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 is named "night_dat", 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. Many 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 4d 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 day_num observation day number (day 1 is 1 March 1997, 0h UT) - smallint n 1 4hd 01 n n n_seg number of segments in night (presently <= 5) - smallint n 0 1hd 01 y y phot_flg photometric flag (y/n) for the night - char(1) n 0 1s 01 y y _extinc extinction value mag decimal(5,4) n 1 7.4f 01 y y _color color value mag decimal(5,4) n 1 7.4f 01 y y _zp_ext extended src zero-point mag decimal(4,2) n 1 6.2f 01 y y ut_beg_1 beginning UT of photometric data for night segment 1 time datetime(h-s) n 0 %H:%M:%S 01 n n ut_end_1 ending UT of photometric data for night segment 1 time datetime(h-s) n 0 %H:%M:%S 01 n n _slope_1 linear fit slope for segment 1 mag decimal(6,4) y 0 8.4f 01 n y _intcpt_1 linear fit intercept for segment 1 mag decimal(6,4) y 0 8.4f 01 n y _err_1 rms error from linear fit for segment 1 mag decimal(6,4) y 0 8.4f 01 n y _zp_1 point src average zero-point for segment 1 mag decimal(6,4) y 0 8.4f 01 y y _zperr_1 rms error from point src average zero-point for seg 1 mag decimal(6,4) y 0 8.4f 01 n y ut_beg_2 beginning UT of photometric data for night segment 2 time datetime(h-s) y 0 %H:%M:%S 01 n n ut_end_2 ending UT of photometric data for night segment 2 time datetime(h-s) y 0 %H:%M:%S 01 n n _slope_2 linear fit slope for segment 2 mag decimal(6,4) y 0 8.4f 01 n y _intcpt_2 linear fit intercept for segment 2 mag decimal(6,4) y 0 8.4f 01 n y _err_2 rms error from linear fit for segment 2 mag decimal(6,4) y 0 8.4f 01 n y _zp_2 point src average zero-point for segment 2 mag decimal(6,4) y 0 8.4f 01 y y _zperr_2 rms error from point src average zero-point for seg 2 mag decimal(6,4) y 0 8.4f 01 n y ut_beg_3 beginning UT of photometric data for night segment 3 time datetime(h-s) y 0 %H:%M:%S 01 n n ut_end_3 ending UT of photometric data for night segment 3 time datetime(h-s) y 0 %H:%M:%S 01 n n _slope_3 linear fit slope for segment 3 mag decimal(6,4) y 0 8.4f 01 n y _intcpt_3 linear fit intercept for segment 3 mag decimal(6,4) y 0 8.4f 01 n y _err_3 rms error from linear fit for segment 3 mag decimal(6,4) y 0 8.4f 01 n y _zp_3 point src average zero-point for segment 3 mag decimal(6,4) y 0 8.4f 01 y y _zperr_3 rms error from point src average zero-point for seg 3 mag decimal(6,4) y 0 8.4f 01 n y ut_beg_4 beginning UT of photometric data for night segment 4 time datetime(h-s) y 0 %H:%M:%S 01 n n ut_end_4 ending UT of photometric data for night segment 4 time datetime(h-s) y 0 %H:%M:%S 01 n n _slope_4 linear fit slope for segment 4 mag decimal(6,4) y 0 8.4f 01 n y _intcpt_4 linear fit intercept for segment 4 mag decimal(6,4) y 0 8.4f 01 n y _err_4 rms error from linear fit for segment 4 mag decimal(6,4) y 0 8.4f 01 n y _zp_4 point src average zero-point for segment 4 mag decimal(6,4) y 0 8.4f 01 y y _zperr_4 rms error from point src average zero-point for seg 4 mag decimal(6,4) y 0 8.4f 01 n y ut_beg_5 beginning UT of photometric data for night segment 5 time datetime(h-s) y 0 %H:%M:%S 01 n n ut_end_5 ending UT of photometric data for night segment 5 time datetime(h-s) y 0 %H:%M:%S 01 n n _slope_5 linear fit slope for segment 5 mag decimal(6,4) y 0 8.4f 01 n y _intcpt_5 linear fit intercept for segment 5 mag decimal(6,4) y 0 8.4f 01 n y _err_5 rms error from linear fit for segment 5 mag decimal(6,4) y 0 8.4f 01 n y _zp_5 point src average zero-point for segment 5 mag decimal(6,4) y 0 8.4f 01 y y _zperr_5 rms error from point src average zero-point for seg 5 mag decimal(6,4) y 0 8.4f 01 n y ----------------------------------------------------------------------------------------------------------------------------------------- total # columns = 99, # bytes/row = 385 -----------------------------------------------------------------------------------------------------------------------------------------