1 Installation {#installation}
6 # Binary installation {#installation_binary}
8 Binary installation is strongly recommended
for new users of %IMP. It is
9 much faster than building from source code, requires a smaller download,
10 and all the necessary prerequisites are handled
for you automatically.
12 We recommend you use a stable release. These are available
for
13 Windows, Mac and Linux from our [download page](https:
15 Binaries are [also available
for our latest nightly builds](https:
16 please check out the [nightly builds results page](https:
17 to see
if the code is currently stable enough
for your purposes.
19 # Source code installation {#installation_source}
21 ## Prerequisites {#installation_prereqs}
23 In order to build %IMP from source, you will need:
27 [currently work](https:
31 if you want to use Python 3)
33 The following prerequisites are _optional_; without them some parts of %IMP
34 will not build, and some will not
function optimally.
39 - [Modeller](\ref modeller): needed to use the IMP.modeller module.
40 - [CGAL](\ref CGAL): enables faster geometric operations, such as
42 - [Google perf tools](\ref perf): needed only
for profiling %IMP code.
43 - [ANN](\ref ANN): certain data structures will be faster
if it is available.
44 - [GSL](\ref GSL): needed to use the IMP.gsl module.
45 - [OpenCV](\ref OpenCV) (2.1 or later): needed to use the IMP.em2d module or the
46 [idock](@ref idock_pcsk9) and [emagefit](@ref emagefit_3sfd) command
49 modules or the [multifit](@ref multifit_3sfd) command line tool.
51 IMP.cnmultifit module or the [cnmultifit](@ref cnmultifit_groel) command
53 - An [MPI](@ref IMP::mpi) library is needed to use the IMP.mpi module.
54 - The [numpy, scipy](http:
60 for visualization of results.
62 ### Getting prerequisites on Linux {#installation_prereqs_linux}
63 All of the prerequisites should be available as pre-built packages
for
64 your Linux distribution of choice. For example, on a Fedora system the
65 following should install most of the prerequisites:
67 sudo yum install boost-devel gperftools-devel CGAL-devel graphviz gsl-devel cmake doxygen hdf5-devel swig fftw-devel opencv-devel
69 ### Getting prerequisites on a Mac {#installation_prereqs_mac}
71 Mac users must first install Xcode (previously known as Developer Tools)
72 which is not installed by
default with OS X, but is available from the App store
73 (or from the Mac OS install DVD
for old versions of Mac OS). They will also
74 need the Xcode command line tools (install by going to Xcode Preferences, then
75 Downloads, then Components, and select
"Command Line Tools").
77 Then Mac users should use one of the available collections of Unix tools,
82 brew tap homebrew/science
83 brew tap salilab/salilab
84 brew install boost gmp google-perftools cgal graphviz gsl cmake doxygen hdf5 swig fftw mpfr opencv libtau
86 to install everything %IMP finds useful (or that you will want
for installing various useful Python libs that %IMP finds useful). On older Macs, you may also need to `brew install git`
if you want to use git (newer Macs include git).
88 config file or by making an `environment.plist` file) and then
do
90 sudo port install boost cmake swig-python
92 to install the needed libraries and tools. When installing HDF5 with MacPorts, be sure to install `hdf5-18`
93 (version 1.8), rather than the older `hdf5` (version 1.6.9).
96 ### Getting prerequisites on Windows {#installation_prereqs_windows}
98 We recommend Linux or Mac
for developing with %IMP, as obtaining the
99 prerequisites on Windows is much more involved. However,
if you really want
100 to build on Windows, see the
101 [building from source code on Windows](@ref install_windows) page
for the
105 ## Download {#installation_download}
107 - Download the source code tarball from [our download page](https:
109 tar -xvzf ../imp-<version>.tar.gz
111 - Alternatively you can use [git](http:
112 directly from our [GitHub repository](https:
115 git clone -b master https:
116 (cd imp && ./setup_git.py)
118 (the `master` branch tracks the most recent stable
119 release; alternatively you can use `develop` to
get the most recent code,
120 but please check out the [nightly builds results page](https:
121 to see
if the code is currently stable enough
for your purposes).
123 ## Compilation {#installation_compilation}
125 Make a separate directory to keep the compiled version of %IMP in (it
's tidier
126 to keep this separate from the source code, and if you need to later you can
127 just delete this directory without affecting the source). Set up the build
128 with [CMake](@ref cmake_config), then finally compile it, with something
133 cmake <path to IMP source>
136 There are a number of ways in which %IMP can be configured.
137 See [the configuration options page](@ref cmake_config) for more details.
139 ## Testing {#installation_testing}
140 Once the compilation is complete, you can optionally run the test suite.
141 Test are run using `ctest`. A good start is to run `ctest --output-on-failure`.
143 Tests are labeled with the module name and the type and cost of the test, so to run just the expensive tests in the `atom` module, use `ctest -L "^IMP\.atom\-test\-.*EXPENSIVE"`.
145 Benchmarks are simply tests labeled as `benchmark`; examples are tests labeled as `example`.
147 Note that some test failures are to be expected; compare the failures with
148 those at our own [nightly builds page](https://integrativemodeling.org/nightly/results/)
149 if you are concerned.
151 ## Installation {#installation_install}
153 Once everything is compiled (and optionally tested) you can install %IMP
154 by simply running `make install`. If you opted to install in a non-standard
155 location, it is up to you to set up your environment variables so that %IMP
156 can be found (you may need to set `PATH`, `PYTHONPATH`, and `LD_LIBRARY_PATH`).
158 Alternatively, you can run %IMP directly from the build directory by using
159 the `setup_environment.sh` script. This sets the necessary environment
160 variables and then runs the rest of the command line with this modified
161 environment. For example, to run the `ligand_score` command line tool you
164 ./setup_environment.sh ligand_score <arguments>
166 or create a new shell with
168 ./setup_environment.sh $SHELL
172 ligand_score <arguments>