Changes between Version 16 and Version 17 of pstamp_2015-04-changes

Timestamp:

Apr 17, 2015, 10:40:21 AM (11 years ago)

Author:

bills

Comment:

--

pstamp_2015-04-changes

@@ -1 +1 @@
 = Changes to the postage stamp server interface and implementation to be made on 2015-April-21 =
 
-While the collection of data for the PS1 Science Consortium has ended PS1 continues to take data. For now, this new data is only available for members of the new Pan-Starrs Consortium PSNC.
+While the collection of data for the PS1 Science Consortium has ended PS1 continues to take data. For now, this new data is only available to members of the new Pan-Starrs Consortium PSNC.
 
 Some changes to the operation of the postage stamp system are required to support the new consortium. This page describes the changes. For users who use the Pan-Starrs Science Interface (PSI) 
@@ -19 +19 @@
 higher access level. 
 
-A user with level 1 access will be limited to  single frame observations made prior to 2015-03-01. Access to stacks will be handled on a release by release data using the release tables in the IPP databases.
+A user with level 1 access will be limited to  single frame observations made prior to 2015-03-01. Access to stacks will be handled on a release by release basis using the release tables in the IPP databases.
 
 [wiki:pstamp_version_2_conversion] provides some hints for converting software that creates version 1 request files to version 2.
 
-Requests from version 1 files received between April 21 and May 5 will only be provided with level 1 access. After May 5 version 1 files will be rejected.
+== Requests from version 1 files received between April 21 and May 5 will only be provided with level 1 access. After May 5 version 1 files will be rejected. ==
 
 == The postage stamp images and other results may be directed to a different data store location based on the email address ==
@@ -34 +34 @@
 If the system can't figure out a specific product for the user the results will continue to go to pstampresults.
 
-The data store links that PSI uses will automatically resolve to the new locations. Users who summit their own files will need to look in the new locations.
+The data store links that PSI presents will automatically resolve to the new locations. Users who summit their own files will need to learn where to look.
 
 If a PS1SC institution would like to have their own data store product let Bill Sweeney know.
@@ -42 +42 @@
 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. (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 if supplied, but this parameter has been 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.
+ * 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 woefully out of date. (For example, for an embarassingly long time PV3 was not included in the list). This concept is removed. If no release parameters are included in the request SURVEY will be set to 3PI. The DATA_GROUP  column in the request specification is still respected if supplied.
+This parameter has been somewhat 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.