meyresearch / ML_bind

0 stars 1 forks source link

Incorrect periodicity error in MMPB(GB)SA calculations #1

Open victorprincipe opened 3 years ago

victorprincipe commented 3 years ago

When the MMPBSA script is run using the ambertools20 package, the following output with error message appears:

Loading and checking parameter files for compatibility...
cpptraj found! Using /home/victor/miniconda3/envs/ambertools20/bin/cpptraj
mmpbsa_py_energy found! Using /home/victor/miniconda3/envs/ambertools20/bin/mmpbsa_py_energy
Preparing trajectories for simulation...
231 frames were processed by cpptraj for use in calculation.

Running calculations on normal system...

Beginning GB calculations with /home/victor/miniconda3/envs/ambertools20/bin/mmpbsa_py_energy
  calculating complex contribution...
Found an invalid periodicity in the prmtop file: 23
  File "/home/victor/miniconda3/envs/ambertools20/bin/MMPBSA.py", line 100, in <module>
    app.run_mmpbsa()
  File "/home/victor/miniconda3/envs/ambertools20/lib/python3.9/site-packages/MMPBSA_mods/main.py", line 218, in run_mmpbsa
    self.calc_list.run(rank, self.stdout)
  File "/home/victor/miniconda3/envs/ambertools20/lib/python3.9/site-packages/MMPBSA_mods/calculation.py", line 82, in run
    calc.run(rank, stdout=stdout, stderr=stderr)
  File "/home/victor/miniconda3/envs/ambertools20/lib/python3.9/site-packages/MMPBSA_mods/calculation.py", line 156, in run
    raise CalcError('%s failed with prmtop %s!' % (self.program,
CalcError: /home/victor/miniconda3/envs/ambertools20/bin/mmpbsa_py_energy failed with prmtop tyk2_10_unsolvated_nona.prm7!
Exiting. All files have been retained.

The input command (while in the ambertools20 environment and in the following directory: ML_bind/productions/trial_tyk2/mmpbsa_test/prepared_files) is: $AMBERHOME/bin/MMPBSA.py -O -i mmpbsa.in -o FINAL_RESULTS_MMPBSA.dat -sp tyk2_10.prm7 -cp tyk2_10_unsolvated_nona.prm7 -rp tyk2_vacuum.prm7 -lp tyk2_lig10_vacuum.prm7 -y ~/project2021/ML_bind/productions/trial_tyk2/production.dcd (Please note that your path to the final 'production.dcd' file may be different)

The "prepared files" for this calculation involve:

Other earlier (resolved) issue: Another earlier error message stated that there was an inconsistent number of SOLTY variables (expected=0) in the desolvated complex. These variables in the topology file were all set to zero. On the Amber file formats webpage, it stated that SOLTY is "currently unused (reserved for future use)". Removing these values in the topology file resolved the issue.

jjuarez84 commented 3 years ago

Hi!

victorprincipe commented 3 years ago

Hi Jordi,

Thanks for the help!