Changes between Version 2 and Version 3 of ippReleaseManagement

Timestamp:

Sep 20, 2012, 3:22:15 PM (14 years ago)

Author:

bills

Comment:

--

ippReleaseManagement

@@ -25 +25 @@
  * DVO catalogs
 
-The data is the results of runs through the various stages of the IPP pipeline. For the most part the IPP does not have a very good record of which data went into the various releases. For example given a single frame detection in the IPP database, there is no direct method to determine which version of the processed pixels the detections were measured on. Making the answer to this and other similar questions easy to obtain is the primary purpose of this
+The data is the results of runs through the various stages of the IPP pipeline. For the most part the IPP does not have a very good record of which data went into the various releases. For example, given a single frame detection in the IPP database, there is no direct method to determine which version of the processed pixels the detections were measured on. Making the answer to this and other similar questions easy to obtain is the primary purpose of this
 project.
 
@@ -70 +70 @@
 We currently have no way of tracking which of the various processing runs are intended for end user use
 and those that are the results of testing. The postage stamp server currently attempts to work around this
-problem but the results have been mixed. By specifically identifying the data that should be released this
-problem will be solved.
-
+problem but the results have been mixed. By specifically identifying the data that should be released it
+will be easy to indentify those runs that should not be released as well. 
 
 === Stacked Images ===
@@ -97 +96 @@
 Management of difference images is a subject for further research and will be discussed later.
 
+== Definition of an IPP release ==
+
+A collection of data "released" to the PS1SC community will be represented in the IPP database by a row 
+in 2 new tables called "ippRelease" and "survey". Here are the proposed definitions
+
+{{{
+mysql> describe survey;
++-------------+--------------+------+-----+---------+-------+
+| Field       | Type         | Null | Key | Default | Extra |
++-------------+--------------+------+-----+---------+-------+
+| surveyID    | tinyint(8)   | NO   | PRI | 0       |       | 
+| name        | varchar(16)  | YES  | MUL | NULL    |       | 
+| description | varchar(255) | YES  |     | NULL    |       | 
++-------------+--------------+------+-----+---------+-------+
+3 rows in set (0.00 sec)
+
+mysql> describe ippRelease;
++-------------+-------------+------+-----+---------+----------------+
+| Field       | Type        | Null | Key | Default | Extra          |
++-------------+-------------+------+-----+---------+----------------+
+| rel_id      | smallint(6) | NO   | PRI | NULL    | auto_increment | 
+| surveyID    | tinyint(8)  | YES  | MUL | NULL    |                | 
+| releaseName | varchar(16) | YES  | MUL | NULL    |                | 
+| state       | varchar(16) | YES  | MUL | NULL    |                | 
+| dataRelease | tinyint(8)  | YES  |     | NULL    |                | 
++-------------+-------------+------+-----+---------+----------------+
+5 rows in set (0.00 sec)
+}}}
+
+The survey table is a copy of the PSPS table Survey. Example entries are
+
+{{{
++----------+------+------------------------------------+
+| surveyID | name | description                        |
++----------+------+------------------------------------+
+|        0 | 3PI  | PS1 3PI Survey                     | 
+|        1 | MD01 | PS1 MD01 XMM-LSS-DXS 022224-043000 | 
++----------+------+------------------------------------+
+}}}
+
+The columns in ippRelease are 
+ * rel_id primary key for the row
+ * surveyID for to the survey that the data in a particular release contains
+ * releaseName - human friendly identifier for the release
+ * 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 data is not yet ready to be available by default
+   * archive - the release contains the results of a previous processing of the data that has been superseded.
+ * dataRelease - If not null, the dataRelease value in the corresponding PSPS tables.
+
+{{{
++--------+----------+-------------+---------+-------------+
+| rel_id | surveyID | releaseName | state   | dataRelease |
++--------+----------+-------------+---------+-------------+
+|      1 |        0 | 3PI.nightly | active  |        NULL | 
+|      2 |        0 | 3PI.GR0     | active  |           0 | 
+|      3 |        0 | 3PI.GR1     | pending |           1 | 
+|      4 |        0 | SAS.V8      | archive |           8 | 
+|      5 |        0 | SAS.V9      | active  |           9 | 
++--------+----------+-------------+---------+-------------+
+}}}
 
 
@@ -109 +169 @@
 
 
-
-
-
-