LSST DM Developer Guide

Introduction

Development Resources

The following build resources are essential to LSST software development: 

• SCons is the build system. See the SCons User Guide to get started. 
• EUPS is the package management system. 
• Git is the version control software used for the LSST Stack; the various packages are stored as LSST git repositories. 
  • See the Pro Git book by S. Chacon for a good introduction to git. 
• Swig is a software development tool that generates interfaces from C or C++ to other languages; for LSST, the target language is python. 
• LSST-data mailing list subscription and management

For development or testing activity on NCSA machines, see:

• establishing Public/Private Keys for ssh access to NCSA development machines
• the list of available development servers and their intended use
• system announcements of the status and planned down-time
• Real-time system status (requires login)
• Report system issues to lsst-admin@ncsa.uiuc.edu 

• Do the following to initialize for LSST development (or include in the shell .rc file):

  > source ~lsstsw/eups/bin/setups.sh   # bash users
  > setup anaconda
  > setup git
  > setup lsst

DM Standards and Processes

The following appointed groups oversee various aspects of DM Software requirements, design, or implementation. 

Technical Control Team (TCT)

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: 

Membership:

The TCT is chaired by the DM System QA and Test Lead. Other members include the DM System Scientist and Lead Institution Project Scientists. 

Meetings: 

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.

Responsibilities:

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. 

System Architecture Team (SAT)

DM Reviews

Various kinds of review of the DM software are conducted during development.