Changeset 40559 for trunk/doc/release.2015/ps1.detrend/detrend.tex
- Timestamp:
- Nov 18, 2018, 10:38:23 AM (8 years ago)
- File:
-
- 1 edited
-
trunk/doc/release.2015/ps1.detrend/detrend.tex (modified) (6 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/release.2015/ps1.detrend/detrend.tex
r40441 r40559 188 188 view. 189 189 190 \note{need to define PV3 (and PV0-2) here. see datasystem.tx} 191 190 192 %The Processing Version 3 (PV3) reduction represents the third full 191 193 DR1 contains the results of the third full reduction of the Pan-STARRS … … 254 256 section \ref{sec:discussion}. 255 257 258 \note{describe gpc1 camera layout before the following paragraph} 259 256 260 Image products presented in figures have been mosaicked to arrange 257 261 pixels as follows. Single cell images are arranged such that pixel … … 273 277 mosaic. 274 278 275 \textit{Note: These papers are being placed on the arXiv.org to276 provide crucial support information at the time of the public277 release of Data Release 1 (DR1). We expect the arXiv versions to be278 updated prior to submission to the Astrophysical Journal in January279 2017. Feedback and suggestions for additional information from early280 users of the data products are welcome during the submission and281 refereeing process.}279 %%\textit{Note: These papers are being placed on the arXiv.org to 280 %% provide crucial support information at the time of the public 281 %% release of Data Release 1 (DR1). We expect the arXiv versions to be 282 %% updated prior to submission to the Astrophysical Journal in January 283 %% 2017. Feedback and suggestions for additional information from early 284 %% users of the data products are welcome during the submission and 285 %% refereeing process.} 282 286 283 287 … … 298 302 These corrections assume that the detector response is linear across 299 303 the full range of values. This assumption is not universally true for 300 GPC1, and an additional set of detrending steps are required to remove 301 these artifacts. The first of these is the \IPPprog{burntool} 302 correction, which removes the flux trails left by the incomplete 303 transfer of charge along the readout columns. These trails are 304 generally only evident for the brightest stars, as only pixels that 305 are at or beyond the saturation point of the detector leave residual 306 charge. More widespread is the non-linearity at the faint end of the 307 pixel range. Some readout cells and some readout cell edge pixels 308 experience a sag relative to linear at low illumination, such that 309 faint pixels appear fainter than expected. The correction to this 310 requires amplifying the pixel values in these regions to match the 311 expected model. 304 GPC1, and an additional set of detrending steps are required as a 305 result. The first of these is the \IPPprog{burntool} correction, 306 which removes the flux trails left by the incomplete transfer of 307 charge along the readout columns. These trails are generally only 308 evident for the brightest stars, as only pixels that are at or beyond 309 the saturation point of the detector leave residual charge. More 310 widespread is the non-linearity at the faint end of the pixel range. 311 Some readout cells and some readout cell edge pixels experience a sag 312 relative to linear at low illumination, such that faint pixels appear 313 fainter than expected. The correction to this requires amplifying the 314 pixel values in these regions to match the expected model. 312 315 313 316 Large regions of some OTA cells experience significant charge transfer … … 496 499 with the noise generally higher away from the read out amplifier 497 500 (higher cell x pixel positions). This is likely an effect of the 498 row-by-row bias issue discussed below. As a result of this 499 increased noise, more sources are detected in the higher noise regions 500 when the read noise is assumed constant across the readout. 501 row-by-row bias issue discussed below (Section~\ref{sec:pattern.row}). 502 As a result of this increased noise, more sources are detected in the 503 higher noise regions when the read noise is assumed constant across 504 the readout. 501 505 502 506 To mitigate this noise gradient, we constructed an initial set of … … 1274 1278 1275 1279 \subsubsection{Pattern Row} 1280 \label{sec:pattern.row} 1276 1281 %% Statistics so I have them written down somewhere 1277 1282 %% chipProcessedImfile.bg/bg_stdev by filter for XY33 (a good chip)
Note:
See TracChangeset
for help on using the changeset viewer.
