This guide has yet to be written, although snippets of potentially useful content appear below. |
The following build resources are essential to LSST software development:
For development or testing activity on NCSA machines, see:
> source ~lsstsw/eups/bin/setups.sh # bash users > setup anaconda > setup git > setup lsst |
/lsst7/stripe82/dr7/runs
. The following appointed groups oversee various aspects of DM Software requirements, design, or implementation.
The DM Technical Control Team has responsibility for issues similar to those of a Configuration Control Board. The TCT reviews and approves changes to all baselines in the LSST Data Management System, including proposed changes to the DM functional requirements' (FRS), reference design, or Data Challenge design baselines, the tools to be used (including third-party packages), and standards and policies. Specifically:
The TCT is chaired by the DM System QA and Test Lead. Other members include the DM System Scientist and Lead Institution Project Scientists.
The TCT meets at least monthly, and more often during periods prior to major reviews and data challenge integrations, or when developers request expedited approval to change the baseline.
The TCT determines when specification and deliverables are of sufficient maturity and quality to be baselined (placed under configuration controlled status) or released. The TCT reviews and approves proposed changes to baselined items.
Various kinds of review of the DM software are conducted during development.