Welcome to the online community thinking about LSST survey strategy ("cadence"), with quantifications via the Metric Analysis Framework.
We are writing a white paper on this topic, primarily composed of a set of individual science cases that are either very important, and somehow stress the observing strategy, and describing how we expect them to be sensitive to LSST observing strategy. MAF metric calculations are then being designed and implemented: these form the quantitative backbone of the document. You may have heard of the coming "Cadence Wars" - this white paper represents the "Cadence Diplomacy" that will allow us, as a community, to avoid, or at least manage, that conflict. We welcome contributions from all around the LSST Science community.
-
Read the current draft of the white paper (automatically generated PDF, rebuilt every time the
master
branch is updated)
- Guidelines for how to get involved are in the introduction of the white paper itself, in Section 1.4
- For help getting started with git and GitHub, see this handy guide.
- Shortened URL for this repository (for passing around): http://ls.st/o5k
- Community-contributed MAF metric code at the
sims_maf_contrib
repository
August 19-21, 2015.
November 19-20, 2015.
This effort is being coordinated by Zeljko Ivezic and Beth Willman, while Phil Marshall is the white paper's editor-in-chief. Any of them can propagate your privately-communicated concerns into a redacted issue on this repository. Contributions are very welcome from all round the LSST science collaborations, and beyond. Perhaps we are missing a science case? Or an idea for how to perturb the observing strategy? We'd like to hear from you! Please send all your feedback to this repo's issues.
All white paper content is Copyright 2015, 2016, 2017 The Authors. If you make use of the ideas and results in the white paper in your research, please cite it as "(LSST Science Collaborations in preparation)", and provide the URL of this repository: https://github.com/LSSTScienceCollaborations/ObservingStrategy. Thanks!