Closed laurenreid1 closed 1 year ago
This is because you set the variable cas_intdiel=1
, which assigns internal dielectric constant values depending on the residue being mutated. We discussed related aspects in this issue.
Let me know if you have any questions.
Hi @Valdes-Tresanco-MS,
Thanks for the speedy reply! Having read the documentation and the paper linked in the issue, I'd like to check that my understanding is correct: To compare the deltaH(bind) from multiple alanine scanning simulations, I need to use the default cas_intdiel=0 and PB indi = 1.0 for each system? This will make the different alanine scan mutant calculations comparable but some will have larger errors than others depending on the nature of the residue in question?
Thanks!
Yes and no. The results you get can be comparable to each other in any instance. However, it is sensible to use the same internal dielectric constant (intdiel). In the article, they observed a better correlation of the mutant DDG vs experimental (for the systems they tested) if the intdiel was varied according to the mutated residue. The remainder is sacrificed for trying to predict the importance of the contribution of that particular residue. In general, they found that the results fit better under these conditions than if they used the same intdiel. Along these same lines, it is important to remember that these methods are good for comparisons with relative values, not absolute ones. However, these may be specific cases, and may not be suitable for your system. In certain cases, as discussed in #280, the variation in the electrostatic component (EEL and EPB) is so large that it creates more problems than solutions. In any case, we implement tools that can be useful in some cases and not in others. It is important to understand how they work and in which cases to apply them. Let me know any doubts
Thanks a lot for your detailed reply, that has clarified the setting for me!
Bug summary
I have run 4 ST mmpbsa calculations on a protein-protein complex using the same trajectory and the same general settings. 1 calculation was run on the wild type (WT) trajectory and the other 3 calculations were run on the same WT trajectory with the same settings but also incorporated an alanine scan calculation in each one. My question relates to the WT calculation produced by each gmx_mmpbsa run. I observed that 2 of the calculations (the original WT-only calc and the WT calc produced by one of the alanine scan runs) produced exactly the same enthalpy, however the other 2 calculations produced quite different numbers for the enthaply. Specifically, the EEL and EPB contributions are different, and the remaining terms are the same.
If an mmpbsa calculation is run on the same trajectory with exactly the same settings, shouldn't the result be the same each time, or is there are a random seed used in the calculation that could be causing this discrepancy? If it's caused by a difference in a random seed, how should I interpret the results?... is it a sign of lack of convergence in my trajectory?
The 4 WT results are as follows:
1) WT-only calculation:
2) WT calculation from alanine scan 1:
3) WT calculation from alanine scan 2:
4) WT calculation from alanine scan 3:
Terminal output
gmx_MMPBSA.log
-
Operating system
Linux
gmx_MMPBSA Version
v1.6.1
Python version
3.9.15
Installation
None