Ha14 installation: Difference between revisions

From cctbx_xfel
Jump to navigation Jump to search
(Used mbox for leading note.)
m (Aaron moved page Installation to Ha14 installation: deprecated installation instructions)
 
(25 intermediate revisions by 4 users not shown)
Line 1: Line 1:
This document aims to be a step-by-step installation guide for ''cctbx.xfel''.  Note that in this text <code>$</code> denotes the prompt of any unprivileged user on the system.  Certain shells may be configured to use <code>%</code> or <code>&gt;</code> for that purpose.  The user prompt is distinct from <code>#</code>, which denotes the prompt of the superuser.  The prompt should <em>not</em> be included in the command typed to the shell.  This installation can be performed by any regular user—no superuser privileges are required.
== Prerequisites ==


{{ mbox
While these tutorials assume you wish to process XTC streams at SLAC, some users have stills collected from other sources and do not need the full PSDM suite.  If this is the case, see the installation directions below for installing on a non PSDM systemOtherwise, it is assumed that the [[Set up PSDM software | PSDM software distribution has been set up]].  Note again that several sites already have ''cctbx.xfel'' installed, and so regular users not involved in the development of the software will not need the instructions here.
| type = notice
| text = installing ''cctbx.xfel'' is not necessary for most users, as ''cctbx.xfel'' is installed at SLAC already and is generally accessibleGeneral users should instead go to [[setup]] to configure their unix account at SLAC to run ''cctbx.xfel.''
}}


Once ''cctbx.xfel'' has been installed it must be [[Setup | set up]] before it can be used.  Developers may additionally want to [[Set up ssh-agent | set up an ssh-agent]]. 


== Prerequisite: install and set up the PSDM suite ==
Finally, you must have a user account on cci.lbl.gov in order to proceed, or else you will not be able to download the sources. A sourceforge account is only needed if you wish to commit changes back to the repository. If you don't have or don't want to use a sourceforge account, you can leave it off in the below commands where it is specified.


