Thank you, John, for your detailed reply. > we routinely do this, in the following way. We run jobs that may take > up to a week to finish, and they are usually run on a cluster. Our > setup relies on the following behavior for a script. > > 1. you can run the script anytime you want, and it can tell the state > of the calculation by some means. If the script has never been run > before, it submits the job to a queue and exits. If the job is still > in the queue, it exits, and if the job is done, it gives you the > result.
Returning immediately with whatever state the long-running computation is in currently seems indeed to be a good solution. I think I will setup something similar. Would you share your experience on the following issues? - How do you interface such jobs from orgmode? With org-babel, do you execute Python code, or do you run shell commands? - Do you run your Emacs on the master node of the cluster? Or does your setup involve running emacs on the machine you are working on and talking to the cluster over the network? Cheers, Christoph
