HADDOCK2.4 manual - PDB files
Note: We advise you to consult our online tutorial about the local installation and use of HADDOCK2.4 where you will find many more tips and instructions to prepare your PDB files for docking.
In order to run HADDOCK you need to have the structures of the molecules (or fragments thereof) in PDB format. There are a few points to pay attention to when preparing the PDBs for HADDOCK.
Make sure that all PDB files end with an END statement
HADDOCK will check for breaks in the chain (e.g. missing density in crystal structures or between the two strands of a DNA molecules). In the case of multiple chains within one molecule (e.g. DNA) or in the presence of co-factors, it is however recommended to add a TER statement in between the chains/sub-molecules.
If your molecule consists of multiple chains with overlapping numbering you will have to renumber those (or shift the numbering of some parts) in order to avoid overlapping numbering. HADDOCK will treat each molecule with a single chainID and overlap in numbering will lead to problems. Refer for detailed instruction on this topic to our online local installation tutorial.
Higher resolution crystal structures often contain multiple occupancy side-chain conformations, which means one residue might have multiple conforamtions present in the crystal structure, each with a partial occupancy. The is often reflected by the presence of a
Bbefore the residue name for the atoms having multiple conformations. To avoid problems, only one conformation should be retained (the web server will raise an error for such cases). This can be easily done using our PDB-tools. Alternatively you can also make use of our new PDB-tools webserver for this. The script that allows you to remove double occupancies is
pdb_selaltloc. Its default behavior is to only keep the fisrt (
A) conformation, but you can select other conformations if wanted.
When starting from an ensemble of structure like, for example, from an NMR PDB entry, split structures into single PDB files. Make sure that each structure file ends with an END statement and does not contain any SEGID. Refer for detailed instruction on this topic to our online local installation tutorial.
HADDOCK can deal with ions. You will have however to make sure that the ion naming is consistent with the ion topologies provided in HADDOCK (check for this the ion.top file in the toppar directory. For example, a CA heteroatom with residue name CA will be interpreted as a neutral calcium atom. A doubly charged calcium ion should be named CA+2 with as residue name CA2 to be properly recognized by HADDOCK.
(See also the FAQ for docking in the presence of ions).
A list of supported modified amino acids and ions is available online on the haddock2.4 web server page.
Note: Most of the tasks mentioned above can also be performed using our PDB-tools python scripts (Rodrigues et al. F1000 Research) to manipulate PDB files, select and rename chains and segids, renumber residues… and much more! See for this our GitHub repository. Alternatively you can also make use of our new PDB-tools webserver . Some examples are also provided in the HADDOCK2.4 local installation tutorial.