Changes between Version 16 and Version 17 of ippReleaseManagement

Timestamp:

Aug 9, 2013, 10:19:40 AM (13 years ago)

Author:

bills

Comment:

--

ippReleaseManagement

@@ -179 +179 @@
  * state - current status of the release. Several values have been identified
    * active - results for the release are currently available to the community
-   * pending - release identified, construction may have begun, but the results not yet ready to be available
+   * pending - release identified, construction may have begun, but the results not yet ready to be available (not currently used)
    * archive - the release contains the results of a previous processing of the data that has been superseded.
    * drop - the results of the release have been abandoned and should be ignored
@@ -187 +187 @@
  * ubercal_file - file name of fits table that provided the ubercal calibrations
 
-Here is an example of how this system might work for the 3pi survey. Assume that we have finished the
-current 2012 grand reprocessing and are ready to start the next one. 
+Here is an example of how this system is being used for the 3pi survey. 
 
 {{{
@@ -202 +201 @@
 }}}
 
-There are 4 releases shown here. 
+There are 3 releases shown here. 
 
 The 3PI.nightly release is active. Data is being currently added to it by the IPP nightly science
 processing. Since these data are not being ingested into PSPS the dataRelease column is -1.
 
-3PI.PV1 refers to the 2012 3PI "grand reprocessing". This release is active. dataRelease == 1
-
+3PI.PV1 refers to the 2012 3PI "grand reprocessing". This release is current. dataRelease == 1
 
 3PI.PV2 is the next grand reprocessing dataRelease == 2. The state of this release is active.
@@ -277 +275 @@
  * processed - The initial results of the camera stage for the exposure.
  * poor_quality - The camRun failed to find a solution for the exposure.
- * calibrated - The calibration information (zero point and astrometry) has been updated by a DVO calibration operation
+ * calibrated - The calibration information  has been updated by a DVO calibration operation
  * psps - The information from the exposure has been added to the PSPS database corresponding to the release.
  * drop - This relExp is to be dropped for some reason.
 
+==== calibration ====
+After an exposure is "calibrated" in DVO the data is extracted and certain columns are updated in the relExp table. 
+ * state is changed to calibrated
+ * zpt_obs and zpt_stdev are updated
+ * flags is set to the value of the FLAGS column for the row in the DVO images table used for the calibrated data
+   * The only interesting value here is bit 0x200. If set the zero point came from the ubercal process
+ * mcal (zero point offset due to clouds" is set
+ * ubecal_dist - for non ubercal exposures the distance to the "nearest" ubercal exopsure.
+
+The process used to update the calibration information for 3PI.PV1 is described [wiki:3pi.pv1.calibrationextraction here].
 
 == Released Stack ==