See [[Set up PSDM software]]. It is assumed that <code>ana_env.sh</code> or <code>ana_env.csh</code> has been sourced, a release directory has been configured in <code>~/myrelease</code> or <code>~/analisys-rel</code>, and that an empty analysis package has been set up in <code>~/myrelease/my_ana_pkg</code> or <code>~/analisys-rel/my_ana_pkg</code>
== Standard installation using PSDM ==
===Quick start===
This step has to be performed on a host with Internet access. Not all hosts at SLAC have that, but the members of <i>e.g.</i> pslogin pool do. Make and change to a working directory to contain the new source code and build (this directory should be accessible from any computing nodes ''cctbx.xfel'' will be run. Then download these bootstrap modules:


<!-- XXX In addition, these software packages need to be available: reportlab, h5py, etc -->
  wget https://raw.githubusercontent.com/cctbx/cctbx_project/master/libtbx/auto_build/bootstrap.py


== Download and extract ''cctbx'' and ''LABELIT'' source bundles ==
Then:


<!-- XXX Seems to be important to source ana_env.sh before building! XXX Stored in /net/cci/auto_build/cctbx/results -->
  python bootstrap.py hot update --builder=xfel --cciuser=<cciusername> --sfuser=<githubusername>


<!-- XXX This is probably the only place where the developer installation is different from the standard installation. Investigate and accommodate! -->
This command instructs bootstrap.py to download static packages required for ''cctbx.xfel'' (hot), and then to checkout the rest of the sources from cci.lbl.gov and github (update), using the user accounts specified by the cciuser and sfuser parameters, respectively.


Note that developers should follow the instructions in [[Installation for developers]] instead.  This step has to be performed on a host with Internet access. Not all hosts at SLAC have that, but the members of <i>e.g.</i> psexport pool do. In what follows, the absolute path <code><b><i>/path/to/cctbx/directory</i></b></code> should be replaced with something more appropriate. The directory should accessible everywhere ''cctbx.xfel'' is to be run.
===Alternate instructions for non-LBNL developers===
  $ mkdir -p <b><i>/path/to/cctbx/directory</i></b>
Our non-LBNL colleagues will now realize that the "python bootstrap" step does not work without cci username credentials, needed to obtain source code for the program LABELITDevelopers are instructed to use the following alternate procedure:
$ cd <b><i>/path/to/cctbx/directory</i></b>
$ wget http://cci.lbl.gov/cctbx_build/results/2013_08_13_0005/cctbx_bundle.tar.gz
$ wget http://cci.lbl.gov/~hattne/labelit/labelit_bundle_20130814.tar.gz


{{ mbox
  python bootstrap.py hot --builder=xfel --sfuser=<githubusername> # download the static packages
| type = speedy
  python bootstrap.py update --builder=dials --sfuser=<githubusername> # download the github code for dials & cctbx
| text = New bundles are automatically prepared nightly. It is, however, not advisable to automatically update from the latest bundle. Please check with the program authors before upgrading a critical installationAlso note that the labelit_bundle cannot currently be downloaded.
  mkdir modules/cxi_xdr_xes # create a stub directory for experiment-specific python code
}}
Then download phenix from http://phenix-online.org and untar the packageLocate the modules directory in the phenix directory tree, and copy-paste the labelit subdirectory into the modules directory of your current working area.


Extract the sources:
===Finish up the build===
  $ mkdir cctbx_project
After downloading the sources, you need to be sure you have the appropriate compilers before executing the next command. At SLAC, that means you need to ssh to one of the psana nodes, as the pslogin nodes do not have the requisite compilersWhen ready, configure and compile thusly:
$ tar -xpvzf cctbx_bundle.tar.gz -C cctbx_project --strip-components=1
  $ tar -xpvzf labelit_bundle_20130814.tar.gz


<!-- XXX This is duplicated in the developer instructions! -->
  python bootstrap.py build --builder=xfel --with-python=`which python` --nproc=<# cores available for compile>
Add the <code>cxi_user</code> directory and its <code>__init__.py</code> module.  This defines the default integration algorithm used by ''cctbx.xfel''.
$ mkdir cxi_user
$ cat > cxi_user/__init__.py << EOF
from xfel.mono_simulation.mono_treatment import post_outlier_rejection
from xfel.mono_simulation.mono_treatment import pre_get_predictions
EOF


== Configure the source tree ==
On SLAC's interactive nodes, this takes just over 6 minutes. To avoid problems with run-time dynamic linking of Python extensions, the Python interpreter required for the above command must be the one provided by the PSDM software distribution.  That interpreter can be located using find, <i>e.g.</i>
This next two steps require access to a C++ compiler and a Python interpreter.  At SLAC, the members of the psexport pool do not have any compilers installed, but the interactive nodes, reachable <i>via</i> psanacs, do.  The Python interpreter used to configure the source tree must be the same interpreter the PSDM suite uses.  That interpreter can be located using find, <i>e.g.</i>
  $ find $SIT_ROOT/sw/external/python -perm /0111 -type f -wholename "*/$SIT_ARCH/*/python" 2> /dev/null
  $ find $SIT_ROOT/sw/external/python -perm /0111 -type f -wholename "*/$SIT_ARCH/*/python" 2> /dev/null
At SLAC this interpreter is located somewhere under <code>/reg/g/psdm/sw/external/python</code>.  Then create and initialize the build directory using the appropriate Python interpreter.  Developers may want to use slightly different configuration options, see [[Installation for developers]].
At SLAC this interpreter is located somewhere under <code>/reg/g/psdm/sw/external/python</code>.  Here we use `which python` to get this path automatically.   
$ mkdir -p <b><i>/path/to/cctbx_build</i></b>
$ cd <b><i>/path/to/cctbx_build</i></b>
$ <b><i>python</i></b> <b><i>/path/to/cctbx/directory</i></b>/cctbx_project/libtbx/configure.py xfel
where <code><b><i>python</i></b></code> should be substituted with output of the previous find commandThe name and location of the build directory is arbitrary; <code><b><i>/path/to/cctbx/directory</i></b>/cctbx_build</code> is a common choice.


Now, initialise the running shell using the newly created configuration files.  bash-users should do
Initialise the running shell using the newly created configuration files.  bash-users should
  $ . setpaths.sh
  $ . build/setpaths.sh
while csh-users should instead run
while csh-users will instead need to run
  % source setpaths.csh
  % source build/setpaths.csh


To finalize the installation, see [[Setup]].


== Compile the sources ==
Note, you may also follow this procedure if you are on a machine where you have your own python that you want to use, instead of the one provided by PSDM.
If building at SLAC, log into one of the psanacs nodes. Then compile:
$ make
On SLAC's interactive nodes, this takes just over 6 minutes.  To finalize the installation, see [[Setup]].


== Installation on a non-PSDM system ==
If you find yourself on a machine without PSDM and won't be dealing with XTC directly, for example if you have your own data collected as stills from a non-XFEL source, you can use the below commands in a new directory (again assuming you have a cci user account):
  # On Linux:
  wget https://raw.githubusercontent.com/cctbx/cctbx_project/master/libtbx/auto_build/bootstrap.py
  # On MacOSX:
  curl https://raw.githubusercontent.com/cctbx/cctbx_project/master/libtbx/auto_build/bootstrap.py > bootstrap.py
  python bootstrap.py hot update base build --builder=xfel --cciuser=<cciusername> --sfuser=<sourceforgeusername>
Here, in addition to hot, update and build, there's a command called 'base', which downloads a python and needed packages and compiles it.  After this process completes, source the installation (for details see above), and then add scipy to it:
  . build/setpaths.sh
  libtbx.python -m easy_install scipy
Please contact the authors if with any issues.  Some gotchas:
1) On a Mac, you will need to make sure you have the latest version of xcode installed.  Consider the command xcode-select --install. [NOTE: Xcode v. 8.2.1. for Mac OS 10.12 (Sierra) does not include a gFortran compiler. You will need to install gFortran separately if you need scipy.]
2) On linux you will likely need to install some dependencies, including gFortran. [Note: gFortran is needed only for the scipy installation, not for the core build based on cctbx.  Therefore, only install gFortran if you need scipy.]


== External links ==
== External links ==
Line 70: Line 74:


