Closed xiki-tempula closed 2 years ago
You've not added process.wait()
after process.run()
. If you don't have this in your script, then it will just exit the script and terminate the process, hence the error that you are seeing. You need to add .wait()
when you aren't working interactively. If you are in a notebook, it is fine to just use .run()
, after which you can monitor the progress of the process.
Cheers.
@lohedges It would still fail with the same error even if I have process.wait() at the end.
Sorry, also realised that you need to use process.start()
, not process.run()
. If you look at the docs, e.g. here, you'll see that process.run()
is a convenience function to create an run a new process, i.e. you can use it to re-run an existing process, or pass in a completely new system and protocol. Importantly, it returns a new process object, so you would need to capture this object, which you are not doing. (This exists for consistency with the BioSimSpace.MD.run
interface, i.e. an engine specific version of the engine agnostic MD interface.)
Replacing process.run()
with process.start()
and adding process.wait()
works for me.
@lohedges Thank you.
Prerequisites
I tried to run an energy minimisation with the dev branch and gmx 2022.1 but I got the issue of
Killing job /Users/zwu/build/gromacs/2022.1/bin/gmx mdrun -v -deffnm gromacs
If I go to the work_dir, I could excute the command
/Users/zwu/build/gromacs/2022.1/bin/gmx mdrun -v -deffnm gromacs
and the energy minimisation would finish normally.Steps to Reproduce
Failure logs
param_eror.zip.zip
Context