Closed marioernestovaldes closed 2 years ago
fundamentally, nothing has changed in the way gmx_MMPBSA runs... As a matter of fact, I tried using nohup and it works fine...
The gmx_MMPBSA run that I am performing is for 700 frames. It takes about 4-4 hrs to complete a run with 100 frames. Since I am accessing my server remotely, I often set up my jobs using "nohup" and "&" signs to push the job in the background, so that the job keeps running even after closing the terminal or after getting disconnected from the server. I rerun this same command, nohup mpirun -np 8 gmx_MMPBSA MPI -O -i mmgbsa_5frames.in -cs sys.pdb -ci prot_rna_dna.ndx -cg 1 15 -ct fnrna-dna_0-500ns_norest-350-400_nopbc_compact_fit_dt1ns.xtc -cp topol.top & but it terminated when the terminal was closed.
This seems to be a very common problem. As you were told earlier, gmx_MMPBSA did not change its execution mode. You can check if it is this problem and let me know.
closing this... feel free to reopen if the problem persists...
I was running this command, nohup mpirun -np 8 gmx_MMPBSA MPI -O -i mmgbsa_5frames.in -cs sys.pdb -ci prot_rna_dna.ndx -cg 1 15 -ct fnrna-dna_0-500ns_norest-350-400_nopbc_compact_fit_dt1ns.xtc -cp topol.top & it was running fine earlier, not the process stops after closing the terminal.
On Wed, Mar 23, 2022 at 5:31 AM Mario Sergio Valdés Tresanco < @.***> wrote:
-- Gayatri Panda PhD19206 (Computational Biology)
_Originally posted by @gayatripanda5 in https://github.com/Valdes-Tresanco-MS/gmx_MMPBSA/issues/176#issuecomment-1077916567_