Skip to content

Commit

Permalink
Update solar-system-processing-pipeline.rst
Browse files Browse the repository at this point in the history
  • Loading branch information
sgreenstreet committed Dec 11, 2024
1 parent 3900260 commit 20a5294
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion data-products-dp0-3/solar-system-processing-pipeline.rst
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ During the day before the coming night’s observing:
Solar System Data Release Processing
====================================

In addition to the prompt processing that will be performed on a daily basis, re-processing of the data will be performed annually to produce the Data Release Data Products; an exception to the annual re-processing timeline will be the first two Data Releases that will be created six months apart. As described above, the Daily (Prompt) Data Products for Solar System objects will include single visit images, difference images, catalogs of sources detected in difference images (``DIASources``) and detected objects that are associated with Solar System objects (``SSObjects``), which will include all data collected by the survey to date and will be entered into the Prompt Products database and made available in near real time. One expection to the use of all survey data to date for the near real time data releases, however, is the Alert Production pipeline that limits the `DIASource` history for all variability parameters within the alert packets to a 12-month period.
In addition to the prompt processing that will be performed on a daily basis, re-processing of the data will be performed annually to produce the Data Release Data Products; an exception to the annual re-processing timeline will be the first two Data Releases that will be created six months apart. As described above, the Daily (Prompt) Data Products for Solar System objects will include single visit images, difference images, catalogs of sources detected in difference images (``DIASources``) and detected objects that are associated with Solar System objects (``SSObjects``), which will include all data collected by the survey to date and will be entered into the Prompt Products database and made available in near real time. One expection to the use of all survey data to date for the near real time data releases, however, is the Alert Production pipeline that limits the ``DIASource`` history for all variability parameters within the alert packets to a 12-month period.

The roughly annual Data Release Data Products for Solar System objects will include high-fidelity re-processing of all catalogs derived from re-reductions of all survey data using improved calibrations and a single, well-characterized, software release. In addition, the Data Release Data Products will include a LSST Catalog of Solar System Objects that will be suitable for population studies of objects detected by LSST with orbits estimated using only LSST data; this catalog will not rely on association of known objects using MPC orbit predictions. In contrast to the Prompt Products database, which is updated continuously during observing, the Data Release database is static and will not change after release. In general, the Data Release Data Products are best for purposes such as large-scale Solar System population studies and model debiasing, while the Daily (Prompt) Data Products are most useful for efforts such as follow-up and characterization of Solar System objects as they are detected by the survey.

Expand Down

0 comments on commit 20a5294

Please sign in to comment.