| | 1 | {{{ |
| | 2 | The PS1 software team is finally applying resources to produce a good interactive |
| | 3 | inteface to the IPP postage stamp server. This will be included as part of the PS1 SCI (term) |
| | 4 | interface along side PSPS. |
| | 5 | |
| | 6 | The original web interface prototype has many significant limitations. The most important is that |
| | 7 | it is quite IPP centric. The second is that the user experience is not friendly. Finally, it |
| | 8 | supports neither the the complete feature set of the existing postage stamp server interface or various other |
| | 9 | features that users require. |
| | 10 | |
| | 11 | The purpose of this note is to outline a more user oriented interface and certain enhancements |
| | 12 | to the IPP system that are required to implement them. |
| | 13 | |
| | 14 | There are three major functions of the current postage stamp request interface |
| | 15 | |
| | 16 | 1. Select the images of interest |
| | 17 | 2. Identify the region of interest - the set of pixels to be extracted |
| | 18 | 3. Select the output data products to be returned. |
| | 19 | |
| | 20 | Some of these functions are really "database operations" yet the postage stamp request |
| | 21 | specification does not provide very complete set of selectors. |
| | 22 | |
| | 23 | In this document we propose splitting many of those functions off. |
| | 24 | |
| | 25 | In the end it changes from a "fire and hope" system, to a more controlled user managed system. |
| | 26 | |
| | 27 | Review of the Postage Stamp Interface |
| | 28 | ------------------------------------- |
| | 29 | The postage stamp server interface is described in the interface control document (LINK). |
| | 30 | |
| | 31 | Requests are submitted to the server as fits tables. Each row in the table specifies one set |
| | 32 | of coordinates and parameters to select the input images and output data products. When processed |
| | 33 | by the server each row generates zero or more postage stamp jobs. When all of the jobs |
| | 34 | queued for a given request the results are bundled into a fileset on the IPP data store. |
| | 35 | A fits file containing a table is also created. Each row in this results file lists the files |
| | 36 | included in the output and various parameters of the source images. |
| | 37 | |
| | 38 | Images of Interest - Stage |
| | 39 | -------------------------- |
| | 40 | The postage stamp server interface is based on the various stages of the IPP. Images are |
| | 41 | selected from one of the stages of the IPP pipeline |
| | 42 | |
| | 43 | raw |
| | 44 | chip |
| | 45 | warp |
| | 46 | stack |
| | 47 | diff |
| | 48 | |
| | 49 | Raw stage |
| | 50 | --------- |
| | 51 | The images acquired by the GPC1 camera. 60 fits files per exposure on for each OTA (chip), |
| | 52 | 64 or more extensions per file 1 for each cell. Raw images are of limited use to end users. |
| | 53 | |
| | 54 | Chip stage |
| | 55 | ---------- |
| | 56 | Outputs from the IPP chip and camera stage. At the chip stage images have been detrended. These |
| | 57 | operations include dark, flatfield, burntool, and various other chip (and cell) specific corrections. |
| | 58 | These images have had a fit to the sky background subtracted. Photometry is performed at this |
| | 59 | stage. At the camera stage the chip stage outputs for the 60 OTAs are analyzed together to arrive |
| | 60 | at the astrometric solution and the initial zero point is measured. |
| | 61 | |
| | 62 | The postage stamp server uses the camera stage astrometric solution to select the pixels |
| | 63 | and includes the solution as the WCS in the headers of the output files. The zero point measured |
| | 64 | at the camera stage is not currently included. That must be fixed. |
| | 65 | |
| | 66 | Warp stage |
| | 67 | ---------- |
| | 68 | After the camera stage the images are transformed (warped) to a given skycell tessellation. |
| | 69 | The resulting images have right ascension and declination as the X and Y axes. Each skycell gets |
| | 70 | contributions from chip stage images from one or more of the OTAs. The photometry outputs from |
| | 71 | the various input chips are combined. Photometry is *not* repeated at the warp stage. The sources |
| | 72 | files contain the sources detected at the chip stage with coordinates transformed to skycell |
| | 73 | coordinates. |
| | 74 | |
| | 75 | Stack Stage |
| | 76 | ----------- |
| | 77 | At the stack stage multiple warps are combined together. More details on this process will be |
| | 78 | discussed below in the section on data products. |
| | 79 | |
| | 80 | Diff Stage |
| | 81 | ---------- |
| | 82 | At the Diff stage various combinations of images are subtracted from each other to find differences. |
| | 83 | These are used to find transient events and moving objects. The major difference modes are |
| | 84 | Warp-Warp Two individual frames are compared |
| | 85 | Warp-Stack A single frame is compared to a template stack image |
| | 86 | Stack-Stack Stack created from a single night's exposures are compared to a template stack |
| | 87 | |
| | 88 | There are some other stages of the IPP pipline which are currently ignored by the current postage stamp |
| | 89 | interface. Many of these are critical to a complete understanding of the data |
| | 90 | |
| | 91 | DVO - Associates source detections from single frames and stacks into objects. Zero point and |
| | 92 | astrometric measurements are refined. The results are exported to PSPS but are not fed |
| | 93 | back into the images returned by the postage stamp server. |
| | 94 | |
| | 95 | Static Sky and Sky Calibration - Performs photometry and astrometric correction to stacked images |
| | 96 | including extended source measurments. These results are imported into PSPS but for more rapid |
| | 97 | turn around and easy association with images these results should be avialable through the pstamp server. |
| | 98 | |
| | 99 | Chip Background Stage - Certain images undero further processing to remove the background correction |
| | 100 | that was applied at the chip stage. (Currently only used for M31.) It has been recommended to add a |
| | 101 | feature to the postage stamp server to optionally perform this operation on an arbitrary image. |
| | 102 | Work has been done to implement this but haa not yet been deployed. |
| | 103 | |
| | 104 | Warp Background Stage chip background outputs warped to sky coordinates. |
| | 105 | |
| | 106 | Background restored stacks - For analysis of large extended objects the background correction is |
| | 107 | problematic. It is a requirement to the IPP to make avaliable through the postage stamp server |
| | 108 | stack images with the background restored. A project has been started to implement the |
| | 109 | background restoration. |
| | 110 | |
| | 111 | Suggested New user interface |
| | 112 | ---------------------------- |
| | 113 | The selection by stage makes perfect sense for the implementation but requires some knowlege of the |
| | 114 | workings of the IPP. The IPP terminolgy is somewhat different than that used by PSPS and many users |
| | 115 | are not familar with it. We assert here that they shouldn't need to be. |
| | 116 | |
| | 117 | The inteface should be presented as a series of choices which more reflect the nature of the |
| | 118 | underlying data than the architecture of the IPP |
| | 119 | |
| | 120 | The image type choices should be presented as follows |
| | 121 | |
| | 122 | 1. Single Frame Images |
| | 123 | chip coordinate pixels |
| | 124 | warped coordinate pixels |
| | 125 | |
| | 126 | 2. Stacked Images |
| | 127 | |
| | 128 | 3. Difference Images |
| | 129 | |
| | 130 | 4. Raw images |
| | 131 | |
| | 132 | The UI should present options 1 and 2 prominently and make 3 and especially 4 advanced options. |
| | 133 | |
| | 134 | |
| | 135 | Selection of source images |
| | 136 | -------------------------- |
| | 137 | Once the stage is identified, the actual input images need to be selected. The server supports several |
| | 138 | image selection methods. Note that currently postage stamps are extracted from a *single* IPP |
| | 139 | image product. No combination between chips or skycells is performed. |
| | 140 | |
| | 141 | bycoord Images are selected based on supplied RA and DEC |
| | 142 | byexp Single frame images selected by name (IPP rawExp.exp_name PSPS FrameMeta.name) |
| | 143 | byid Specific images are selected by IPP database ID (exp_id, chip_id, warp_id, stack_id, diff_id) |
| | 144 | byskycell warp, stack, and diff images selected based on tessellation id (tess_id) and skycell_id |
| | 145 | bydiff specialized method used by MOPS to select images from a particular difference detection |
| | 146 | |
| | 147 | Image of Interest filtering |
| | 148 | --------------------------- |
| | 149 | A number of parameters can be supplied with the request to narrow down the set of target images. Two |
| | 150 | obvious ones are filter and observation date. The IPP data_group can be used to narrow down the |
| | 151 | data set. In practice this is only useful with advice from the IPP team or access to a copy of the |
| | 152 | IPP's gpc1 mysql data base. |
| | 153 | |
| | 154 | Problems with this interface for end users |
| | 155 | ------------------------------------------ |
| | 156 | Other than bycoord these methods are not friendly to end users. Unless the user has |
| | 157 | access to a copy of the gpc1 database or software to find out which skycell contains |
| | 158 | a given point int the sky it is difficult to narrow down images to specific |
| | 159 | data sets. |
| | 160 | |
| | 161 | Now that PSPS is being loaded with more PSPS data this problem is relieved somewhat. However |
| | 162 | given inevitable the time lag between the exposures and frames information that PSPS does not currently |
| | 163 | have is needed to select recent data efficeintly. |
| | 164 | |
| | 165 | Given the vast data set of pan starrs selection by coordinates has it's problem. Asking for all chip |
| | 166 | images for a spot in one of the medium deep fields is easy to do and probably not what a user |
| | 167 | really wants. |
| | 168 | |
| | 169 | Also frames have been procssed multiple times. The IPP has no notion of what the right set of |
| | 170 | runs should be "released" to end users. A solution to this problem has been proposed. In this |
| | 171 | document we will assume that those features will be available. |
| | 172 | |
| | 173 | Suggested Features for the New UI |
| | 174 | --------------------------------- |
| | 175 | It is desirable to be able to preview what the results of a given set of requests will include. |
| | 176 | In the current interface this is problematic because this information is obtained by parsing |
| | 177 | the request file which is an extremely inefficent operation. |
| | 178 | |
| | 179 | Since the new UI is inside a "database environment" we have an opportunity to improve this |
| | 180 | significantly. |
| | 181 | |
| | 182 | While finding all of the images for a given stage that correspond to a set of coordinates is |
| | 183 | somewhat expensive finding the individual frames is more straightforward. |
| | 184 | |
| | 185 | We suggest moving the selection of frames for processing from the postage stamp server to |
| | 186 | the web interface. The Web interface will thus only do byexp or byid requests. |
| | 187 | |
| | 188 | |
| | 189 | Choices in the UI - Single Frame Images |
| | 190 | --------------------------------------- |
| | 191 | |
| | 192 | Coordinates |
| | 193 | Sky coordinates RA DEC decimal degrees and sexagesimal standard formats |
| | 194 | pixel coordinates (advanced) |
| | 195 | |
| | 196 | Note that it is desirable to accept a list of coordinates and process them together. Users |
| | 197 | should be able to upload lists with certain parameters to the UI for example |
| | 198 | RA DEC FILTER dateobs_min dateobs_max. |
| | 199 | |
| | 200 | The user should also be able to provide a list of object or detection ids obtained from a query. |
| | 201 | |
| | 202 | Choices in the UI - All image types |
| | 203 | ----------------------------------- |
| | 204 | |
| | 205 | Stamp Size |
| | 206 | pixels |
| | 207 | arcseconds |
| | 208 | entire image |
| | 209 | |
| | 210 | Image Selection |
| | 211 | by coordinates |
| | 212 | by frame id |
| | 213 | by skycell id (advanced) |
| | 214 | |
| | 215 | Data Release |
| | 216 | Best (default) |
| | 217 | PSPS data / release version |
| | 218 | Original Nightly Processing (not sure if we need this but it's easy) |
| | 219 | |
| | 220 | This is a new concept which requires some work on the IPP side. It should probably eventually |
| | 221 | default to the version in PSPS database for a given survey but at the current time this is too |
| | 222 | restrictive as it hides much of the data. |
| | 223 | |
| | 224 | If we are not selecting by frame id a few more selectors should be made available |
| | 225 | |
| | 226 | Survey |
| | 227 | 3PI |
| | 228 | MD (includes M31, CNP, and STS) |
| | 229 | SAS |
| | 230 | SS |
| | 231 | |
| | 232 | To use this information requires a new interface with the postage stamp server. Note the individual |
| | 233 | frames can be identified by rawExp.obs_mode.... but this is buggy for old data. Perhaps something |
| | 234 | should be added to the new ippRelease table for the given frame. |
| | 235 | |
| | 236 | Choices in the UI - Single Frame Images |
| | 237 | --------------------------------------- |
| | 238 | Filter |
| | 239 | hints should perhaps be provided. For example w shouldn't be a choice in the 3pi or MD surveys. |
| | 240 | STS is only i. |
| | 241 | |
| | 242 | Observation Date |
| | 243 | min Default to the beginning of the mission to avoid buggy data. User can change to accept |
| | 244 | earlier data if desired |
| | 245 | max default no limit |
| | 246 | |
| | 247 | |
| | 248 | Data Group This exists in the current interface and should be included but not displayed prominently. |
| | 249 | |
| | 250 | Preview Function |
| | 251 | ---------------- |
| | 252 | Once the user has selected the parameters he can command the system to perform the image lookup for |
| | 253 | preview and selection. |
| | 254 | |
| | 255 | Ideally this would be a PSPS operation but since we want to make all PS1 data available we propose |
| | 256 | using the gpc1 database (or a replicated copy or subset). |
| | 257 | |
| | 258 | The query would use the selection parameters described above to query the new table ipp release table. |
| | 259 | This table will have entries for each exposure that indicate which images in the IPP have been |
| | 260 | "released" by the IPP. Paremeters available |
| | 261 | exp_id |
| | 262 | chip_id |
| | 263 | warp_id |
| | 264 | diff_id |
| | 265 | survey_id |
| | 266 | release (or data version) |
| | 267 | |
| | 268 | Other parameters (ra, dec, filter, dateobs) will be included by joining to the rawExp table. |
| | 269 | |
| | 270 | When the query returns the relevant data will be presented to the users in a format that allows |
| | 271 | them to select the target frames for the postage stamp requests. |
| | 272 | |
| | 273 | frameID survey filter "released version" comment |
| | 274 | |
| | 275 | By released version I mean something that tells whether the data is from one of the grand reprocessed data |
| | 276 | sets or is the original nightly processing. |
| | 277 | |
| | 278 | If a list of coordinates was provided the presentation of the results to the user in friendly |
| | 279 | way may be tricky. |
| | 280 | |
| | 281 | |
| | 282 | Image Selection from results of PSPS queries |
| | 283 | -------------------------------------------- |
| | 284 | One obvious use case is to request postage stamps from the objects or detections in |
| | 285 | results of a specific PSPS query. |
| | 286 | |
| | 287 | Object coordinates could be used to create a bycoord request to the server. If individual detections are |
| | 288 | available then the frameID may be obtained and byexp requests could be used. A user might also |
| | 289 | be interested in looking at stamps from frames where the object was not detected so that should |
| | 290 | be supported as well. |
| | 291 | |
| | 292 | Stacked images |
| | 293 | -------------- |
| | 294 | The IPP will need a table to manage releases for Stacked images as well. The fundamental unit in this |
| | 295 | case is the Skycell. |
| | 296 | stack_id |
| | 297 | skycell_id |
| | 298 | survey_id |
| | 299 | release |
| | 300 | |
| | 301 | Other parameters, ra, dec, filter, tess_id will be available through join to the tables stackRun |
| | 302 | and skycell |
| | 303 | |
| | 304 | QUESTION: One feature that might be interesting is to find the stacks that a particular frame is included |
| | 305 | in. Currently this information is not availalble from the PSPS or postage stamp server. It can be |
| | 306 | derived from the IPP database. Is this useful? |
| | 307 | |
| | 308 | |
| | 309 | Data Products Available Current Interface |
| | 310 | ----------------------------------------- |
| | 311 | Image |
| | 312 | Mask |
| | 313 | Variance |
| | 314 | Sources (CMF) |
| | 315 | |
| | 316 | Chip stage |
| | 317 | psf |
| | 318 | model |
| | 319 | |
| | 320 | Stack |
| | 321 | Unconvolved images |
| | 322 | |
| | 323 | Processing |
| | 324 | ---------- |
| | 325 | |
| | 326 | |
| | 327 | |
| | 328 | |
| | 329 | }}} |