Changes between Version 7 and Version 8 of calib_info_in_pstamp

Timestamp:

Aug 1, 2013, 3:27:14 PM (13 years ago)

Author:

bills

Comment:

--

calib_info_in_pstamp

@@ -21 +21 @@
 ZPCALERR    F32     error in calibrated zero point. Zero for ubercal exposures. Also saved in relExp.zpt_obs
                     
-DVOFLAGS    U32     photometry calibration flags extracted from dvo image flags. Includes flag indicating if ubercal
+DVOFLAGS    U32     photometry calibration flags extracted from dvo image flags. Includes flag indicating if the exposure is an ubercal
                     exposure.
 UCALDIST    U32     Distance to ubercaled image XXX: 0 for ubercaled exposures. XXX: Describe more completely.
-UCALFILE    STR     base name of ubercal file (in lieu of ubercal version)
-DVODB       STR     base name of DVO database used for calibration (where information was extracted)
+UCALFILE    STR     base name of ubercal file (serves as ubercal version)
+DVODB       STR     base name of DVO database used for calibration (Source of calibration information)
 
-CALDATE     STR     timestamp relExp was set to calibrated
-PS1REL      STR     ippRelease name (for example 3PI.PV1) for processing/calibration
-                    XXX: drop '1' ? change PS1 to IPP ?
+CALDATE     STR     timestamp relExp was last updated (presumably when it's state was changed to calibrated)
+PSREL       STR     ippRelease name for processing/calibration (for example 3PI.PV1) 
+
 }}}
 
@@ -36 +36 @@
 Related keywords
 {{{
-ZPT_OBS     psastro zero point and error
+ZPT_OBS     zero point and error measured by psastro
 ZPT_ERR
 PSREFCAT    base name of reference catalog used by psastro.
 }}}
 
-Issues
- * While there is a single zero point for an exposure the data is extracted from the DVO images table. There are a small number of exposures (15) where the zero point (MCAL) is not the same for all chips. This problem will be ignored and the first value will be chosen.