...
Any of the above packages and all their dependencies can be installed by replacing lsst_sims with the appropriate package name in the above code snippet (e.g. sims_maf). Installation is now complete. See package specific pages for documentation.
4. Setup installed packages
You have now downloaded and built all of the packages in lsst_sims. These packages are designed to be totally self-contained. They have been built in the directories
| Code Block |
|---|
$LSST_HOME/yourOperatingSystem/yourPackageName/ |
where yourOperatingSystem is 'DarwinX86' for Mac users and 'Linux64' for Linux users. In order to use the packages you installed, you must add these directories to your $PYTHONPATH. This is done using
| Code Block |
|---|
setup your_package_name -t your_package_tag |
setup is an eups command. your_package_name is the name of one of the packages you have installed (e.g. sims_maf or sims_catUtils). your_package_tag is a tag eups uses to keep track of the versions of each package you have built on your machine. This corresponds to the argument of '-t' in the 'eups distrib install' command above. So, if you wanted to setup the version of MAF you just downloaded, you would use
| Code Block |
|---|
setup sims_maf -t sims |
When you setup a package, eups inspects it and determines what other packages it depends on. Eups will also setup those prerequisite packages, preferring versions tagged with the tag you specified and defaulting to versions with the tag 'current'. If you do not want to default to 'current', you can specify more than one tag.
| Code Block |
|---|
setup sims_maf -t sims -t $USER |
will setup sims_maf and all of its dependencies, preferring versions tagged as 'sims,' using versions tagged as '$USER' if no 'sims' version exists, and only using 'current' if neither 'sims' nor '$USER' can be found. This system of eups tags allows you to have multiple versions of the stack built on your system simultaneously. You will only ever be using the one that eups has setup. To see which versions of a package exist on your system (and which has been setup) use
| Code Block |
|---|
eups list -v your_package_name |
Known issues:
- If you have issues with installation, first check that your system meets the minimum requirements listed here: LSST software user guide prerequisites.
- If you are having issues specifically with pyephem or healpy on a Mac, check for the existence of a /Developer directory. This is obsolete after upgrading to newer versions of XCode, but not removed by the XCode installer. Rename the /Developer directory and pyephem will install.
- If you are using your own python, be sure to check the Using Your Own Python page.
- If you are using your own anaconda python, be sure it is not installed in /anaconda (install somewhere like your home directory instead). This should be fixed in a new release soon.
- On a Mac, make sure you have accepted the terms on XCode. You can do this by opening the Xcode.app (should be in your Applications folder).
- git can fail, complaining about not having an https helper. If your native git version is > 1.7, you can probably use that rather than the LSST installed git.
- If all else fails, it's usually an issue with some environment variables interfering with the installation. You can create a new user and install the stack there. You can quickly login/out of a new user account as follows: First make a new admin-level user in System Preferences->Users and Groups, and then click on your name in the top right hand corner of the screen. A drop-down menu should appear, offering you a choice of other users to log in as. You might have to toggle the check box in System Preferences->Users and Groups->Login Options first though.
...