<!-- POSSBILE ADDITIONS:
<!-- POSSBILE ADDITIONS:
HOW TO KEEP UP TO DATE (links to psdm page, links to developers page: these pages assemble all the information in one place).


COMMON PITFALLS:
COMMON PITFALLS:

Latest revision as of 23:13, 6 November 2018

Prerequisites

While these tutorials assume you wish to process XTC streams at SLAC, some users have stills collected from other sources and do not need the full PSDM suite. If this is the case, see the installation directions below for installing on a non PSDM system. Otherwise, it is assumed that the PSDM software distribution has been set up. Note again that several sites already have cctbx.xfel installed, and so regular users not involved in the development of the software will not need the instructions here.

Once cctbx.xfel has been installed it must be set up before it can be used. Developers may additionally want to set up an ssh-agent.

Finally, you must have a user account on cci.lbl.gov in order to proceed, or else you will not be able to download the sources. A sourceforge account is only needed if you wish to commit changes back to the repository. If you don't have or don't want to use a sourceforge account, you can leave it off in the below commands where it is specified.

Standard installation using PSDM

Quick start

This step has to be performed on a host with Internet access. Not all hosts at SLAC have that, but the members of e.g. pslogin pool do. Make and change to a working directory to contain the new source code and build (this directory should be accessible from any computing nodes cctbx.xfel will be run. Then download these bootstrap modules:

 wget https://raw.githubusercontent.com/cctbx/cctbx_project/master/libtbx/auto_build/bootstrap.py

Then:

 python bootstrap.py hot update --builder=xfel --cciuser=<cciusername> --sfuser=<githubusername>

This command instructs bootstrap.py to download static packages required for cctbx.xfel (hot), and then to checkout the rest of the sources from cci.lbl.gov and github (update), using the user accounts specified by the cciuser and sfuser parameters, respectively.

Alternate instructions for non-LBNL developers

Our non-LBNL colleagues will now realize that the "python bootstrap" step does not work without cci username credentials, needed to obtain source code for the program LABELIT. Developers are instructed to use the following alternate procedure:

 python bootstrap.py hot --builder=xfel --sfuser=<githubusername> # download the static packages
 python bootstrap.py update --builder=dials --sfuser=<githubusername> # download the github code for dials & cctbx
 mkdir modules/cxi_xdr_xes # create a stub directory for experiment-specific python code

Then download phenix from http://phenix-online.org and untar the package. Locate the modules directory in the phenix directory tree, and copy-paste the labelit subdirectory into the modules directory of your current working area.

Finish up the build

After downloading the sources, you need to be sure you have the appropriate compilers before executing the next command. At SLAC, that means you need to ssh to one of the psana nodes, as the pslogin nodes do not have the requisite compilers. When ready, configure and compile thusly:

 python bootstrap.py build --builder=xfel --with-python=`which python` --nproc=<# cores available for compile>

On SLAC's interactive nodes, this takes just over 6 minutes. To avoid problems with run-time dynamic linking of Python extensions, the Python interpreter required for the above command must be the one provided by the PSDM software distribution. That interpreter can be located using find, e.g.

$ find $SIT_ROOT/sw/external/python -perm /0111 -type f -wholename "*/$SIT_ARCH/*/python" 2> /dev/null

At SLAC this interpreter is located somewhere under /reg/g/psdm/sw/external/python. Here we use `which python` to get this path automatically.

Initialise the running shell using the newly created configuration files. bash-users should

$ . build/setpaths.sh

while csh-users will instead need to run

% source build/setpaths.csh

To finalize the installation, see Setup.

Note, you may also follow this procedure if you are on a machine where you have your own python that you want to use, instead of the one provided by PSDM.

Installation on a non-PSDM system

If you find yourself on a machine without PSDM and won't be dealing with XTC directly, for example if you have your own data collected as stills from a non-XFEL source, you can use the below commands in a new directory (again assuming you have a cci user account):

 # On Linux:
 wget https://raw.githubusercontent.com/cctbx/cctbx_project/master/libtbx/auto_build/bootstrap.py
 # On MacOSX:
 curl https://raw.githubusercontent.com/cctbx/cctbx_project/master/libtbx/auto_build/bootstrap.py > bootstrap.py
 python bootstrap.py hot update base build --builder=xfel --cciuser=<cciusername> --sfuser=<sourceforgeusername>

Here, in addition to hot, update and build, there's a command called 'base', which downloads a python and needed packages and compiles it. After this process completes, source the installation (for details see above), and then add scipy to it:

 . build/setpaths.sh
 libtbx.python -m easy_install scipy

Please contact the authors if with any issues. Some gotchas:

1) On a Mac, you will need to make sure you have the latest version of xcode installed. Consider the command xcode-select --install. [NOTE: Xcode v. 8.2.1. for Mac OS 10.12 (Sierra) does not include a gFortran compiler. You will need to install gFortran separately if you need scipy.]

2) On linux you will likely need to install some dependencies, including gFortran. [Note: gFortran is needed only for the scipy installation, not for the core build based on cctbx. Therefore, only install gFortran if you need scipy.]

External links