DEPRECATED

This space is obsolete and unmaintained. The entire content of the DM Developer Guide is now maintained at https://developer.lsst.io .

LSST DM Developer Guide

Created by Unknown User (shaw), last modified on Aug 20, 2014

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Introduction

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

Core Development Resources

Getting Started

Begin by getting an account on lsstcorp.org, which provides access to a variety of project resources. Contact lsst-sysadmins@lsst.org for this and any DM system administration needs or questions. Be sure to mention that you will need to access git.lsstcorp.org.
Once you have an account, you can view material on the main www.lsstcorp.org page
Subscribe to the lsst-data and lsst-dm-dev mail lists.
Download and install HipChat.
Many meetings are conducted using Google Hangouts. You will need a Google account for this. The main DM meeting site is https://ls.st/sup which supports up to 10 users with both video and audio. Additional participants will be connected via audio only.

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.