I am trying to use Haddock to dock heme to a couple of proteins but am having trouble with the heme pdb file, in particular how to name the Fe2+ ion. I’ve tried to use HEC as the residue name since this, as far as I understand is described in the topology files used by Haddock. I thought it was working but on close inspection Haddock is complaining about the Fe2+ ion and the last time I tried it wouldn’t run. Please find the last few lines of the heme pdb file below. I would really appreciate any help on this.
Thanks in advance,
Susanna
HETATM 40 C4C HEC A 202 0.364 -3.364 -14.250 1.00 5.95 C
ANISOU 40 C4C HEC A 202 694 666 901 -85 -24 -32 C
HETATM 41 C4D HEC A 202 -0.404 -7.457 -13.263 1.00 6.39 C
ANISOU 41 C4D HEC A 202 919 552 957 -143 2 3 C
HETATM 42 NC HEC A 202 0.117 -3.937 -15.473 1.00 5.95 N
ANISOU 42 NC HEC A 202 826 541 895 -185 -53 -52 N
HETATM 43 FE+2 HEC A 202 -0.143 -5.892 -15.842 1.00 5.79 FE
ANISOU 43 FE+2 HEC A 202 830 527 844 -134 -18 -1 FE
Thanks for the reply!
I tried the docking with the heme c coordinates you sent but it still doesn’t work. I get the following error message from Haddock:
waiting for the psf files…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.psf…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.pdb…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.psf…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.pdb…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.psf…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.pdb…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.psf…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.pdb…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.psf…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.pdb…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.psf…
waiting for /home/enmr/services-enmr/HADDOCK2.2/server/run/userrun000026/run1/begin/protein2.pdb…
Error in the topology generation: prot_psf_B could not be created
=> HADDOCK stopped
And in generate_B.out the error message is as follows:
ASSFIL: file protein2.pdb opened.
COOR>ATOM 1 FE HEC 400 3.565 0.487 0.949 1.00 0.00
COOR>ATOM 2 NA HEC 400 2.428 0.067 -0.589 1.00 0.00
CNSsolve>
CNSsolve> show sum(1) ( not(hydrogen) and not(known) )
SELRPN: 0 atoms have been selected out of 75
SHOW: zero atoms selected
CNSsolve> if ( $select = 0 ) then
NEXTCD: condition evaluated as true
CNSsolve> display %INFO: There are no coordinates missing for non-hydrogen atoms
%INFO: There are no coordinates missing for non-hydrogen atoms
CNSsolve> end if
CNSsolve>
CNSsolve> if ( $log_level = verbose ) then
NEXTCD: condition evaluated as false
CNSsolve> set message=normal echo=on end
CNSsolve> else
CNSsolve> set message=off echo=off end
%SELRPN-BYNU-ERR: no valid number 0
%SELRPN error encountered: no valid number
(CNS is in mode: SET ABORT=NORMal END)
Yes, I am using the web server. I added the chain name B to the file you sent and defined it in the run. I just tried again and it was the same error message. The link to the run should be arriving in an email.
You had run into an issue appearing only when docking a single heme into a protein (the result of a recent addition that should automatically recognise covalently heme groups). This has now been corrected in the production server.