Related documents discussing precursor datasets:
Draft SST Proposal for Test Datasets
| Data Set Id | Survey | Notes | Size | Website | Used in Tests | Suggested for tests | Use in LSST |
|---|---|---|---|---|---|---|---|
| HSC-PDR1 | HSC | HSC Public Data Release 1 | https://hsc-release.mtk.nao.ac.jp/doc/ | LVV-T23, LVV-T36, LVV-T37, LVV-T38, LVV-T68, LVV-T76 | LVV-T24?, LVV-T27, LVV-T49 | ||
| HSC-RC2 | HSC | Medium subset of PDR1 (two Wide-layer tract, one UltraDeep tract), selected to sample various features of the full PDR1 dataset; see DM-11345 - Getting issue details... STATUS . This is processed every two weeks using the weekly releases of the DM stack. | LVV-T28, LVV-T67, LVV-T71 | LVV-T58, LVV-T59, LVV-T69, LVV-T73, LVV-T74, LVV-T75, LVV-T77, LVV-T78, LVV-T79, LVV-T80, LVV-T82, LVV-T132 | Useful for verification, but for end-to-end science acceptance testing (validation) we would likely use the full PDR1. | ||
| ci_hsc | HSC | Small HSC dataset. Not a subset of PDR1; this is engineering data that went public even earlier. `ci_hsc` is run nightly. | 8.3G | LVV-T2 | LVV-T24 | Jenkins CI of ~90% of DRP pipeline steps (not large enough to run Jointcal or FGCM). Not useful for science validation. | |
| HSC-RC1 | HSC | Medium subset of PDR1 (two Wide-layer tract, one UltraDeep tract). Superseded by RC2. | LVV-T11, LVV-T12, LVV-T13, LVV-T14, LVV-T15, LVV-T16 | Won't be used for science validation. | |||
| WISE | WISE | LVV-T2, LVV-T3, LVV-T4, LVV-T5, LVV-T6 | Tables and catalogs for LSP testing. | ||||
| HiTS | HiTS (DECam) | http://astro.cmm.uchile.cl/HiTS/HiTS/ | LVV-T17, LVV-T18, LVV-T19, LVV-T20, LVV-T21, LVV-T22, LVV-T28, LVV-T35, LVV-T36, LVV-T37, LVV-T38, LVV-T67, LVV-T112, LVV-T113, LVV-T114, LVV-T160 | LVV-T49, LVV-T50, LVV-T51, LVV-T52, LVV-T53, LVV-T54, LVV-T55, LVV-T56, LVV-T57, LVV-T58 | Diff imaging and alert generation. From the HiTS data processing, we will also generate an alert stream. | ||
| DECam NEO | DECam NEO survey | PI L. Allen; 320 sq. degrees, 5 epochs/night in a single filter w/ 5 min. cadence. Repeated for 3 nights, 3 seasons of data. | LVV-T53, LVV-T57 | ||||
| DDOSSS | DECam KBO survey | PI D. Trilling; KBOs to VR~27 | https://www.noao.edu/noaoprop/abstract.mpl?2019A-0337 | MOPS | |||
| DES-SN | DECam DES-SN | Difference imaging, alert production. Benefit over HiTS is multiple filters. | |||||
| DECam Bulge Survey | Crowded fields. | ||||||
| Opsim | LSST | LSST Simulations of various survey strategies | http://astro-lsst-01.astro.washington.edu:8080/ | ||||
| DESC-DC2 | LSST | DESC DC2 | |||||
| Twinkles | LSST | DESC | |||||
| Stripe82 | SDSS | SDSS Stripe 82 catalog processed with LSST Stack | LVV-T7, LVV-T8, LVV-T9 | Gregory Dubois-Felsmann Stripe82 just happened to be convenient at the time of these tests, but doesn't seem essential for them. Is this correct? (i.e., that HSC, WISE, or other datasets could achieve these tests?) | |||
| L1Test | LSST | L1 Test Stand DAQ; not so much a "data set" as a "data source" | LVV-T29, LVV-T30, LVV-T31, LVV-T32, LVV-T33, LVV-T34, LVV-T45 | Verifying LSST headers, formats, and well-formed images. Does LVV-T45 : | |||
| photo-z | COSMOS, GAMA (others?) | High-quality spectroscopic and photometric redshift catalogs in the HSC-PDR footprint. | LVV-T68 | Training of photometric redshifts, but not needed for science validation. | |||
What will be used to create a Prompt Products database that enables tests of MOPS?
Are there any larger sky-area data sets that should be included (e.g., LVV-T76 calls for one)?
Gaia (and possibly a catalog of QSOs) is used in LVV-T80, but only as a catalog for selecting objects in HSC data. The QSO catalog is also re-used in LVV-T160.
LVV-T92 - T95 concern "Special Programs." Are HSC Deep/Ultra-Deep fields appropriate for this? Or HiTS?
LVV-T112 - T114 refer to a "Simulated alert stream" – add this above?
Simulated EFD? (e.g., LVV-T153) – could also wait until single-day operations rehearsal.
A few tests suggest that inserting artificial sources (e.g., variable stars, QSOs, etc.) would be useful. This is more a requirement to write the tools than it is a data set.