Skip to content

Commit

Permalink
Apply suggestions from review
Browse files Browse the repository at this point in the history
Co-authored-by: Leanne Guy <[email protected]>
  • Loading branch information
ebellm and leannep authored Jan 10, 2025
1 parent b1affd4 commit 2591d00
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions alertproduction.tex
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,8 @@ \section{Alert Production in Commissioning and Early Operations}
Emphasize that AP is a continuous process


The \DPDD{} summarizes the pipelines which will be used during Prompt Processing to produce alerts as well as other prompt data products, including Solar System Processing.
Both Alert Production and Solar System Processing depend on the presence of template images.
The \DPDD{} summarizes the pipelines that will be used during Prompt Processing to produce alerts as well as other prompt data products, including Solar System Processing.
Both Alert Production and Solar System Processing depend on the existence of template images.
During steady-state operations, these templates will be constructed during the annual Data Releases and will be built from the best available subset of images taken.
To enable alert production to proceed during commissioning and early operations, it is necessary build templates incrementally as data become available, as recommended by the study described in \citeds{DMTN-107}.
Because we have a smaller set of input images to choose from and uncertain knowledge about future observations, incremental template generation necessarily must balance the trade off of earlier template availability against template quality and spatial completeness.
Expand All @@ -30,7 +30,7 @@ \section{Alert Production in Commissioning and Early Operations}
By the end of the commissioning period, coadd templates for use in difference imaging will only be available for $\approx$ 10\% of the sky.
Generating templates over a wide area is not an explicit goal of commissioning; however, where possible, if commissioning observations are agnostic to pointing and filter, we would endeavour to choose a pointing and filter that maximizes building templates to enable early science.

Rubin aims to scale up alert production during commissioning with the aim of beginning routine Alert Production as soon as is feasible following the Rubin First Look event.
Rubin aims to scale up alert production during commissioning with the aim of beginning routine Alert Production as soon as is feasible following the Rubin First Look event (\S~\ref{sec:timeline}).
\citeds{RTN-061} describes the criteria for sending the first Rubin alerts.
Once begun, Alert Production will then proceed continuously into the full LSST survey.
Alerts generated during commissioning may be produced with higher latency, and access to images and the PPDB may not be immeidately available.
Expand Down

0 comments on commit 2591d00

Please sign in to comment.