| | 1 | |
| | 2 | == IPP Data Release Management == |
| | 3 | |
| | 4 | The IPP does not have a good way of keeping track of what data is intended for or has been released |
| | 5 | to the PS1SC community. Up until now this has not been a big problem, but several issues have recently |
| | 6 | led us to believe that some new functionality is necessary to make it easy for users to get access to |
| | 7 | IPP data products that meet their expectations. |
| | 8 | |
| | 9 | The specific goals are |
| | 10 | |
| | 11 | * To record which versions of the data products have been (and should be) "released" to the community through the various distribution channels. |
| | 12 | * To allow users to get the "right" versions of the data in their requests to the postage stamp server |
| | 13 | * To record within the IPP domain the results of various re-calibrations and re-processings that may occur |
| | 14 | |
| | 15 | These goals will be met with some enhancements to the IPP data base schema and through some lightweight changes |
| | 16 | to the procedures for processing and releasing data. |
| | 17 | |
| | 18 | |
| | 19 | == IPP Release Channels == |
| | 20 | Data is released through several channels. |
| | 21 | |
| | 22 | * The IPP Distribution data store |
| | 23 | * The Published Science Products Subsystem (PSPS) |
| | 24 | * The IPP Postage Stamp Server |
| | 25 | * DVO catalogs |
| | 26 | |
| | 27 | 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 |
| | 28 | project. |
| | 29 | |
| | 30 | == IPP Data Products == |
| | 31 | There are three categories of data products to be covered by the IPP release mechanism |
| | 32 | * Single Frame Data Products |
| | 33 | * Stacked Image Data Products |
| | 34 | * Difference Image Data Products |
| | 35 | |
| | 36 | === Single Frame Results === |
| | 37 | Single exposures move through the IPP pipeline in a number of stages. The data products of interest to end users |
| | 38 | are the results of the chip and camera stage (focal plane coordinates) and the warp stage. The end results are |
| | 39 | two sets of images and catalogs of detected sources. The catalogs are then imported into the DVO system and |
| | 40 | eventually into a PSPS data base. Exposures are also queued for difference processing which will be discussed |
| | 41 | separately. |
| | 42 | |
| | 43 | ==== Nightly Science ==== |
| | 44 | On the night that the exposures are acquired they are run through the IPP "Nightly Science" processing. |
| | 45 | The resulting catalogs are posted to file sets on the IPP Data Store web server. For certain exposures |
| | 46 | warped images are placed on the data store as well. This is the first "release" for a given exposure. |
| | 47 | |
| | 48 | The catalog files (smf and cmf) currently remain on the data store indefinitely. For various |
| | 49 | reasons this needs to be changed. A new system for on demand access to these files is under development. |
| | 50 | The image files posted to the data store are removed after some time to conserve space. |
| | 51 | |
| | 52 | |
| | 53 | |
| | 54 | |