Even I calculated MM/PBSA with single CPU, it failed with similar messages:
----------------------
Loading and checking parameter files for compatibility...
mmpbsa_py_energy found! Using /soft/amber/16/bin/mmpbsa_py_energy
cpptraj found! Using /soft/amber/16/bin/cpptraj
Preparing trajectories for simulation...
100 frames were processed by cpptraj for use in calculation.
Running calculations on normal system...
Beginning GB calculations with /soft/amber/16/bin/mmpbsa_py_energy
calculating complex contribution...
File "/soft/amber/16/bin/MMPBSA.py", line 100, in <module>
app.run_mmpbsa()
File
"/soft/amber/16/lib/python2.7/site-packages/MMPBSA_mods/main.py", line
218, in run_mmpbsa
self.calc_list.run(rank, self.stdout)
File
"/soft/amber/16/lib/python2.7/site-packages/MMPBSA_mods/calculation.py",
line 82, in run
calc.run(rank, stdout=stdout, stderr=stderr)
File
"/soft/amber/16/lib/python2.7/site-packages/MMPBSA_mods/calculation.py",
line 157, in run
self.prmtop))
CalcError: /soft/amber/16/bin/mmpbsa_py_energy failed with prmtop
com.prmtop!
Exiting. All files have been retained.
On 01/31/2017 10:38 AM, Vlad Cojocaru wrote:
> One job meaning a single MPI process, or a single job with multiple MPI
> processes ?
>
> Depending on the system size, grid size and number of MPI processes
> asked in 1 job, you may easily consume 64 GB .. At least that was the
> case with Amber 12 and 14 ... I know that in Amber 16 a lot of
> optimizations were done with the MMPBSA code, but we have limited
> experience thus far with Amber 16 and MMPBSA.
>
> All I can say is that we experienced this error often in this context
> before ... But I also know this is a generic error that can be due to
> multiple other reasons ... So, if you calculated your memory consumption
> and you found is fine within your limits, you would have to search for
> other potential issues ...
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Tue Jan 31 2017 - 06:00:04 PST
