Changeset 39823
- Timestamp:
- Nov 24, 2016, 11:21:10 AM (10 years ago)
- Location:
- trunk/doc/release.2015/ps1.analysis
- Files:
-
- 2 edited
-
Makefile (modified) (1 diff)
-
stages.tex (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/release.2015/ps1.analysis/Makefile
r39822 r39823 3 3 help: 4 4 @echo "USAGE: make (target)" 5 @echo " targets: all analysis "5 @echo " targets: all analysis stages" 6 6 7 7 all: analysis.pdf stages.pdf 8 stages: stages.pdf 9 analysis: analysis.pdf 8 10 9 11 ANALYSIS = analysis.tex -
trunk/doc/release.2015/ps1.analysis/stages.tex
r39822 r39823 1 \documentclass[iop,floatfix]{emulateapj}1 % \documentclass[iop,floatfix]{emulateapj} 2 2 % \documentclass[iop,floatfix,onecolumn]{emulateapj} 3 \documentclass[12pt,preprint]{aastex} 3 4 % \pdfoutput=1 4 5 … … 106 107 The processing database is colloquially referred to as the `gpc1' 107 108 database, since a single instance of the database is used to track the 108 processing of images and data products related to the PS1 GPC1 109 camera. This same database engine also has instances for other 110 cameras which the IPP has processed, e.g., GPC2, the test cameras TC1, 111 TC3, theImaging Sky Probe (ISP), etc.109 processing of images and data products related to the PS1 GPC1 camera. 110 This same database engine also has instances for other cameras 111 processed by the IPP, e.g., GPC2, the test cameras TC1, TC3, the 112 Imaging Sky Probe (ISP), etc. 112 113 113 114 Within the processing database, the various processing stages are 114 115 represented as a set of tables. In general, there is a top level 115 116 table which defines the conceptual list of processing items either to 116 be done, in progress, or completed. An associated table will listthe117 specific details of elements which have been processed. For example, 118 one critical stage is the Chip processing stage, discussed below, in 119 which the individual chips from an exposure are detrended and sources 120 are detected. Within the gpc1 database, there is a top-level table 121 called `chipRun' in which each exposure has a single entry. 122 Associated with this table is the `chipProcessedImfile' table, which 123 contains one row for each of the (up to 60) chips associated with the124 exposure. The top-level tables, such as chipRun, are populated once 125 the system has decided that a specific item (e.g., an exposure) should126 be processed at that stage. Initially, the entry is given a state of 127 `run', denoting that the exposure is ready to be processed. The 128 low-level table entries, such as the chipProcessedImfile entries, are 129 only populated once the element (e.g., the chip) has been processed by 130 the analysis system. Once all elements for a given stage, e.g., chips 131 in this case, are completed, then the status of the top-level table 132 entry (chipRun) will be switched from 'run' to 'done'.117 be done, in progress, or completed. An associated table lists the 118 details of elements which have been processed. For example, one 119 critical stage is the Chip processing stage, discussed below, in which 120 the individual chips from an exposure are detrended and sources are 121 detected. Within the gpc1 database, there is a top-level table called 122 `chipRun' in which each exposure has a single entry. Associated with 123 this table is the `chipProcessedImfile' table, which contains one row 124 for each of the (up to 60) chips associated with the exposure. The 125 top-level tables, such as chipRun, are populated once the system has 126 decided that a specific item (e.g., an exposure) should be processed 127 at that stage. Initially, the entry is given a state of `run', 128 denoting that the exposure is ready to be processed. The low-level 129 table entries, such as the chipProcessedImfile entries, are only 130 populated once the element (e.g., the chip) has been processed by the 131 analysis system. Once all elements for a given stage, e.g., chips in 132 this case, are completed, then the status of the top-level table entry 133 (chipRun) are switched from `run' to `done'. 133 134 134 135 If the analysis of an element (e.g., chip) completed successfully, … … 137 138 recorded. An analysis which results in a fault is one in which the 138 139 failure is thought to be temporary. For example, if a computer had a 139 network glitch and was unable to write out some of the result files,140 network glitch and was unable to write out some of the output files, 140 141 this would be an ephemeral failure which was not a failing of the 141 142 data, but merely the processing system. On the other hand, if the … … 514 515 and objects}. 515 516 517 \section{Difference Images} 518 519 Two of the primary science drivers for the Pan-STARRS system are the 520 search hazardous asteroids and the search for Type Ia supernovae to 521 measure the history of the expansion of the universe. Both of these 522 projects require the discovery of faint, transient source in the 523 images. For the hazardous asteroids, and solar system studies in 524 general, the sources are transient because they are moving between 525 observations; supernovae are stationary but transient in brightness. 526 In both cases, the discovery of these sources can be enhanced by 527 subtracting a static reference image from the image taken at a certain 528 epoch. The quality of such a difference image can be enhanced by 529 convolving one or both of the images so that the PSFs in the two 530 images are matched. \note{discuss Alard-Lupton}. 531 532 In the Difference Image stage, the IPP generates diffferece images for 533 specified pairs of images. It is possible for the difference image to 534 be generated from a pair of warp images, from a warp and a stack of 535 some variety, or from a pair of stacks. During the PS1 survey, pairs 536 of exposures, call TTI pairs (see~\note{Survey Strategy}), were 537 obtained for each pointing within a $\approx$ 1 hour period in the 538 same filter, and to the extent possible with the same orientation and 539 boresite position. The standard PS1 nightly processing generated 540 difference images from the resulting warp pairs (`warp-warp diffs'). 541 542 The nightly stacks generated for the Medium Deep fields were combined 543 with a template reference stack image to generate `stack-stack diffs' 544 for these fields each night. 545 546 For the PV3 processing, the entire collection of warps for the $3\pi$ 547 survey were combined with the $3\pi$ stacks to generate `warp-stack 548 diffs'. 549 516 550 \begin{verbatim} 517 Outline:518 551 DVO Ingest 519 552 Calibration 520 553 IPP to PSPS 521 554 PSPS Load & Merge 522 Difference523 555 \end{verbatim} 524 556
Note:
See TracChangeset
for help on using the changeset viewer.
