# Force field and scoring function

**URL:** <https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206>\
**Category:** HADDOCK\
**Created:** [August 11, 2024, 12:51pm UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206 "2024-08-11T12:51:45Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@michael](https://ask.bioexcel.eu/u/michael)\
**Post date:** [August 11, 2024, 12:51pm UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/1 "2024-08-11T12:51:46Z")

</div>

Hi,  
I read a lot of HADDOCK background and I want to ensure I understood correctly- the forcefield used in haddock2.4 local version is OPLSX non-bonded parameters, while there is an option to use the course-grained I specified. Correct?  
{\* Coarse grained molecule? \*}

Also, I have seen this figure on violations for AIR, but how are the violations calculated from unambiguous restraints?  
And I will very much appreciate the source article.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/bioexcel/original/2X/a/a09621331686c70eaeee2eb28ded0d6b91630cda.jpeg)

Thank you very much

The HADDOCK category is meant to discuss any HADDOCK-related issue. For general information about HADDOCK refer to [HADDOCK – Bonvin Lab](http://www.bonvinlab.org/software/haddock2.4)

---

<div class="post-metadata">

**Author:** ![VGPReys](https://dub1.discourse-cdn.com/flex013/user_avatar/ask.bioexcel.eu/vgpreys/32/960_2.png) [@VGPReys](https://ask.bioexcel.eu/u/VGPReys)\
**Post date:** [August 12, 2024, 7:01am UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/2 "2024-08-12T07:01:41Z")

</div>

Hi Michael,

> [@michael](#):
>
> the forcefield used in haddock2.4 local version is OPLSX non-bonded parameters

Yes indeed

> [@michael](#):
>
> there is an option to use the course-grained I specified. Correct?

Yes, in that case, first the structure is being coarse grained with Martini2.2 and the corresponding force-field is used.

Here is the reference:  
**D.H. de Jong, G. Singh, W.F.D. Bennett, C. Arnarez, T.A. Wassenaar, L.V. Schäfer, X. Periole, D.P. Tieleman, S.J. Marrink**  
_Improved Parameters For The Martini Coarse-Grained Protein Force Field_, J. Chem. Th. Comp, 9:687–697, 2013. [DOI:10.1021/ct300646g](http://pubs.acs.org.proxy-ub.rug.nl/doi/abs/10.1021/ct300646g)

With the hope these answers will help you.

Cheers

---

<div class="post-metadata">

**Author:** ![michael](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@michael](https://ask.bioexcel.eu/u/michael)\
**Post date:** [August 12, 2024, 7:20am UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/3 "2024-08-12T07:20:17Z")

</div>

Thank you  
So how are there restraints violations (positive NOE violations + Eair) if I only use unambiguous restraints?  
how are those calculated?  
My understanding is that constraints always have to be obeyed, and they are not always

---

<div class="post-metadata">

**Author:** ![amjjbonvin](https://dub1.discourse-cdn.com/flex013/user_avatar/ask.bioexcel.eu/amjjbonvin/32/23_2.png) [@amjjbonvin](https://ask.bioexcel.eu/u/amjjbonvin)\
**Post date:** [August 12, 2024, 7:58am UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/4 "2024-08-12T07:58:17Z")

</div>

Actually unambiguous restraints can be violated in the same way as ambiguous restraints. And violations will depend on the effective distance being calculated compared to your restraint range definition

> ![](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/48.png)michael:
> 
> how are the violations calculated from unambiguous restraints

There are none. Unambiguous restraints should be considered more as **constraints**.

With the hope these answers will help you.

Cheers

---

<div class="post-metadata">

**Author:** ![michael](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@michael](https://ask.bioexcel.eu/u/michael)\
**Post date:** [August 12, 2024, 12:41pm UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/5 "2024-08-12T12:41:47Z")

</div>

I’m sorry, but I don’t understand  
From what I know constraints mean they cannot be violated, therefore how can you say  
“Actually unambiguous restraints can be violated in the same way as ambiguous restraints. And violations will depend on the effective distance being calculated compared to your restraint range definition”  
From this sentence, it seems there can be a violation (and therefore I see in the results that there are violations even though the only restraints I use are unambiguous)

---

<div class="post-metadata">

**Author:** ![amjjbonvin](https://dub1.discourse-cdn.com/flex013/user_avatar/ask.bioexcel.eu/amjjbonvin/32/23_2.png) [@amjjbonvin](https://ask.bioexcel.eu/u/amjjbonvin)\
**Post date:** [August 12, 2024, 1:14pm UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/6 "2024-08-12T13:14:04Z")

</div>

Because they are restraints and not constraints

---

<div class="post-metadata">

**Author:** ![michael](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@michael](https://ask.bioexcel.eu/u/michael)\
**Post date:** [August 12, 2024, 1:19pm UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/7 "2024-08-12T13:19:55Z")

</div>

but you wrote also  
" Unambiguous restraints should be considered more as **constraints**."

I’m sorry for this confusion, I don’t understand

---

<div class="post-metadata">

**Author:** ![amjjbonvin](https://dub1.discourse-cdn.com/flex013/user_avatar/ask.bioexcel.eu/amjjbonvin/32/23_2.png) [@amjjbonvin](https://ask.bioexcel.eu/u/amjjbonvin)\
**Post date:** [August 13, 2024, 2:01am UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/8 "2024-08-13T02:01:13Z")

</div>

This was a mistake - they are restraints!  
Sorry for the confusion

---

<div class="post-metadata">

**Author:** ![VGPReys](https://dub1.discourse-cdn.com/flex013/user_avatar/ask.bioexcel.eu/vgpreys/32/960_2.png) [@VGPReys](https://ask.bioexcel.eu/u/VGPReys)\
**Post date:** [August 13, 2024, 7:00am UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/9 "2024-08-13T07:00:39Z")

</div>

> [@michael](#):
>
> but you wrote also  
> " Unambiguous restraints should be considered more as **constraints**."

I am very sorry michael that you got confused, I guided you wrong.  
I just learned something here.  
I modified my first post so future user will no more get confused.

---

<div class="post-metadata">

**Author:** ![michael](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@michael](https://ask.bioexcel.eu/u/michael)\
**Post date:** [August 13, 2024, 12:10pm UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/10 "2024-08-13T12:10:59Z")

</div>

thank you  
Ok so this is the function

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/bioexcel/original/2X/6/6a159cb49b0b02947a10c8d413cdb979a26dbd11.png)  
If I have a restraint were the distance allowed is “3.3 1.0 1.0” (so the range is between 2.3 and 4.3), how will the value of this function be implemented in the docking scoring Eair? I can’t find anywhere the full calculations. Is this on purpose?  
If not can you please explain/ send a source article?  
Thank you

---

<div class="post-metadata">

**Author:** ![amjjbonvin](https://dub1.discourse-cdn.com/flex013/user_avatar/ask.bioexcel.eu/amjjbonvin/32/23_2.png) [@amjjbonvin](https://ask.bioexcel.eu/u/amjjbonvin)\
**Post date:** [August 13, 2024, 1:34pm UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/11 "2024-08-13T13:34:06Z")

</div>

See: [https://ask.bioexcel.eu/t/how-is-eair-calculated/4085](https://ask.bioexcel.eu/t/how-is-eair-calculated/4085)

And remember the forum is searchable 🙂

---

<div class="post-metadata">

**Author:** ![michael](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@michael](https://ask.bioexcel.eu/u/michael)\
**Post date:** [August 26, 2024, 11:45am UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/12 "2024-08-26T11:45:34Z")

</div>

> [@michael](#):
>
> OPLSX non-bonded paramet

Hi,  
I just want to make sure- the “X” in OPLSX stands for some extension/ version that I’m assuming HADDOCK forum will not share?

---

<div class="post-metadata">

**Author:** ![amjjbonvin](https://dub1.discourse-cdn.com/flex013/user_avatar/ask.bioexcel.eu/amjjbonvin/32/23_2.png) [@amjjbonvin](https://ask.bioexcel.eu/u/amjjbonvin)\
**Post date:** [August 27, 2024, 9:34am UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/13 "2024-08-27T09:34:43Z")

</div>

No - it is the standard version which has been used e.g. for NMR structure calculations and distributed with HADDOCK as described e.g. in:

- J. Linge, M.A. Williams, C.A.E.M. Spronk, A.M.J.J. Bonvin\* and M. Nilges\* [Refinement of protein structures in explicit solvent.](https://www3.interscience.wiley.com/cgi-bin/abstract/102523901/START) _PROTEINS: Struct. Funct. & Genetics_ _50_, 496-506 (2003).

---

<div class="post-metadata">

**Author:** ![michael](https://avatars.discourse-cdn.com/v4/letter/m/4bbf92/32.png) [@michael](https://ask.bioexcel.eu/u/michael)\
**Post date:** [August 27, 2024, 4:54pm UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/14 "2024-08-27T16:54:58Z")

</div>

> [@amjjbonvin](#):
>
> standard version which has been used e.g. for NMR structure calculations and distributed with HADDOCK as described e.g. in:

Thank you  
So what does the X stand for? explicit? Since I do not see the word OPLSX in the article.

---

<div class="post-metadata">

**Author:** ![amjjbonvin](https://dub1.discourse-cdn.com/flex013/user_avatar/ask.bioexcel.eu/amjjbonvin/32/23_2.png) [@amjjbonvin](https://ask.bioexcel.eu/u/amjjbonvin)\
**Post date:** [August 28, 2024, 6:47am UTC](https://ask.bioexcel.eu/t/force-field-and-scoring-function/5206/15 "2024-08-28T06:47:07Z")

</div>

Historical naming… I actually don’t know if X has a special meaning.
