The general philosophy LSST software stack is that some python dependencies are so ubiquitous in scientific computing environments that it is more difficult for users to provide new versions than it is to supply them with the stack. The simulations framework relies on the following dependencies that are not part of the LSST stack:
- python 2.7
The recommended install instructions will provide these dependencies for you through an Anaconda distribution
From the rest of the official LSST software stack, it depends on
There are additional python, third-party dependencies, all of which can be installed through the LSST software distribution package manager.
These additional packages are:
and depending on what kind of database you'd like to use, there will be some additional dependency on a python SQL driver for your database. SQLite compatibility is built into python, and LSST provides MySQL and SQLServer compatibility.
Recommended Installation Instructions
The recommended (simplest) approach is to use the newest W14 LSST software stack, and use the LSST-managed version of anaconda python. (Note that you can still use your own python instead - if you prefer this method, instructions for this custom procedure are included on this page).
Start by installing the necessary parts of the LSST software stack and the LSST-installed anaconda.
Here, we assume you are installing the stack in the directory ~/lsst, but feel free to replace that with any directory you like.
Answer the prompts for newinstall.sh – in particular, choose 'yes' to have LSST install and manage Anaconda python. The newinstall.sh script will then install Anaconda python for you and declare this to eups (LSST's software package manager).
After running 'bash newinstall.sh' above, then enter (if you use .csh)
this will install MAF and all it's dependencies, and declare them to eups (the LSST software package manager).
Alternatively, if you use .bash, then enter 'source loadLSST.sh' (and substitute loadLSST.sh everywhere for loadLSST.csh below). The rest of these instructions also assume .csh shell .. if you use .bash instead, simply translate 'setenv' into 'EXPORT' statements.
The following is convenient to add a file that is easy to source when you log in, so that the LSST stack and MAF can be set up and ready to go in one step. (Adding these to your .cshrc is optional). (Note that you do NOT have to define LSST_HOME before sourcing the loadLSST.csh file).
DONE! You are ready to try out the MAF examples.