Changes between Version 14 and Version 15 of ippReleaseManagement

Timestamp:

Jan 25, 2013, 11:23:59 AM (13 years ago)

Author:

bills

Comment:

--

ippReleaseManagement

@@ -112 +112 @@
 +-------------+--------------+------+-----+---------+-------+
 3 rows in set (0.00 sec)
-
-
 }}}
 
@@ -155 +153 @@
 }}}
 
+We may omit obsolete surveys.
+
 === ippRelease ===
 {{{
@@ -173 +173 @@
 The columns in ippRelease are 
  * rel_id - the primary key for the row
- * surveyID of the corresponding
+ * surveyID of the corresponding survey
  * releaseName - a human friendly identifier for the release
  * state - current status of the release. Several values have been identified
@@ -184 +184 @@
 
 Here is an example of how this system might work for the 3pi survey. Assume that we have finished the
-current grand reprocessing and are ready to start the next one. 
-
-{{{
-mysql> select * from ippRelease where releaseName like '3%' order by priority desc;
+current 2012 grand reprocessing and are ready to start the next one. 
+
+{{{
+mysql> select * from ippRelease where releaseName like '3PI%' order by priority desc;
 +--------+----------+-------------+---------------+-------------+----------+
 | rel_id | surveyID | releaseName | release_state | dataRelease | priority |
@@ -220 +220 @@
 data will be returned from a lower priority release. 
 
+A typical situation is that of a recent exposure. Since it isn't found in the current release the
+nightly science version is selected.
+
 Note: This scheme will be used for request where the user has not explicitly listed the release of interest.
 All IPP data will be still be available if the user can identify it. 
+
+Once we are ready to make data from the next release available, the release_state and priorities will
+be adjusted accordingly.
 
 == Released Exposure ==
@@ -271 +277 @@
 
 The full results and history of any calibration operations will be stored in files referenced by the relExp's path_base. 
-
-=== Life cycle of a relExp ===
-
-
 
 == Released Stack ==