You can try starting a tmux/screen session over ssh, and launch Firedrake inside that. Then detach session, log out. When you log back in next time, you can reattach the session and continue. This, of course, often does not work on supercomputers because they like to kill the processes of users on login nodes who are not logged in. In that case the submission system is the answer. On 06/03/17 13:05, Onno Bokhove wrote:
Will submits it to a "standard" multi-core workstation too.
What is the remote login solution for that case?
------------------------------------------------------------------------ *From:* firedrake-bounces@imperial.ac.uk <firedrake-bounces@imperial.ac.uk> on behalf of Lawrence Mitchell <lawrence.mitchell@imperial.ac.uk> *Sent:* Monday, March 6, 2017 12:19 PM *To:* firedrake *Subject:* Re: [firedrake] Running firedrake with nohup Dear Will,
On 6 Mar 2017, at 12:05, William Booker <scwb@leeds.ac.uk> wrote:
Dear Firedrakers,
I'm trying to run some Firedrake runs on HPC, but I keep killing my run whenever I close the terminal I've ssh'ed in with. I was using nohup:
nohup mpirun -n 16 python run.py > output.out
Is there another way to get firedrake to run when I close the connection to my local computer?
You should ask your local HPC systems people how to submit jobs. Normally this is done through some kind of queue manager (e.g. PBS) with qsub.
Cheers,
Lawrence _______________________________________________ firedrake mailing list firedrake@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/firedrake
_______________________________________________ firedrake mailing list firedrake@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/firedrake