LSST DM Developer Guide

This guide has yet to be written, although snippets of potentially useful content appear below.

This Guide describes the processes and capabilities available to LSST DM staff developers. The content includes the available machines hardware, the development procedures for planned changes (the version control system, tickets, reviews, merging, etc.), how continuous integration operates, coding and documentation standards, and so forth.

Document Downloads

You may capture the content in PDF from the pull-down menu: Tools→Export to PDF, though the rendering is often less than satisfactory.

In this guide

Core Development Resources

Software Development Resources

The following build resources are essential to LSST software development:

The master repositories for LSST project and contributed software are hosted at: https://dev.lsstcorp.org/cgit/
- The repositories are managed with gitolite.
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 chapter on LSST Code Repositories for background on using git in the software development workflow.
- 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.

See Development on NCSA Machines to set up your development environment there.

Standards and Policies

The Standards and Policies provide the framework in which DM software is designed, implemented, tested and documented. These documents have been reviewed and accepted by the DM TCT as developer best practices.