| 11 | | This note is intended to be a starting point for fleshing out the requirements and plan for implentation of this work. |
| | 11 | This note is intended to be a starting point for fleshing out the requirements and plan for implentation of this work. First we discuss the |
| | 12 | current system for delivering images to the consortium. Next we talk about what the requirements for an image server for public |
| | 13 | release might be. Then we discuss what data must be delivered by the IPP to meet these requirements. Finally we have some thoughts |
| | 14 | on what IPP software might be adapted to meet the requirements and what might need to be developed. |
| | 15 | |
| | 16 | The contents here in the first draft come from my understanding of what is needed and what is planned. I'm sure others have thought |
| | 17 | through many issues in detail. |
| | 64 | |
| | 65 | == Data Requirements for Image Server for PS1 Public Release == |
| | 66 | |
| | 67 | * Postage stamp (cut outs) subsets and complete single frame warp skycell images |
| | 68 | * These are the data products from IPP warp processing (full state) which are being preserved for PV3. |
| | 69 | * Are results from the entire run needed, psfs cmfs etc. I suspect no. |
| | 70 | * Postage stamps and complete stack skycell images |
| | 71 | * These are the data products from the IPP stack processing |
| | 72 | * To provide photometry information for headers and detections equivalent to what the IPP server odes today the skycal cmfs for each skycell are needed. |
| | 73 | * Stack Summary images for a given region of the sky |
| | 74 | |
| | 75 | Note: The IPP postage stamp server delivers images based on a single IPP image. That is we do not mosaic images together although is is |
| | 76 | an often requested feature. |
| | 77 | |
| | 78 | === Data products that will not be included in the public release === |
| | 79 | * detrended chip stage images |
| | 80 | * difference images |
| | 81 | |
| | 82 | |
