Closed wrmartin closed 2 years ago
Hello there! Usually the fastest way for us to deal with these errors is to send around the files you are using, so we can check closely... Could you pleae send a compressed file with all the files you are using? Make sure to include all the itp files associated with the topologies... Send only few frames in the trajectories...
Cheers!
Best I can do is a link to some files; it's too big to attach here (the trajectories aren't the problem).
Hi Martin The error is related to the number of atoms in the topology and structure file. The structure file only contains the atoms of the selected group (27795) while the topology also contains the atoms that are not removed, for example, CAL, ZN2, SOD, POPS Currently, only the following groups of atoms are automatically removed:
sol_ion = [
# standard gmx form
'NA', 'CL', 'SOL',
# charmm-GUI form ??
'SOD', 'CLA', 'TIP3P', 'TIP4P', 'TIPS3P', 'TIP5P', 'SPC', 'SPC/E', 'SPCE', 'TIP3o', 'WAT']
The way to fix this is by eliminating those molecules and leaving only the ones of interest, for example:
#include "topparr/forcefield.itp"
#include "topparr/PROA.itp"
#include "topparr/PROB.itp"
#include "topparr/PROC.itp"
[ system ]
; Name
Title
[ molecules ]
; Compound #mols
PROA 1
PROB 1
PROC 1
We are working to improve the handling of topologies, given that in some cases eliminating the molecules is not a viable option and focused on the implementation of the consideration of explicit water molecules. However, there is bad news and that is that the current stable version (v1.4.3) has a bug for the MT approach. Currently, we fixed it in part but the development version (v1.5.0) is not ready for production yet. With your system, we managed to identify another problem related to this, so we hope that the new version will be able to do the calculations without difficulty. We are making a huge effort to release the v1.5.0 as soon as possible. We regret not being able to give you the solution immediately, but we assure you that as soon as the new version is released, you will be able to do your calculations without problems. Sincerely.
I don't believe there is an issue regarding the first part. As I noted, the complex works just fine in the ST approach with the files as they are, and only fails when using the MT approach. Sounds like I will just have to be patient for the update, thank you!
Ok, I have identified the error. In version 1.4.3 it is still impossible to carry out the calculation since an error related to the way the topology is generated from the index persists.
You are defining the topology of the ligand with the -rp
option. Currently, gmx_MMPBSA does not check if the option is duplicated, which means that ligand.top
is taken as an argument of -rp
, which will always cause a mismatch between the structure and the topology of the receptor. In version 1.4.3, although the modification of the topology is not necessary, its manipulation is quite limited. In the current version, no modification is necessary and we have much more robust management of the topology, so there should be no future related errors.
We have corrected these problems in the development version. I'll let you know when we're in the final stages of testing for you to install it.
Fixed via f6a3ad0, 6ebdeab
We are in the final stages of testing the new version. You can test if it runs fine for your system. Our tests did not give errors, however, your verification is important to us.
You can test the development version as follows:
conda create --name AmberTools21 python=3.9
conda activate AmberTools21
conda install -c conda-forge mpi4py ambertools=21 compilers
python -m pip install PyQt5
python -m pip install git+https://github.com/Valdes-Tresanco-MS/gmx_MMPBSA
I will close this issue, but if you have any doubts or errors, feel free to open a new one or reopen this one.
I am trying to do PBSA on a protein-protein complex using the CHARMM forcefield, but I'm getting numerous errors. I've been able to "fix" some of them, but I'm stuck here. The receptor for the system is also a multimer, and using a single-trajectory approach on the receptor only (and also the complex) work fine. A multi-trajectory approach on the receptor also fails with a similar error. The logfile is as follows:
For what it's worth, the receptor is 27795 atoms; I'm not sure where the 27899 is coming from.