Closed aizatzaini closed 1 year ago
Please, attach the gmx_MMPBSA.log file
gmx_MMPBSA.log Thank Dr Valdes, I hereby reattach the log file for the above process. Really appreciate your input on this, thank you.
Please, rerun the calculation and send the gmx_MMPBSA.log file
I had rerun the process, and the problem still persist. The log file as follows gmx_MMPBSA.log
The process seemed to stuck at producing output from processing ligand's AMBER topology, claiming that there is 1 water/ion molecule when there isn't any. The ligand consist of only Carbon, Hydrogen and Oxygen. Nothing that resemble water/ion.
This can happen because the ligand contains some atoms listed as ions. Please, send me the files (only 5 or 10 frames of the trajectory) to verify them
trajectory frame 91-100ns.zip Here are the 10 frames (91ns-100ns) of the simulation in xtc form. I chose this timeframe as it had shown least backbone RMSD. I've also included the mol2 file of my ligand, in case it's helpful.
Please, remove the PBCs and select a few frames in xtc format. Also, attach the rest of the files used for the calculation to reproduce the error.
Command line to extract 10 frames
gmx trjconv -f md.xtc -e 100 -o md_10f.xtc
Thanks for the tip on frame extraction, Dr. I've included the 10 frames without PBC the in md_10f_center.xtc file. Trajectory Files.zip
I hereby attach the other files used in the command:
mmpbsa.in -from your tutorial .tpr file. .ndx file (group 1 Protein group 13 Ligand) topology file
What's happening is that the ligand is named "POT" which turns out it's also an abbreviation for an ion (potassium). Please change the name to something else (for example "LIG") and it should work... make sure to change the name in all instances i.e. topology, structure files...
That's amusing. Thanks Dr Valdes, will try it out.
Bug summary
Hi, I am unable to understand what is wrong with my input. It stated that 1 water/ion molecule was found, but there isn't any. I had ran gmx_MMPBSA on a different complex (same protein, different ligand), and it ran smoothly with no error. I think something is wrong with the ligand but need help troubleshooting. I had updated to the latest version of gmx_MMPBSA. Please help!
Terminal output
gmx_MMPBSA.log
gmx_MMPBSA.log
Operating system
Window Subsystem for Linux (Ubuntu 22)
gmx_MMPBSA Version
gmx_MMPBSA v1.6.1+16.gc99f0b4 based on MMPBSA version 16.0 and AmberTools 20
Python version
Python 3.9.12
Installation
conda AmberTools + pip