Changes between Version 7 and Version 8 of pstamp_2015-04-changes

Timestamp:

Apr 15, 2015, 1:02:10 PM (11 years ago)

Author:

bills

Comment:

--

pstamp_2015-04-changes

@@ -8 +8 @@
 Some of the details of this may seem somewhat unexpected. When reading this keep in mind that the postage stamp server is implemented in a distributed maner. There is the
 IPP side and the PSI front end. There are some usage patterns that only use the IPP part. These must continue to be supported. The IPP portion does not have accounts. The PSI side does not manage
-permissions for users. In the end control of the access to the pixels is through the HTTP server's list of hosts.
+permissions for users. In the end, control of the access to the pixels is through the HTTP server's list of hosts.
 
 == Version 1 of the request file is no longer supported. A version 2 file with a valid email address in the request header is required ==
@@ -19 +19 @@
 
 If the email address' domain is unknown to the system. Postage stamp results will be given the default access level (1) unless the specific user has been flagged with greater access level.
-A user with the default access level may get results from single frame observations made prior to 2015-03-01. Access to stacks is controlled using a new accessLevel column in the ippRelease table in the
-IPP database. 
+A user with the default access level may get results from single frame observations made prior to 2015-03-01. Access to stacks 
+is controlled using a new accessLevel column in the ippRelease table in the IPP database. 
 
 == The postage stamps images and other results may be directed to a different data store location than previously ==
 
 Currently most postage stamp results are posted to filesets in a single data store product "pstampresults". This product is accessible through HTTP requests from
-a set list of identified PS1SC institutions. In the new implementation each institution will get it's own data store product.  For example requests
+a set list of all the identified PS1SC institutions. In the new implementation each institution will get it's own data store product.  For example requests
 from ifa.hawaii.edu users will go to an ifa specific data store product. Results for users from Durham will go to a directory specific to that institution. Each product will have
 it's own list of allowable IP addresses.  Certain users (for example MOPS) will have their own data store products.
@@ -32 +32 @@
 
 === Other implementation changes ===
-There are also some minor changes to the postage stamp implementation that are being made at this time. These primarily apply to requests submitted outside of PSI and are being made to enhance system performance.
+There are also some minor changes to the postage stamp implementation that are being made at this time. These primarily apply to requests submitted outside of PSI and are being made to improve
+parsing performance.
 
- * Currently if requests do not supply a survey or release the system for look ups by coordinate or skycell fall back to a list of "default data_groups". Over time this list has fallen woefullly out of date. This concept is removed. If no release parameters are included in the request SURVEY is set to 3PI.
+ * Currently if requests do not supply a survey or release the system for look ups by coordinate or skycell fall back to a list of "default data_groups". Over time this list has fallen woefullly out of date. (For an embarassingly long time PV3 was not included) This concept is removed. If no release parameters are included in the request SURVEY is set to 3PI. The data_group column in the request specification is still respected but it's use is really obsolete since SURVEY and IPP_RELEASE were added.
  * For skycell images if a tess_id is not supplied with the request, it defaults to the most appropriate tessellation based on the survey. For 3PI the tess_id is set to RINGS.V3. For the medium deep fields tess_id is set to the V3 version. For example MD01.V3.