Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

creating tbl file #873

Closed
pallavi-compchem opened this issue Apr 23, 2024 · 6 comments
Closed

creating tbl file #873

pallavi-compchem opened this issue Apr 23, 2024 · 6 comments
Assignees
Labels
CNS Improvements in the CNS engine community contributions from people outside the haddock team discussions Discussions / Brainstorming

Comments

@pallavi-compchem
Copy link

Hi there,

I am unable to find an explanation of the tbl file for imposing interaction restraints. Could you please help understand the format of the tbl file and how to create such files?

Thanks.

Best,
Pallavi

@VGPReys
Copy link
Contributor

VGPReys commented Apr 23, 2024

Hi Pallavi,

Please refer to the Nature Protocols and Nature Protocols Correspondence paper where everything is well described.
Also, you can use our GenTBL online tool to generate a restraints file based on residues ids.

Cheers

@VGPReys VGPReys added discussions Discussions / Brainstorming CNS Improvements in the CNS engine community contributions from people outside the haddock team labels Apr 23, 2024
@VGPReys VGPReys self-assigned this Apr 24, 2024
@VGPReys VGPReys closed this as completed Apr 24, 2024
@pallavi-compchem
Copy link
Author

Hi,

Thanks for the links! I have now an understanding of the general syntax, but I still have one question. In the protein-DNA docking example, the cro_air.tbl shows:

assign ( resid 27 and segid A)
(
( resid 32 and segid B and (name O2 or name O4 or name H3 or name C2 or name C4 or name C5 or name C6 or name C7))
or
( resid 33 and segid B and (name O2 or name O4 or name H3 or name C2 or name C4 or name C5 or name C6 or name C7))
or
( resid 34 and segid B and (name N3 or name N7 or name O6 or name H1 or name H22 or name H21 or name C2 or name C4 or name C5 or name C6 or name C8))
) 2.0 2.0 0.0

Does this imply that center of mass of the residues connected by "or" (residues 32, 33, 34) is used for the distance restraint?

@amjjbonvin
Copy link
Member

amjjbonvin commented Apr 24, 2024 via email

@VGPReys VGPReys reopened this Apr 24, 2024
@pallavi-compchem
Copy link
Author

Ok, understood!

Also, what is the difference between Haddock restraints for 1st partner vs those for 2nd partner? Can't we put all the restraints in one section? For the same protein-DNA docking example,
I see the following under "HADDOCK AIR restraints for 1st partner":
assign ( resid 27 and segid A)
(
( resid 32 and segid B and (name O2 or name O4 or name H3 or name C2 or name C4 or name C5 or name C6 or name C7))
or
( resid 33 and segid B and (name O2 or name O4 or name H3 or name C2 or name C4 or name C5 or name C6 or name C7))
or
( resid 34 and segid B and (name N3 or name N7 or name O6 or name H1 or name H22 or name H21 or name C2 or name C4 or name C5 or name C6 or name C8))
) 2.0 2.0 0.0
!

and the following under "HADDOCK AIR restraints for 2nd partner":
assign ( resid 34 and segid B and (name N3 or name N7 or name O6 or name H1 or name H22 or name H21 or name C2 or name C4 or name C5 or name C6 or name C8))
(
( resid 27 and segid A)
or
( resid 29 and segid A)
) 2.0 2.0 0.0
!

Residues 27, 29, 34 are mentioned twice.

@VGPReys
Copy link
Contributor

VGPReys commented Apr 25, 2024

The first selection is called active residue, while the second selection is called passive residue.

Restraints penalties only apply on active residues.

Therefore having the reverse (in the "HADDOCK AIR restraints for 2nd partner"), allows to define previously described passive (from chain B) residues as active, and vice-versa.

@pallavi-compchem
Copy link
Author

Got it! Thanks :)

@VGPReys VGPReys closed this as completed Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CNS Improvements in the CNS engine community contributions from people outside the haddock team discussions Discussions / Brainstorming
Projects
None yet
Development

No branches or pull requests

3 participants