Introduction

Package management of the analysis software that LCLS maintains for users is being transitions to conda, from RPM's. This software includes psana (the software LCLS develops for working with experiment data), hdf5, openmpi, and many python packages such as numpy, scipy, ipython and scikit-beam. Advantages of this transition include

• easier for LCLS to integrate and update new software for users
• easier for offsite users to install psana

User Documentation

Users need to do the following

...

At this point your linux prompt should change to something that starts with the name of the conda environment. For example,

(ana-1.0.7)

Python 3

The LCLS Data Analysis group will maintain conda environments with python 3. To activate the latest python 3 environment, pass the --py3 flag to conda_setup. That is run

...

Note - psana has not been ported to python 3.

...

The python 3 environments do not include software to work with LCLS experiment data files recorded by the data acquisition system.

Managing Conda Environments

• source conda_setup -h for full help on the script
• after sourcing conda_setup, you can execute the undo_conda command to restore your environment
• see conda ana release notes for release notes on these environments
• to switch to an older environment called name, you can Psana Developerscan use conda_setup with the --env name arguments, or use the standard conda source activate name command.

Newer Package Versions

The conda environments will keep up with the latest versions for many standard python packages. Some notable version changes from the RPM based releases

• ipython, version 2.3 -> 5.1
• matplotlib, version 1.4.3 -> 1.5.1
• openmpi, version 1.8.3 -> 1.10.2
• mpi4py, version 1.3.1 -> 2.0.0
• numpy, version 1.9.2 -> 1.11.2 also conda version is based on the intel MK

New package versions means newer features, bug fixes, but it can also mean old interfaces are deprecated, and new bugs crop in. Some users may need to update their code to run with later versions of packages.

Red Hat 5, 6, 7 Issues

Most users will run on rhel7 machines - anyone doing analysis on the interactive machines or submitting batch jobs to the usual queues will use rhel7 machines. There are some rhel6 and rhel5 machines in the experiment hutch control rooms. In particular users running from shared memory may have to run on a rhel6 or rhel5 host.

Continuum (which produced conda) suggests linux packages be built once in a way that runs on any linux operating system - rhel5, rhel6, rhel7, ubuntu, etc. In practice, for large packages like openmpi that the LCLS Data Analysis group must build local versions of, this can get very technical and lead to a brittle system. Similarly, conda-forge, a primary source of conda packages, decided to not support rhel5 for technical reasons.

The LCLS Data Analysis group is presently maintaining 3 separate conda installations, one for rhel5, rhel6, and rhel7. Locally built packages, like openmpi, hdf5, and psana, will be built natively on each platform. The conda_setup script will automatically detect rhel5 vs rhel6 vs rhel7 and activate an environment in the appropriate installation. Use conda_setup to get into a conda environment.

However since conda-forge does not support rhel5, certain packages will not function on rhel5 (for example, opencv, which we obtain from conda-forge). In general, our support for rhel5 is more limited with the conda releases than the RPM releases. Rhel5 users may not be able to use a conda environment.

Moreover it is possible that we install a package that is limited to rhel7. Today - the only such package is tensorflow.

Test Release

Adding a Package

...