...
There are some additional requirements for the simulations packages, mostly python dependencies that are so ubiquitous in scientific computing environments that it is more difficult for users for us to provide new versions than it is to supply them with the stack. These requirements are (there is some overlap here with the basic stack requirements):
- python 3.6
- cmake - available from conda if required
- gfortran (which is necessary to build the ephemeris-generating software package oorb – this is ONLY needed if you are installing sims_movingObjects in addition to lsst_sims)
- On linux systems, gfortran is probably preinstalled. Otherwise, you can get gfortran binaries from https://gcc.gnu.org/wiki/GFortranBinariesMacOS or (on a mac) from the homebrew distribution (brew install gcc).
...
You do not need to do "eups distrib install lsst_distrib", as described on the pipelines page, as we will install the required simulations packages below. .
If you are intending to install an older version of sims, you should use the corresponding tag of newinstall.sh , e.g.:
| Code Block |
|---|
curl -OL https://raw.githubusercontent.com/lsst/lsst/w.2020.06/scripts/newinstall.sh |
which may in turn require prerequisites from the appropriate version of the documentation at https://pipelines.lsst.io/v/w_2020_06/install/prereqs/
Note that the https://pipelines.lsst.io/install/newinstall.html pages go on to describe LSST Data Management packages (lsst_apps and lsst_distrib) that include additional software not necessary for simulations (although it may be very useful for you!). This includes the LSST data management demo package. You may find it interesting for image processing and catalog purposes, but it is not directly related to installation and use of the simulations packages.
...
This will install all packages currently in the catalogs simulations framework (CatSim) and metrics analysis framework (MAF) and all dependencies. The installation should take on the order of 1 hour, with a final required installation size of 10GB. Note that sims_weekly_tag will change depending on which weekly you want to install. Sims weekly tags are of the form sims_w_YYYY_WW. There is no good place to find what weekly has been most recently published, unfortunately. If you look at the release tab on the lsst/afw repository you should see what the latest release is. If, for example, the latest release is w.2019.14, then sims_weekly_tag will be sims_w_2019_14.
If you are using an older sims weekly tag, it is safest to use the corresponding version of newinstall.sh
The `shebangtron` command is there to correct the paths to installed binaries of Data Management software packages. Every time you install new binary packages, you will need to run the `shebangtron` command.
...