Installation on most systems is rather straightforward - as the bulk of the PDB2PQR code is written in Python, the PDB2PQR code itself is architecture/compiler independent. PDB2PQR has been tested using Python versions 2.6 through 2.7 - problems will occur with other versions.
If you would like to enable pdb2pka or ligand support, then you must have Numpy installed. http://numpy.scipy.org/
Networkx is now required for pdb2pka support. https://networkx.github.io/
PDB2PQR will need to be configured and compiled in order to run:
$ python scons/scons.py (see python scons/scons.py --help for more options)
This should configure pdb2pqr and compile the pdb2pka wrappers necessary to interface with PDB2PQR and ligand support.
Compilation and installation can be configured by editing the build_config.py file. This is the preferred way to configure the program. Instructions and examples for each setting are included in the file.
These will override any setting in build_config.py.
PREFIX=<DIR> Set install directory. Default is ~/pdb2pqr URL=<URL> Set url for the website. Default http://<COMPUTER NAME>/pdb2pqr/ APBS=<APBS_BINARY> Location of APBS binary. OPAL=<OPAL_URL> Set URL for Opal service APBS_OPAL=<APBS_OPAL_URL> Set URL for APBS Opal service. MAX_ATOMS=<MAX_ATOMS> Sets the maximum number of atoms in a protein for non-Opal job submission. Only affects web tools. Default is 10000 BUILD_PDB2PKA=False Disable pkb2pka compilation. Needed if no C++ compiler is installed or numpy is not installed. pdb2pka is required for ligand support.
Installing is only needed if you plan to set up the web service or to make the install available to all users.
The installation location is specified by the
PREFIX setting above.
If you are planning to invoke the flag,
you will need to build the python APBS libraries and set your library path to point to them. For APBS build instructions see the documention provided here.
pdb2pqr will be configured to use whichever python was used to run the build script. If you would like to use a different installed python to run pdb2pqr run the scons/scons.py script with that python. For example:$ /opt/python27/python scons/scons.py
If ligand support is required Numpy must be installed on the python used to build pdb2pqr.
Compilation of pdb2pka on Windows requires that VS2008 or VS Express 2008 and Windows SDK 6.0A installed in the default location. MinGW is no longer supported.
If numpy cannot be installed directly on the python used to run pdb2pqr you can either install numpy for your local user account or use virtualenv. Homebrew may be an option on OSX. http://docs.python.org/2/install/index.html#alternate-installation http://stackoverflow.com/questions/7465445/how-to-install-python-modules-without-root-access http://www.virtualenv.org
##Binary Builds A PyInstaller spec file is included if a stand alone binary build (no python install or compile required to run) is desired. http://www.pyinstaller.org/
PyInstaller 2.1 or newer installed as python library is required. To create standalone build, first build the application as normal then run
in the root archive folder. The distributable program will be in the dist/pdb2pqr folder.
Each supported platform has different needs when creating the binary build:
On windows pywin32 is required.
The built binaries will dynamically link against the system standard libs. For this reason the Linux binaries should be built on an older system to increase compatibility if needed.
On the Mac you must use homebrew and use the python that it installs with
brew python. See http://brew.sh/ and https://github.com/Homebrew/homebrew/wiki/Homebrew-and-Python
Once homebrew python is setup and configured correctly pyinstaller, numpy and networkx can be installed with
pip install numpy,
pip install pyinstaller, and
pip install networkx.
If the global python is used the binary will fail when the
--ligand option is used.
Similar to Linux, this binary is dynamically linked against the system libraries. The binary will not work on OSX older than the version built on.
We officially support OSX 10.6 or newer.
##Documentation Please see the main documentation at doc/userguide.html for a complete look at installation, compiler/architecture support, and a general FAQ.