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
- LSST Code Repositories
- Standards and Policies
- DM Coding Style Policy
- Python Coding Standard
- C++ Coding Standard
- How to use C++ templates
- Policy on use of C++11/14 language features
- On Using 'Using'
- C++ Coding Standards Compliance
- Documentation Standards
- Documentation Guidelines
- Policy on Updating Doxygen
- DM Wiki Use
- Git Commit Best Practices
- DM Branching Policy
- Coverage Analysis
- Profiling
- Software Unit Test Policy
- Config for VIM
- DM Acknowledgements of Use
- Discussion and Decision Making Process
- Transferring Code Between Packages
- Team Culture and Conduct Standards
- Policy on Changing a Baseline Requirement
- The LSST Software Build Tool
- Project Planning for Software Development
- DM Legacy Pages
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.
- DM source code is distributed under the GPL-3 license. Developers must insert the copyright/license statement at the beginning of all source files. The official text is located at https://www.lsstcorp.org/LegalNotices/LsstSourceCopyrightNotice.txt.
DM Reviews
Various kinds of review of the DM software are conducted during development.
Recent space activity
1 Comment
Gregory Dubois-Felsmann
"Archived" this space today, 2020-02-10.