Interrupt execution using signals

[titoiride]

Only a simple question: is optimas equipped with some kind of signal trapping? Say that I'm running on a cluster, I can send a SIGINT to interrupt the execution of the code, but will then optimas spawn new simulations? If yes, is there a way to tell it to stop generating?

[ax3l]

Good question, I think it does not do signal handling and any custom signal will terminate.

@titoiride what are you looking for? A clean "ok, stop spawning new sims now and shut down cleanly" handler of the controlling optimas+libE script?
Or do you want to interrupt a specific exp.run() run and, in the same controlling Python script, do another optimas Exploration without restarting the slurm job?

@shuds13 I think for this to work we need to add control variables to libEnsemble, too?

[titoiride]

No I was more thinking high level the first option: you allocate some walltime on an HPC machine, but then, for instance, I'd like to send a signal half an hour before the end of walltime to signal optimas to finish the current simulations, without interrupting them, without spawning new ones. If this is in place, one could dedicate a signal to this (SIGHUP? or whatever) and another signal to instead tell optimas to also interrupt gracefully the current evaluations and stop spawning (SIGINT?).

So my question was more on shell signals rather than a way to interrupt the execution from within the python script.